docs: add Vercel AI Gateway as a supported provider - #2728
Open
joemckenney wants to merge 1 commit into
Open
joemckenney wants to merge 1 commit into
joemckenney wants to merge 1 commit into
Conversation
✅ Deploy Preview for theagentrouter canceled.
|
Contributor
|
@joemckenney it looks like DCO signoff i missing, can you address that? |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Signed-off-by: Joe McKenney <joe.mckenney@vercel.com>
joemckenney
force-pushed
the
vercel-ai-gateway-provider
branch
from
September 23, 2026 23:30
923df1c to
56f946d
Compare
Author
@missBerg updated, thanks for flagging |
missBerg
added
documentation
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
2 participants
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.
Description
Adds Vercel AI Gateway as a supported provider.
Vercel AI Gateway fronts models from many providers behind a single OpenAI-compatible endpoint at
https://ai-gateway.vercel.sh/v1and authenticates withAuthorization: Bearer <token>. That maps onto the existingOpenAIschema andAPIKeyBackendSecurityPolicy, so no data plane changes are needed. It also serves the native Anthropic Messages API on the same host and accepts the credential viax-api-key, so{"name":"Anthropic"}with anAnthropicAPIKeypolicy works as an alternative. Both options are recorded in the supported-providers table and in the guide.Included:
examples/basic/vercel.yaml: AIGatewayRoute, AIServiceBackend, APIKey BackendSecurityPolicy, Backend, BackendTLSPolicy and Secretsite/docs/getting-started/connect-providers/vercel.mdplus index linkssupported-providers.mdandsupported-endpoints.mdaigw runenvironment-variable example insite/docs/cli/run.mdinternal/autoconfig/testdata/vercel.yamland aTestWriteConfigcase forOPENAI_BASE_URL=https://ai-gateway.vercel.sh/v1Related Issues/PRs (if applicable)
Supersedes #2623. The original author is no longer working on this; this is the same change rebased onto current main with the conflicts resolved.
Special notes for reviewers (if applicable)
LLMProviderscomponent, so the homepage entry now lives insite/src/data/home/providers.ts.raw.githubusercontent.comURLs in the new doc follow the current brand rules;npm run check:brandpasses. Frozen identifiers (envoy-ai-gateway-*resource names, namespace, license headers) are untouched.go test ./internal/autoconfig/...passes with the new testdata.