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.
responseHeaders: {
'cache-control': 'public, max-age=0, must-revalidate',
'content-encoding': 'br',
'content-type': 'application/json',
date: 'Sat, 14 Feb 2026 06:12:44 GMT',
server: 'Vercel',
'strict-transport-security': 'max-age=63072000; includeSubDomains; preload',
'transfer-encoding': 'chunked',
vary: 'rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch',
'x-matched-path': '/v1/ai/language-model',
'x-vercel-cache': 'MISS', 'x-vercel-id': 'hnd1::cle1::lndrn-1771049564546-28485ea2431e'
},
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.
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? Help is the way to go. I wonder if it’s account specific to you. Thanks!
