Skip to main content
Use workspace budgets and API key limits to control spending. An organization shares one account balance; workspace and key limits constrain their respective usage.

​
Set a budget

  1. Enter the workspace. An administrator opens its budget settings.
  2. Choose a period and amount, then select a hard limit or alert only.
  3. Configure any alert thresholds and valid recipients. Save and check current usage.
A hard limit prevents usage beyond the allowance. An alert-only setting notifies recipients without independently blocking requests at the alert threshold.

​
Periods and resets

Resets use UTC, regardless of your browser’s time zone. Changing an amount or period does not erase actual usage. Setting a limit below usage already incurred immediately affects the remaining allowance.

​
How limits work together

  • A key has an amount and period. An amount of 0 means no limit at the key level.
  • An unset workspace limit means no limit is configured at that level, not a zero allowance.
  • An unlimited key still needs workspace allowance and sufficient account balance.
  • Exhausting the account balance, a workspace hard limit, or a key limit restricts requests.
Exhausting an allowance stops in-progress requests with an error. Actual usage before termination is still charged. Check request logs for the result and cost.

​
When a limit is reached

Identify which limit applies. An administrator can add credits when the balance is insufficient. For a periodic limit, wait for the reset or ask an authorized person to adjust it. Switching keys does not remove a hard limit on the same workspace. A budget alert does not add allowance. Use usage analytics to investigate the main sources of spending. Last updated: 2026-10-13