Hey, @hazlettmcdonalds459! Happy to help you out here whilst you wait for support.

For the 403 Forbidden error with AI Gateway API Key specifically, this could be related to:

• API key permissions or scope issues
• Rate limiting
• Incorrect endpoint configuration
• Authentication header formatting

If you can share more details about how you’re implementing the AI Gateway API calls, the community might be able to help troubleshoot.

Thanks!

I got the same error:

curl -v -X POST “https://ai-gateway.vercel.sh/v1/chat/completions” -H “Authorization: Bearer mygateway_key” -H “Content-Type: application/json” -d ‘{“model”: “alibaba/qwen-3-14b”, “messages”: [{“role”: “user”, “content”: “Hi”}]}’

Here is the error msg: {“error”:{“message”:“Forbidden.”,“type”:“access_denied”}}

I ‘m sure the key is right, And I regenerated a new key, still same error.

Exact same issues. Can’t use AI on hobby accounts even with a valid credit card on file and enough credits to spare.

But Hobby and Pro have no difference on AI Gateway

I ran into the same issue—starting yesterday I’ve been getting a 403 error.

Hey, everyone!

Thank you for your patience, flagging with the right team internally to help out.

In the meantime it's worth verifying your AI_GATEWAY_API_KEY, checking if a billing method is attached to your account, ensuring teamId is included for team projects, and checking for incorrect authorization scopes.

The 403 error indicates insufficient permissions, invalid/missing authentication, or billing issues.

Getting error above when using playground and 403 when using AI gateway; responseBody: ‘{“error”:{“message”:“Forbidden.”,“type”:“access_denied”}}’

I have (and have had for some time) a valid card which is used for billing and even adding credit to the AI gateway.

This has only happened recently, was working previously.

Project works great on another Pro account I have.

Hi, everyone! Thanks for your patience

We had some credit card validation issues for the free tier

You shouldn't see the 403 error now - let me know if you're still seeing it :)

Still seeing it.

{"error":{"message":"Forbidden.","type":"access_denied"}}

This is still happening even for PRO users on the AI playground:

[Error] Failed to load resource: the server responded with a status of 403 () (generate, line 0) on https://ai-sdk.dev/api/generate

Has nothing to do with card validation though.

https://ai-sdk.dev/playground

Still same error {“error”:{“message”:“Forbidden.”,“type”:“access_denied”}}%

Thank you folks! I've shared again with the team.

I am also facing this in hobby account.

I’m seeing the exact same error, and it’s directly impacting our product and customers. This isn’t just a technical inconvenience, it’s affecting the experience of real users in production.

We urgently need clarification or a fix from the Vercel team, because this issue is causing customer-facing problems.

Still happening.

1
{
2
    "error": {
3
        "message": "Forbidden.",
4
        "type": "access_denied"
5
    }
6
}

I can confirm that I have a valid payment method on file, and it was previously working.

Support team is saying they don't see any of your teams in the list, are you seeing this on a different account than you're logged in here with?

I'm experiencing same consistent 403 Forbidden / access_denied errors when using Vercel AI Gateway for my project, despite having a Pro plan with valid billing and available AI Gateway credits.

I have verified:

• Created multiple fresh AI Gateway API keys from the team-level AI Gateway API Keys page

• API keys are active and have not been revoked

• Correct request format with Bearer token authorization and proper model naming (provider/model-name format)

• Tested with direct curl requests bypassing my application entirely

• Same 403 error occurs from both deployed Next.js application and direct API calls

The error occurs consistently:

• HTTP status: 403
• Error type: access_denied
• Error message: "Forbidden."
• Endpoint: https://ai-gateway.vercel.sh/v1/chat/completions

This is reproducible across multiple fresh API keys and occurs at the gateway level, indicating this is not a client-side configuration issue but rather an account- or project-level AI Gateway access issue. I suspect there may be an entitlement flag, internal restriction, or configuration preventing access despite my Pro plan status and available credits.

Hi Jacob, I am facing the issue in the same account from which I am messaging here.

No, I am seeing it on this email address. See the screenshot. Also this used to work, just broken about 3 weeks ago and never recovered. See the screenshot.

This is the POST I am doing

{"playgroundId":"b4a12e8e-51ae-470a-b47e-c08dc868e097","chatId":"1","chatIds":["0","1","HtT29O2"],"model":"openai:gpt-5.1","temperature":0.7,"maxTokens":64000,"topP":1,"frequencyPenalty":0,"presencePenalty":0,"stopSequences":[],"isCodeExecutionEnabled":true,"id":"b4a12e8e-51ae-470a-b47e-c08dc868e097_1","messages":[{"id":"de755569-f398-42d3-8f77-db223e9e1e92","role":"user","parts":[{"type":"text","text":"hi"}]}],"trigger":"submit-message"}

And response URL: https://ai-sdk.dev/api/generate Status: 403 Source: Network Address: 64.239.109.65:443 Initiator: playground:80:7162

We've shared internally. Thanks for your patience!

I cannot believe this has been happening for 3 weeks now.

It works now. Thanks.

I am still having the same issue, did you do anything different or it just started working. Also which tier/plan are you on?

Same issue as before.

same issue here

Hi @iamkunal9, @arhatpradhan, @justinian, could you share the account/team name where you are seeing this issue?

