Optiak Docs
Administration

Budgets

Set daily, weekly, or monthly API spend limits for your organization, projects, applications, and API keys.

Budgets set USD limits on API spend over a daily, weekly, or monthly period. Choose whether a budget only tracks spend or blocks new Gateway requests when its limit is reached.

Required role

Organization AdminWorkspace AdminProject AdminApp Admin

Applies to

LLM requests
Organization Admins manage organization budgets. Workspace Admins, Project Admins, and App Admins can manage budgets for applications they can update.

Why use it

Set a spending boundary at the level that owns the traffic. Organization budgets apply across the organization; application budgets can add tighter limits for one application or its API keys.

How it works

A budget combines a Scope, a Limit per, a Period, a USD amount, and an action. Scope selects which requests the budget covers. Limit per determines whether one amount is shared across the scope or each project, application, or API key gets its own amount. Period sets how often the amount resets: Daily, Weekly, or Monthly.

Budget spend is based on priced API request usage. See Metrics for how Optiak calculates cost.

Scopes

A budget makes two distinct choices: Scope selects the requests to count, and Limit per determines how the amount is shared across that scope.

Budget

A USD limit, period, and action for API spend.

Scope

Which requests count toward the budget?

  • Organization

    All organization requests.

  • Projects

    Requests from selected projects.

  • Applications

    Requests from selected applications.

  • API keys

    Requests from selected keys.

Limit per

How is the amount divided within the scope?

  • Organization

    One shared limit.

  • Project, application, or API key

    A separate limit for each entity.

For example, an organization-scoped budget with Limit per set to Application gives each application its own cap. An organization-scoped budget with Limit per set to Organization creates one shared cap for all organization traffic.

Track and block

Track only records spend against the limit. It does not block requests or send an alert. Block requests rejects new requests after spend reaches the limit.

Every applicable budget with Block requests is checked. If any one is exhausted, the Gateway rejects the request; a looser budget does not override a stricter one.

For Chat Completions and Responses, the Gateway checks budgets after authentication and before planning. If any applicable Block requests budget is exhausted, it rejects the request with HTTP 403 and error type budget_limit_exceeded.

Set it up

Organization budgets

In the console, open Company setup → Budgets. Organization Admins can set the Scope to the organization, selected projects, or selected applications. Choose Limit per, a Period, enter the USD limit, and select Track only or Block requests. The organization form does not list individual API keys; create organization budgets scoped to specific keys through the API. To cap keys within one application instead, use the Application budget where it belongs.

Application budgets

In the application, open Configuration → Budgets. Users with permission to update the application can set Scope to This application or select specific API keys. For This application, set Limit per to Application for one shared cap or API key for a separate cap on each current and future key. When you select specific keys, each selected key gets its own cap. Choose a Period of Daily, Weekly, or Monthly for the budget. Application budgets can add stricter limits, but they cannot loosen an organization budget that also applies.

Limits and behavior

  • Budgets reset in UTC: daily budgets reset at the start of each day, weekly budgets reset on Monday, and monthly budgets reset on the first day of the month.
  • The organization and each application can each have up to 100 budgets.
  • After creation, you cannot change a budget's Scope, Limit per, or Period in the console. Create a new budget with the desired settings, then delete the old one when it is no longer needed.
  • Enter a positive USD limit with up to two decimal places.
  • Requests already in progress finish, so concurrent traffic can exceed the limit.
  • Spend counting is best-effort. If the counter store cannot be read, the Gateway allows the request; if a spend write fails, the counter may not include that attempt.
  • Budgets apply to Gateway API requests, not MCP Gateway tool calls.
Copyright © 2026