> ## Documentation Index
> Fetch the complete documentation index at: https://oximy.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Budgets
> Set spend limits and track usage across people and projects.
Open **Sidekick → Spend → Budgets** to cap spend by default, set explicit budgets, and handle requests for more.
## Class default caps
A class default is the cap that applies automatically, before anyone sets an explicit budget. There are two classes:
* **Per person**: a monthly cap, in USD, that applies to each person in the workspace.
* **Per agent**: a monthly cap, in USD, that applies to each agent.
Setting a class default to **0** blocks spend entirely for that class until an explicit budget overrides it.
## Create and update explicit budgets
An explicit budget overrides the class default for one person, agent, or project. Create one to give a specific case more room than the default allows, or less. Updating an existing budget takes effect on the next spend check; it doesn't retroactively change what's already been spent.
## Approve or reject budget requests
When a class default or explicit budget blocks further spend, the person hitting the limit can send a request for more. Requests land in your queue with the amount asked for and the reason it's needed.
Review who's asking, how much, and what the spend is going toward.
Approving raises the budget by the requested amount. Rejecting leaves the existing cap in place and notifies the requester.
## Per-agent cap and rate limit
Beyond the monthly cap, an agent can carry an optional rate limit: a ceiling on how fast it can spend, separate from how much it can spend in total. Use a rate limit alongside the monthly cap when a runaway agent burning its whole budget in a short window is the risk you're guarding against, not just the total.
## Where to go next
Where budget requests appear alongside tool and admin approvals.