Token Pass Models and Routing

AI Gateway bills a request to Token Pass when all of these are true:

• Your team has an active Token Pass with credit remaining.
• You authenticate with an AI Gateway API key. Use a Token Pass API key.
• The request uses a featured model ID.
• The Token Pass provider (token-pass) serves the request.

All other requests follow normal AI Gateway routing and billing.

Token Pass currently serves these models through Wafer. AI Gateway deducts usage from your credit at each model's list price.

A Token Pass API key is an AI Gateway API key marked for Token Pass when you create it. You can't change a key's type later.

With a Token Pass API key:

• AI Gateway serves featured models only through the token-pass provider and bills them to your Token Pass credit.
• Requests never fall back to other providers or to your AI Gateway credits.
• Requests to any other model or endpoint fail with a 403.

Token Pass only works with AI Gateway API keys. AI Gateway doesn't use Token Pass for requests authenticated with an OIDC token, a Edgenivo access token, or an app token. It routes those requests as usual and bills your AI Gateway credits.

These requests don't use Token Pass credit:

• Any model that isn't featured, including image, video, audio, and embedding models.
• Fast variants of featured models, including fast modes in coding agents.
• Featured models that you send with a regular AI Gateway API key and route to another provider.

With a Token Pass API key, these requests fail with a 403. With a regular AI Gateway API key, they bill to your AI Gateway credits.

With a Token Pass API key, AI Gateway sends featured models to the Token Pass provider. You don't need to set provider options.

Because a Token Pass API key can't use other providers, an order or only setting that leaves out token-pass makes the request fail. An order that lists token-pass first works as usual.

To use a featured model with another provider, send the request with a regular AI Gateway API key and name that provider:

curl --fail-with-body https://ai-gateway.vercel.sh/v1/chat/completions \
  -H "Authorization: Bearer $AI_GATEWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "zai/glm-5.3",
  "messages": [
    { "role": "user", "content": "Reply with one short sentence." }
  ],
  "providerOptions": {
    "gateway": { "only": ["zai"] }
  }
}'

Token Pass requests don't fail over. If the Token Pass provider returns an error, the request fails with that error. Retry the request, or switch to regular AI Gateway usage, billed to your AI Gateway credits.

Once you use up your Token Pass credit, requests with your Token Pass API key fail with a 403 until your next billing period starts. AI Gateway doesn't charge your AI Gateway credits for these requests, and Token Pass doesn't top up. To see your remaining credit and reset date, open the Token Pass tab.

To continue with paid usage before your credit resets, switch your coding agent or application to a regular AI Gateway API key and remove any routing options that select the token-pass provider. These requests use your AI Gateway credit balance at the selected provider's rates, so you need enough AI Gateway credits to keep making requests.

For automatic failover, your application has to catch the failed Token Pass request and retry it with a regular AI Gateway API key. Setting a provider order alone doesn't switch API keys.

Regular AI Gateway usage bills to your AI Gateway credits at each provider's rates. It covers every model, including featured models served by other providers. To set it up:

1. Add AI Gateway credits. Go to AI Gateway, click the button that shows your AI Gateway credits balance, and add credits. To keep your balance from running out, configure auto top-up.

2. Connect your agent with a regular API key. Run the setup command without --key. It creates a regular AI Gateway API key and configures your agent with it:

   terminal

   npx vercel@latest ai-gateway setup --agent <name>

   To use an existing key instead, create a key with the Standard key type and pass it with --key.

3. Remove Token Pass routing options. Delete any order or only setting that selects token-pass, such as provider_order in fx or options.order in opencode.json.

4. Set a budget (optional). To cap what the key can spend, set a budget.

To go back to Token Pass after your credit resets, run the setup command again with your Token Pass API key.

Token Pass errors return HTTP status 403 with the error type no_providers_available. Check the message to find the cause:

Errors from the Token Pass provider come back unchanged. See Failover.

Use any of these:

• Dashboard: in Observability, the provider is Edgenivo Token Pass.
• API: providerMetadata.gateway.routing.resolvedProvider is token-pass.
• fx: fx ask --json returns token-pass in resolved_provider.

If a featured model request failed, or another provider served it, check these in order:

1. The request uses a Token Pass API key, not an OIDC token or a Edgenivo sign-in.
2. The key belongs to the team that has Token Pass.
3. The model ID is exactly zai/glm-5.3, moonshotai/kimi-k3, or deepseek/deepseek-v4.1-flash, with fast mode off.
4. Your agent config doesn't set an order or only that leaves out token-pass.
5. Your provider allowlist and model allowlist include Token Pass and the featured models.
6. You still have credit this billing period. Check the Token Pass tab.