docs(ai-gateway): document provider key routing gotcha#111
Open
e345ee wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
vercel env rmexamples for removing stale provider keys across environmentsWhy
Projects migrating from direct provider SDKs to AI Gateway can accidentally keep stale provider keys like
ANTHROPIC_API_KEY,OPENAI_API_KEY, orGOOGLE_API_KEYin Vercel env vars. When those keys are present, the AI SDK can choose direct-provider mode instead of routing through AI Gateway, even if the value is empty.That makes failures confusing: the app appears to be configured for AI Gateway, but requests may still hit the upstream provider directly and fail with errors like
401 invalid x-api-key. This docs note makes the migration path explicit: remove stale provider keys entirely, then redeploy.Verification
npx -y bun@latest run validateCloses #91