Key controls
Per-key spend quotas, expiry, region selection, and revocation.
Plan and usage-pack spend is account-level. Each API key can additionally carry its own controls, which cap a key shared with a teammate, a project, or a CI job.
Per-key controls
| Control | Description |
|---|---|
| Spend quota | A USD limit for the key, from $0.01 to $10,000. |
| Reset window | Optional daily or monthly reset for the quota. |
| Expiry | An optional timestamp after which the key stops working. |
| Regions | Which regions the key's inference may use. See Regions. |
| Revocation | Invalidate a key immediately at the gateway. |
When a key holds a quota, its spend is tracked against that quota independently of the account budget. Exhausting a key's quota returns an error for that key; other keys on the account continue to work.
Manage keys
Create, inspect, and revoke keys under Account → API keys. Copy a key once at creation; only a hash is stored and it cannot be shown again.
Related
- Plans and billing: account budgets and usage packs.
- Authentication: how keys are sent on requests.