# Token Pass credit now applies automatically across AI Gateway

Source: [Vercel](https://vercel.com/changelog/token-pass-credit-now-applies-automatically-across-ai-gateway)  
Feed7 permalink: https://feed7.dev/p/token-pass-credit-now-applies-automatically-across-ai-gateway-0xyrthp  
Published: 2026-11-06T01:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

AI Gateway now applies Token Pass credit to standard API keys and OIDC, with fallback to team credits after exhaustion; this changes credential and billing behavior for Pro teams.

## Source Summary

For Token Pass subscribers on **Pro teams**, included usage now applies through API keys, OIDC tokens, or fx login; a dedicated Token Pass key is no longer required. When credit runs out, standard keys and OIDC fall back to team AI Gateway credits, while Token Pass keys stop.

## Practical Implication

Builders should use a standard key or OIDC token if they want requests to continue on team credits after the Token Pass allowance is depleted. Token Pass provider requests retain ZDR; fallback follows the team's setting.

## Agent-Ready Context

For Token Pass subscribers on **Pro teams**, included usage now applies through API keys, OIDC tokens, or fx login; a dedicated Token Pass key is no longer required. When credit runs out, standard keys and OIDC fall back to team AI Gateway credits, while Token Pass keys stop.

Builders should use a standard key or OIDC token if they want requests to continue on team credits after the Token Pass allowance is depleted. Token Pass provider requests retain ZDR; fallback follows the team's setting.

With team-wide ZDR enabled, fallback routes only to ZDR providers. Existing Token Pass keys do not get fallback, so teams using them need to switch credentials to use this behavior.

## Connected Context

Feed7 judgment across 1020 accumulated Signals:

This removes the dedicated Token Pass key as a requirement for Pro teams, while making credential choice determine whether requests can fall back to team credits after the allowance runs out. The ZDR note also makes fallback policy part of routing behavior: a team's provider settings govern fallback, while Token Pass requests retain ZDR.

- [How Tailscale built a customer-facing model router on AI Gateway](https://feed7.dev/p/how-tailscale-built-a-customer-facing-model-router-on-ai-gateway-186s3tu) — Both describe gateway access shaped by identity or credentials and routing policy; this update adds a concrete allowance-exhaustion fallback behavior to that broader control pattern.
- [The end of credential sprawl for agents](https://feed7.dev/p/the-end-of-credential-sprawl-for-agents-0iwzpki) — Token Pass simplifies which credentials can access included usage, while Connect focuses on short-lived, task-scoped provider credentials; they address related credential operations but describe distinct mechanisms.
- [Vercel AI Gateway and Vercel Sandbox now available on Hermes Agent](https://feed7.dev/p/vercel-ai-gateway-and-vercel-sandbox-now-available-on-hermes-agent-04gyfsv) — Both make OIDC relevant to gateway use, but this update specifies how credential type affects credit fallback, whereas the Hermes item treats gateway routing and execution sandboxing as separate choices.

## Context Map

- Layer: infra
- Domains: coding, security
- Topics: gateways, sandboxing

## Uncertainty

- With team-wide ZDR enabled, fallback routes only to ZDR providers. Existing Token Pass keys do not get fallback, so teams using them need to switch credentials to use this behavior.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.
