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.

Organizations and workspaces
  • 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.

All key settings
Settings on one API key
SettingOptions
Routing modepriority, autoCheapest, autoFastest, autoMostReliable
Provider orderAny providers, in order
Excluded providersUp to 20
Own provider keysfirst, only, off
Key poolall, platformOnly
Auto Retry0 to 10 retries
Auto Fallback0 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.