Skip to main content
Use sandbox API key budgets to set optional lifetime ceilings on funded work attributed to credentials. These budgets are separate from the organization’s prepaid funds.

​
How a budget is consumed

The ceiling covers consumed credit plus outstanding reservations. It has no automatic daily or monthly reset. A request must fit both the key budget and the organization’s available funds. For example, a key can hit its ceiling while the organization still has credit. Adding organization credit does not increase that key’s ceiling.

​
Commitments stay with their budget

A second key cannot move an existing machine’s commitments to a different budget. Lifecycle work remains charged to the original budget. Credential rotation preserves the durable budget identity rather than resetting consumption. A budget does not mint or earmark organization funds. Several credentials can share access to the same organization balance; that balance remains the overall funding constraint.

​
Check a refusal

Inspect the returned funding or admission error. Distinguish an exhausted key ceiling from insufficient organization credit and from resource limits. Use an appropriately authorized credential for new work after the account’s budget authority is resolved. Inspect your key metadata with admin authority when diagnosing credential constraints. See API keys and scopes, Prepaid credit, and Credit and payment problems.