- 00
- Features
- Multiple API Keys
One key per environment, one balance.
Give each environment or client its own key. Each has its own routing, limits and spend caps, and all of them spend the organization's one prepaid balance.
Keys and organization
- Keys per organization
- 50
- Balances
- 1
- Spend caps per key
- 5
- Concurrent tasks per key, up to
- 100,000
01Scope
Keys live in workspaces. The balance belongs to the organization.
- OrganizationHolds the one prepaid balance and every deposit.
- WorkspaceGroups keys and their usage. The key limit counts across all workspaces.
- API keyCarries its own settings and spend caps.
02Per key
What one key can set.
A request can still override each of them for one task.
| Setting | Options |
|---|---|
| Routing mode | priority, autoCheapest, autoFastest, autoMostReliable |
| Provider order | Any providers, in order |
| Excluded providers | Up to 20 |
| Own provider keys | first, only, off |
| Key pool | all, platformOnly |
| Auto Retry | 0 to 10 retries |
| Auto Fallback | 0 to 20 fallbacks |
03FAQ
Questions about Multiple API Keys.
01
Is there a limit on API keys?
An organization can hold up to 50 API keys, counted over all of its workspaces.
02
Do separate keys mean separate balances?
No. Every key spends the organization's one prepaid balance. To bound what one key can spend, give it up to 5 spend caps of its own.