Skip to content
Docs

Call AI models across providers with Vercel AI Gateway

Use one managed gateway from any infrastructure to centralize credentials, log requests, control spend, and fail over across providers.
index.mts
import { generateText } from 'ai';
 
const { text } = await generateText({
  model: 'openai/gpt-6-astra',
  prompt: 'Explain AI Gateway in one sentence.',
});
 
console.log(text);
terminal
curl https://ai-gateway.vercel.sh/v1/chat/completions \
  -H "Authorization: Bearer $AI_GATEWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-6-astra",
    "messages": [
      {
        "role": "user",
        "content": "Explain AI Gateway in one sentence."
      }
    ]
  }'

AI Gateway is available on all plans. Your use of each AI provider is subject to their terms listed on each model's page and subject to Vercel's AI Product Terms.

Vercel AI Gateway gives applications and coding agents shared access to models across providers. It supports modalities including text generation, image generation, video generation, speech, transcription, realtime, embeddings, and reranking. Add files and tool calls where the selected model supports them.

Call AI Gateway from any environment with the AI SDK, OpenAI Chat Completions, OpenAI Responses API, Anthropic Messages, a supported coding agent, or a framework integration.

AI Gateway routes requests across providers and fallback models, then records status, provider, latency, token usage, cost, and every routing attempt. To prefer an inference provider and verify which provider served the request, set a provider order and read the response metadata. Configure budgets, access policies, data handling, and Bring Your Own Key (BYOK) for your team. AI Gateway adds zero markup to provider token prices, including with BYOK.

Your application does not need to run on Vercel. Call AI Gateway from any server, cloud, or local environment with an AI Gateway API key. Vercel deployments can use OpenID Connect (OIDC) instead.

Use AI Gateway when you want these controls without operating your own proxy, database, and routing control plane:

RequirementHow AI Gateway handles it
Centralized credentialsAuthenticate your application once, then use AI Gateway system credentials or your own provider accounts through BYOK.
Request loggingInspect each request's model, provider attempts, latency, token usage, status, and cost in request logs.
Spending controlsSet budgets for a team, project, API key, or team member. AI Gateway rejects new system-credential requests after an applicable budget is exceeded.
Provider failoverRoute a model across healthy providers and configure ordered provider and model fallbacks.

Budgets cover spend billed through AI Gateway system credentials. BYOK spend is metered separately and does not count toward those limits. If a BYOK request fails, AI Gateway can fall back to system credentials. Review the BYOK behavior and soft-cap budget semantics when strict provider-account use or zero-overshoot limits are requirements.

Explore chat platforms and ecosystem integrations, learn how to handle 429 responses, or see the AI Gateway FAQ for common questions about model availability, pricing, and request errors.


Was this helpful?

supported.