Skip to main content
Budgets apply spending controls to a named target. Each budget defines a scope (what it applies to), period limits (how much can be spent or consumed per reset period), and an optional expiration date after which the budget stops enforcing. When a cost or token limit is reached, requests matching the budget’s scope are blocked until the period resets. Requests per minute limits block for one minute only, independent of the reset period. Common use cases:
  • Cap monthly spend per customer or tenant by scoping a budget to an Identity.
  • Prevent a staging or CI environment from consuming production credits by scoping a budget to its API Key.
  • Limit exposure to an expensive provider or model during evaluation by scoping a budget to a Provider or Model.
  • Enforce a hard workspace-wide cost ceiling as a safety net by scoping a budget to the Workspace.
  • Control spend for a time-boxed experiment using a One-time reset period with an expiration date.
Navigate to Settings > Organization > Budgets to manage budgets.
Only workspace admins can create, edit, or delete budgets.

​
Overview

The Budgets table lists all budgets in the organization.
Budgets list showing budget rows with Target, Scope, Limits, Reset, Expires, and Updated columns.

The Budgets overview showing all budgets with their scope, limits, reset period, and expiration status.

Use Filter to narrow the list by Period (Daily, Monthly, One-time, Weekly, Yearly), Scope, or Status (Active, Expired). Use Sort by to reorder by Expiry soon, Newest, or Recently updated.

​
Monitor usage

Click a budget row to open its detail page:
  • A metric card for each configured limit (Total spend, Tokens, Req per minute) shows current usage, a progress bar, and percentage consumed.
  • Scope, Resets period, Renews in countdown, and Expires date appear at the top.
Budget detail page for identity Jarmila showing 66% used of $0.20 total spend, 89% used of 25,000 tokens, 0% used of 5 requests per minute, and two alerts configured at 75% and 90% usage.

Budget detail page for an Identity-scoped budget, showing Total spend, Tokens, and Req per minute metric cards with progress bars, alongside configured alerts.

  • Click Adjust limits to edit the budget’s period limits or expiration date.
  • Click Add threshold in the Alerts section to set up an alert.
  • Click Delete Budget to permanently remove it. Enforcement stops immediately.

​
Create a budget

1

Open the creation dialog

Click Create in the top-right corner of the Budgets page.
Create budget dialog showing Scope, Period limits, and Expiration fields, with an empty Alerts section reading No alerts configured and a disabled Add threshold button.

The Create budget dialog with scope, period limits, expiration date, and Alerts fields.

2

Set the scope

Under Scope, select what the budget Applies to:For all scope types except Workspace, a second field appears to select the specific target (for example, which API key or which identity).
Only one budget is allowed per target. If a budget already exists for the selected target, an inline error is shown and the budget cannot be created until a different target is selected.
3

Configure period limits

Under Period limits, set the Reset period (required) and one or more of the following limits:Leave a limit at 0 to leave it unconfigured. At least one limit must be set to a non-zero value to create the budget.Reset periods follow a fixed schedule:
Requests per minute is a rolling rate cap enforced continuously, independent of the reset period.
If a budget is exhausted before the period resets, an admin can increase its limit to unblock further usage immediately. Existing usage is not removed; the higher limit simply allows the entity to consume more within the current period.
4

Set an expiration date (optional)

Under Expiration, set an Expiration date if the budget should stop enforcing after a specific date. Leave it as Never expires for an indefinite budget.
5

Create the budget

Click Create budget. The budget appears in the list immediately and begins enforcing on the next request.

​
Edit or delete a budget

Select the menu on any budget row to:
  • Edit: update the period limits or expiration date. The scope and target cannot be changed after creation.
  • Delete: permanently removes the budget. Enforcement stops immediately.
Budgets can also be created and updated programmatically through the API using a Management Key. Regular API keys cannot manage Budgets.

​
Configure alerts

Alerts notify configured notifiers when a budget’s cost usage crosses a percentage threshold. The gateway performs two separate checks. Before a request starts, it verifies the budget hasn’t been fully consumed. Requests are blocked once usage reaches 100%. Alert thresholds are evaluated after each request completes, which means a notification can lag slightly behind the moment the threshold was crossed. Example: An 80% cost threshold on a project’s budget, notifying the project administrator by email, gives time to react before the budget blocks traffic at 100%.
Alerts track cost usage only; token and requests-per-minute limits do not trigger them. A cost limit is required before adding an alert; Add threshold stays disabled until one is set.

​
Create a notifier

Notifiers must exist before they can be configured in an alert. Create one under Settings > Organization > Notifiers.
Notifiers table showing a Webhook and an Email notifier, each with a Name, Destination, Type, and Updated date.

Notifiers configured in the organization, available for selection in a budget alert.

1

Open the notifier form

Click Notifier.
2

Name the notifier

Enter a Name to identify it in the notifier list.
3

Choose a channel

Select Send via and configure the channel:
4

Save the notifier

Click Create (or Save when editing an existing notifier).

​
Create an alert

The Alerts section is on the budget’s create/edit panel, and on its detail page (open a budget by clicking its row in the Budgets list).
1

Add a threshold

In the Alerts section, click Add threshold.
2

Set the threshold percentage

Enter a whole number between 1 and 100. Each budget allows only one alert per threshold percentage; duplicate thresholds are rejected.
3

Add notifiers

Click Add notifiers and search for one or more already-created notifiers to receive the alert. At least one notifier is required. Each alert allows a maximum of 10 notifiers.
4

Save the alert

Click Add alert (or Save changes when editing an existing alert).
Create alert dialog showing a 90% threshold, a Webhook notifier chip, and Add notifiers, Cancel, and Add alert buttons.

A configured alert with a 90% threshold and a Webhook notifier.

Existing alerts appear as rows in the Alerts section. Select to edit a threshold or its notifiers, or to delete the alert.

​
See also

API Keys

Create and manage AI Gateway API keys with optional spending limits.

Credits

Manage the workspace credit balance, payment methods, and auto top-up.