same here, dubjafil’s projects

user: justinian-tomegea

team: energyaspects

Same here. I have having the exact same issue.

I’m on a free account, I keep getting 403; I did not change my code since Dec 2025.

project: motivational-quotes

username: achen7x7-3130

Hey everyone! We have our product team looking into this.

Hi @justinian, can you confirm if your issue has been resolved now?

I cannot, there is absolutely no change

Thanks for confirming let me check again with the team.

Hi @justinian, can you confirm the account again? As per our records the user and team you shared shouldn't be affected by this issue. Have you tried logging out and in again?

Yes, I’ve logged in, logged out, cleared cookie, cleared cache, logged in with passkey, logged in with github, nothing works

Summary URL: https://ai-sdk.dev/api/generate Status: 403 Source: Network Address: 64.239.109.193:443 Initiator: ai-sdk.dev:80:7162

1
{"playgroundId":"4f560326-1848-4e4e-99da-f0a385758ab6","chatId":"pElOvUX","chatIds":["pElOvUX"],"model":"google:gemini-2.5-pro","temperature":0.7,"maxTokens":32768,"topP":1,"frequencyPenalty":0,"presencePenalty":0,"stopSequences":[],"isCodeExecutionEnabled":true,"id":"4f560326-1848-4e4e-99da-f0a385758ab6_pElOvUX","messages":[{"id":"038c6e2b-fb5c-4d11-ad83-89ee1307ebce","role":"user","parts":[{"type":"text","text":"hello"}]},{"id":"b1e27884-76c5-4552-8764-0cfedf706078","role":"user","parts":[{"type":"text","text":"hello"}]}],"trigger":"submit-message"}

adding:

1
Response
2
:status: 403
3
Cache-Control: public, max-age=0, must-revalidate
4
Content-Length: 0
5
Date: Fri, 13 Feb 2026 11:29:54 GMT
6
Server: Vercel
7
Strict-Transport-Security: max-age=63072000
8
Vary: RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch
9
x-matched-path: /api/generate
10
x-vercel-cache: MISS
11
x-vercel-id: lhr1::iad1::4n9cs-1770982193360-81eec777ad74

Which team are you on? Can you share your team ID with us? As Anshuman shared, your user/team should't be affected.

same team as pointed above : energyaspects

Yeah, as Anshuman shared, you shouldn't be affected by this issue - we've checked your account. It's weird!

But thank you for sharing all that information, we shared it with our product team to take a look. They are based out in SF so there will be delays in responses, appreciate you being patience

Sure, but this is not a product change, unless something really bad has happened 3-4 weeks ago. This is a pure technical error, as stated this used to work very well.

Last time it worked was this playground https://ai-sdk.dev/playground/s/811dQvCxBvcc

Our AI product team who is responsible for this product area have been notified as I said.

I understand it's frustrating to wait, but no one from my team in the community can speed this up for you. Again, appreciate your patience.

Still have this problem. And I tried every what I can do.

Hi, I have the same problem and credit card is added.

1
responseHeaders: {
2
  'cache-control': 'public, max-age=0, must-revalidate',
3
  'content-encoding': 'br',
4
  'content-type': 'application/json',
5
  date: 'Sat, 14 Feb 2026 06:12:44 GMT',
6
  server: 'Vercel',
7
  'strict-transport-security': 'max-age=63072000; includeSubDomains; preload',
8
  'transfer-encoding': 'chunked',
9
  vary: 'rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch',
10
  'x-matched-path': '/v1/ai/language-model',
11
  'x-vercel-cache': 'MISS',   'x-vercel-id': 'hnd1::cle1::lndrn-1771049564546-28485ea2431e'
12
},
13
responseBody: '{"error":{"message":"Forbidden.","type":"access_denied"}}',

"ai": "5.0.76"

Hey, I also have the same issue. In case it helps, I have been using https://v0nanobananapro.vercel.app/ all this time with the free hobby credits without any problem. The moment I added 10€ a few days ago, it started to show this popup message and I cant use the app anymore:

Team Access Required

To use Nano Banana Pro, you need to grant access to at least one Vercel team. This allows the playground to use your AI Gateway credits.

Click the button below and select a team on the authorization screen.

I suppose its related to the underlying 403 issue I am having by creating another api key and trying to use it via AI SDK v6.

projectId: prj_I2obLncvKL83J3MYcEc8lN5PkGq1 project name: neuro-granada team: angelhodars-projects

I’m not sure if this is the same issue. My error looks like this: {"type":"error","errorText":"Forbidden."}. It was working fine before and I haven’t changed any code.

This should be working for you now, JT! Thanks.

@cwang Looks similar - does it have the same 403 code?

Confirmed as fixed, thanks.

No — the status code is 200.

The 403 errors are back, what are you guys doing ?

It just started to happen again, today, same error, same call.

I'll pass to the team

However, your issue was specifically to the playground not gateway.

Correct, the issue is with the playground use but the error is the same and sharing the same back-end, last time this was working fine was yesterday.

Cool - I'll close this topic as the discussion is going in different directions!

As this has been happening a few times for you, can you raise a support ticket? vercel.com/help is the way to go. I wonder if it's account specific to you. Thanks!