Budgets

Budgets let you set spending limits at multiple levels — organization-wide per-user caps, per-API-key limits, and per-team limits. Each budget tracks total spend against its limit with a visual progress bar and status indicator, so you can see at a glance whether spending is on track or has been exhausted.

Organization per-user limits

Two organization-wide caps appear at the top of the Budgets page. These apply a default spending boundary to every user in your organization:

To set either cap, click Set Cap, enter a dollar amount, and click Save. You can remove a cap at any time by clicking Cancel next to it.

API key budgets

Switch to the API Keys tab to manage per-key spending limits. The table shows all configured budgets:

Create an API key budget

1. Click + Create Budget.
2. Select the Created by user (determines which API keys are available).
3. Select the API key you want to budget.
4. Enter the Budget limit in USD.
5. Click Create Budget.

Edit or delete an API key budget

• Click the pencil icon to edit the budget limit. Editing does not reset the total spend counter.
• Click the trash icon to delete the budget. Historical spend data remains visible in Usage and Analytics.

Team budgets

Switch to the Teams tab to manage per-team spending limits. The page lists every team in your organization with its members, their individual budgets (if set), and their current usage.

Create a team budget

1. Find the team and click + Set Budget.
2. Choose a budget type:

3. Enter the Budget limit in USD.
4. Click Create Budget.

Pooled budgets work well for project teams with a fixed allocation. Per user budgets are better for standardizing individual developer spend across a team.

Per-user overrides

On the Teams tab, each team member row shows their individual Budget and Usage columns. Click the pencil icon next to a member to set a user-specific budget that overrides the team default. This is useful when certain team members need higher or lower limits than the rest of the team.

How budget levels interact

Budgets are evaluated from most specific to least specific:

1. User-specific budget (set on the Teams tab per member)
2. Team budget (pooled or per-user)
3. Organization soft cap (default for users without a more specific budget)
4. Organization hard cap (absolute ceiling — always enforced)

A more specific budget overrides a less specific one, except that the hard cap is never exceeded.

Practical uses

• Cap project spend: create a dedicated API key for a project, set a budget, and monitor it on the API Keys tab. When the budget approaches its limit, decide whether to increase it or shift traffic.
• Standardize team spend: set a per-user team budget so every developer on a team gets the same limit without configuring each one individually.
• Sandbox safety nets: set a low org soft cap as a default, then grant higher limits to specific teams or users who need them.
• Hard guardrails: set an org hard cap to ensure no individual user ever exceeds a fixed dollar amount, regardless of other budget settings.

See also