Token Pass credit now applies automatically across AI Gateway
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.
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.
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.
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.