AI Gateway returns pre-routing 403 with paid credits and fresh API key

AI Gateway inference is blocked with HTTP 403 before provider routing.

Confirmed:

  • Vercel Hobby workspace with $25 paid AI Gateway credit
  • Active newly created AI Gateway API key
  • Key is used by a freshly rebuilt Preview deployment
  • No spend budget is enabled
  • openai/gpt-5.4-mini returns 403 with zero input/output tokens and no routing
  • alibaba/qwen3.5-flash, which supports ZDR and no-training on all routes, returns the identical 403
  • OIDC and API-key authentication were both tested
  • Requests appear in Gateway logs, but routing details are unavailable and cost remains $0

Could Vercel staff please check whether AI Gateway inference entitlement is disabled or incorrectly provisioned for this workspace?

Do you have providerOptions.gateway.zeroDataRetention enabled in the requests you’re making? ZDR is only available on Pro/Enterprise, so the gateway attempts to serve non ZDR tokens and gets blocked as a 403

hanks—that was exactly the issue: we had zeroDataRetention: true enabled on a Hobby project, so I’ve removed that option while keeping disallowPromptTraining enabled.

you rock