Hi Vercel Team and Community,
I’m experiencing a persistent bug with the AI Gateway where requests selected for Claude 4.1 Opus are actually routing to what appears to be Claude 3 Opus (or a misconfigured version). This happens on the Hobby plan, and it’s reproducible. The dashboard logs show the correct model being selected and sent, but the AI’s responses consistently self-report as “Opus 3” with a training data cutoff of April 2024 (which aligns with Claude 3.5 Sonnet’s cutoff, but the model claims Opus 3). This mismatch prevents access to the improved capabilities of Claude 4.1 Opus, like its March 2025 cutoff and enhanced performance on benchmarks (e.g., 74.5% on SWE-bench for coding tasks).
I’ve posted about this before (reference: similar thread at https://community.vercel.com/t/vercel-giving-opus-3-instead-of-opus-4-1-in-ai-gateway/20445), but it was ignored, so I’m providing a full, detailed report here with steps to reproduce, code, logs, and references. Hoping for escalation to the engineering team— this seems like a backend routing or fallback error, especially since Vercel announced full support for Claude 4.1 Opus on August 5, 2025.
My Setup:
-
Plan: Hobby (with the standard $5 monthly credit for AI usage—no out-of-pocket costs until exceeded).
-
Project: Next.js app using Vercel AI SDK for integration.
-
Model Selected: claude-4-1-opus-20250805 (exact ID from Vercel’s model list at https://vercel.com/ai-gateway/models/claude-4.1-opus).
-
Environment: Deployed on Vercel, using the AI Gateway endpoint (https://api.vercel.com/v1/ai/gateway/anthropic).
Steps to Reproduce:
-
Set up a basic Next.js project with Vercel AI SDK (as per official docs: https://vercel.com/docs/ai-gateway/provider-options).
-
Configure the Anthropic provider in code to target Claude 4.1 Opus.
-
Deploy to Vercel and enable AI Gateway in the dashboard.
-
Send a test prompt via the API, e.g., “What is your model version and training data cutoff date?”
-
Check dashboard logs: It confirms routing to claude-4-1-opus-20250805.
-
Observe the response: AI says “I am Claude 3 Opus” (or similar) with “April 2024” cutoff— not the expected “Claude 4.1 Opus” with March 2025 cutoff.
Code Snippet (Minimal Example):
Here’s the exact code I’m using in my app (from @ai-sdk/anthropic package):
typescript
import { createAnthropic } from '@ai-sdk/anthropic';
import { generateText } from 'ai';
const anthropic = createAnthropic({
baseUrl: 'https://api.vercel.com/v1/ai/gateway/anthropic', // Vercel AI Gateway
apiKey: process.env.VERCEL_AI_API_KEY, // My Vercel API key
});
export async function POST(req: Request) {
const { prompt } = await req.json();
const { text } = await generateText({
model: anthropic('claude-4-1-opus-20250805'), // Explicitly selecting 4.1 Opus
prompt,
});
return Response.json({ text });
}
-
Test Prompt: “What is your exact model name, version, and training data cutoff date?”
-
Expected Response (from direct Anthropic API or Claude.ai): “I am Claude 4.1 Opus, trained up to March 2025.”
-
Actual Response (via Vercel AI Gateway): “I am Claude 3 Opus, with a knowledge cutoff of April 2024.” (Sometimes it hallucinates as Opus 3 but gives Sonnet-like answers.)
Evidence and Logs:
-
Dashboard Confirmation: In Project > Observability > Logs, the request payload shows: { “model”: “claude-4-1-opus-20250805”, “provider”: “anthropic”, … } (I can DM screenshots if needed—forum doesn’t allow uploads easily.)
-
Capability Tests: To confirm it’s not 4.1, I asked about events post-April 2024, e.g., “What major Anthropic updates happened in May 2025?” (Claude 4 release). It responds: “I don’t have information past April 2024.” Real 4.1 knows up to March 2025.
-
This isn’t a rate limit issue—usage is well under the $5 credit (e.g., <10k tokens/month).
-
No errors in console; responses are 200 OK.
Why This Matters / Impact:
-
Claude 4.1 Opus is a “drop-in upgrade” per Vercel’s changelog (https://vercel.com/changelog/claude-4-1-opus-is-now-supported-in-vercel-ai-gateway, Aug 5, 2025), with better reasoning, coding, and agentic tasks. Using an older model defeats the purpose.
-
On Hobby, this blocks free/low-cost access to premium models as advertised—no need for separate Anthropic accounts.
-
Similar issues reported elsewhere:
-
Reddit thread on Claude 4.1 bugs: https://www.reddit.com/r/ClaudeAI/comments/1mtb2ka/anyone_else_playing_bug_whackamole_with_claude/ (users switching models due to mismatches).
-
Anthropic’s GitHub: Model identity bugs in their ecosystem (e.g., https://github.com/anthropics/claude-code/issues/5237). This could be an integration glitch on Vercel’s side.
-
Requested Actions:
-
Investigate and Fix: Please confirm if this is a known routing bug (e.g., fallback to Opus 3 on Hobby plans) and provide an ETA for resolution. Is there a config workaround?
-
Escalation: Tag @vercel-support or engineering—I’ve submitted a ticket via https://vercel.com/help but no response in 48+ hours.
-
Community Input: Has anyone else on Hobby seen this? Workarounds like direct Anthropic API work, but I want to stay with Vercel for the gateway features (caching, load-balancing).
-
Compensation: If this persists, consider extending the $5 credit or a Pro trial to test if it fixes (though docs say 4.1 is supported on all plans).
Thanks for your help—Vercel is great otherwise, but this bug is blocking my project. Happy to provide more logs/code or hop on a call.
Best, Yeasin Hobby Plan User