Vercel AI Gateway

Drive the product through a documented public API G

Agent access

Connect an agent via an official MCP server G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Plug MCP servers into this product so it can use their tools G

Agent access

Point an agent at llms.txt or agent-oriented docs G

Agent access

Build against official SDKs G

Agent access

Run the product headlessly / in CI for automation G

Agent access

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Explore an interactive API reference with runnable examples G

Api quality

Issue scoped/least-privilege API credentials for an agent G

Agent access

Use an official CLI G

Agent access

Rely on versioned APIs with a documented deprecation policy G

Api quality

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Operate the product with natural-language commands G

Agentic features

Set up automations that run autonomously in the background G

Agentic features

Subscribe to events via webhooks G

Agent access

Test against a sandbox environment without touching production data G

Api quality

Call many model providers through one consistent API C

One endpoint

Configure automatic fallback to another model or provider when one fails C

Fallbacks

Point existing OpenAI-compatible code at the gateway by changing only the base URL and key C

Compatibility

Inspect logged requests and responses with latency, token counts, and cost attached C

Logs

Make tool and function calls across different providers with a consistent schema C

Tool calling

Set hard budgets and spend limits per key, team, or user C

Budgets

Track spend per model, key, team, or user across all providers in one place C

Spend tracking

Mint gateway-managed keys for teams and apps without exposing raw provider keys C

Virtual keys

My agent can switch models mid-task by policy — cost, capability, or availability — through gateway routing rules C

Policy routing

Export all of my data in open formats and leave G

Stream token-by-token responses through the gateway from any provider C

Streaming

Define rules that trigger actions automatically on events G

Provision gateways, keys, and budgets programmatically through an admin API C

Programmatic admin

Prevent my data from being used to train AI models G

Self-host the core product G

Browse or query a catalog of available models with pricing and context-window metadata G

Catalog

Set automatic retry policies for transient provider errors C

Retries

Cache responses at the gateway to cut cost and latency on repeated requests C

Caching

Do everything through the API that I can do in the UI G

Give an autonomous agent its own key with budget and rate guardrails so it cannot run away on spend C

Agent guardrails

Load-balance traffic across providers, deployments, or keys by weight, latency, or cost C

Load balancing

Bring my own provider API keys and have the gateway use them for my traffic G

Byok

Run traffic through gateway infrastructure that adds minimal latency overhead to provider calls C

Latency

Smooth provider rate limits by spreading traffic across keys and queuing or throttling requests C

Rate limits

Choose where my data is stored (region/residency) G

Control data retention and deletion G

Opt out of telemetry and usage tracking G

Perform bulk operations across many items at once G

Read the product's source under an open license G

Schedule recurring jobs or workflows G

Export gateway logs and traces to my own observability stack G

Integrations

Request structured JSON-schema outputs across providers C

Tool calling

Version, review, and roll back my automations G