- Published on
Token Pass credit now applies automatically across AI Gateway
- Authors
- Name
- DeepHorus
Token Pass credits now apply automatically to included model usage through AI Gateway, eliminating the need for a dedicated Token Pass API key. The change supports requests authenticated with an API key, an OIDC token, or fx login. Subscribers can still create a Token Pass key from the dashboard or CLI for credentials scoped only to featured models and providers.
The update simplifies access for Token Pass subscribers by making credit consumption automatic across supported authentication methods. A dedicated key is no longer required for included usage. The capability is available now for Token Pass subscribers on Pro teams.
Billing-period exhaustion follows clear rules. When Token Pass credit runs out, requests from a standard key or OIDC token fall back to the team’s AI Gateway credits. Token Pass keys stop until the next billing period.
Data handling remains tied to routing. Requests served through the Token Pass provider keep Zero Data Retention (ZDR). Fallback requests follow the team’s setting; with team-wide ZDR enabled, they route only to ZDR providers.
The distinction matters for credential management. Teams that created a Token Pass key during setup must switch to a standard API key or OIDC token to get fallback. A scoped Token Pass key still cannot use team AI Gateway credits after included credit is exhausted.
The automatic application reduces configuration overhead while preserving scoped-key options. It also makes fallback behavior explicit for administrators managing team credits and privacy controls. The change gives administrators a clearer view of how team credits are consumed after included Token Pass credit is exhausted. Token Pass documentation provides further details for subscribers planning credential changes.
