A budget caps how much can be spent in a period and blocks requests when the limit is reached. You can set budgets at the organization or workspace level, and narrow them to specific members or providers when you need finer control.
For the click-through to create one, see Set a Budget.
Scope: where the budget applies
Every budget has two scope dimensions.
Level
Organization caps spend across the whole organization.
Workspace caps spend within a single workspace.
Applies to
Overall is one total cap for everything at that level.
Members caps all members, or one specific member.
Providers caps all providers, or one specific provider.
Combine the two to get a specific scope.
Organization > Overall: total organization spend cap
Organization > A specific member: cap one person's spend across all workspaces
Workspace > All providers: cap spend on every provider used by that workspace
Workspace > A specific member: cap one contributor's spend within one workspace
Each budget is enforced independently. If a workspace has a $500/month overall cap and one member has a $100/month cap inside that workspace, both limits are checked on every request. The first budget to run out blocks the request.
Period: how often it resets
Daily | Resets every day at UTC midnight. |
Weekly | Resets every Monday at UTC midnight. |
Monthly | Resets on the first of the month at UTC midnight. |
All resets are automatic. No cleanup is required.
Enforcement
When a budget is exhausted, Otari blocks matching requests until the next period starts.
Existing in-flight requests complete normally. New requests at or above the cap fail until the next reset.
Status indicators
š¢ Green (0-80%) | Healthy. |
š” Yellow (80-100%) | Approaching the limit. |
š“ Red (100%+) | Exhausted. Matching requests are blocked until reset. |
Limit types
Spend limits are defined in USD. Budgets can also cap tokens and request count.