LLM budget management turns a spending allowance into an operating rule: who may spend, on which workflow, over what period, and what happens at the limit. Start with a monetary budget and a named owner, then verify the request path that will apply it. A spending report alone cannot stop a request.
Ownership, request coverage, and the response at the limit belong in the same record.
Set the amount from useful work
Estimate expected task volume and observed model cost per acceptable completed task. Include repeated attempts in the pilot measurement. Estimate connected services and human review separately so model spending does not stand in for the total operating cost.
Fictional example: Cedar Services expects 400 reviewed intake summaries in a month. A pilot measures average model cost of USD 0.20 per accepted summary, including repeated attempts. That gives a USD 80 planning baseline. The owner chooses a hypothetical USD 100 allowance for variation and reviews it weekly. These figures illustrate planning; they are not AgentShelf prices or promised costs.
Write down the currency and the budget period's start and end. Verify how the configured policy represents that period before launch. Do not treat the allowance as a prepaid balance or assume a calendar boundary has reset a limit without checking the active policy.
Choose a scope and owner
AgentShelf supports monetary budgets at organization, team, user, and widget scopes. Organization admins choose hard or soft budgets. Match the scope to the responsibility you intend to assign.
Scroll horizontally to see all columns.
| Scope | Planning question | Owner to record |
|---|---|---|
| Organization | What allowance covers the organization? | Organization budget owner |
| Team | What allowance supports this team's work? | Team budget owner |
| User | What allowance supports this person's use? | Person responsible for the allocation |
| Widget | What allowance supports this website surface? | Website operations owner |
Role and group are not additional budget scopes. Agent and workspace reporting provides visibility, not separate budget enforcement. Token counts can explain usage, but these budgets are monetary limits, not direct token caps. If several scopes apply, verify the policies with the actual request rather than assuming a precedence rule.
Choose the response at the limit
On covered paths with an active policy, a soft limit warns and allows requests to continue. A hard limit rejects covered requests when the applicable limit is reached. A warning signals an operator; it does not by itself authorize or reject requests.
Cedar's organization admin might choose a hard allowance because summaries can wait for a spending review. Another workflow might use a soft allowance so work continues while the owner investigates. Record who reads warnings, who decides on additional spending, and how people handle work that cannot proceed. Soft budgets need an active response owner because spending can exceed the allowance.
Verify coverage before relying on a limit
Supported authenticated workspace and external-agent requests can apply organization, team, and user policies. Supported widget requests can apply organization and widget policies. Enforcement requires a supported request path and an active policy; other paths can continue without a budget check.
Test the real entry point in a controlled pilot. Confirm attribution to the intended scope and verify the configured warning or rejection. Document uncovered paths and assign an operator. A cost record demonstrates reporting, not that a budget check ran.
Review changes before raising limits
Use this launch checklist:
- Name the budget owner, organization admin, and exception responder.
- Record amount, currency, period, scope, and expected workload.
- Confirm the active policy and supported request path.
- Verify soft continuation or hard rejection and the human fallback.
- Review spending, completed tasks, repeated attempts, and quality together.
- Record why an allowance changes and when to review it again.
If Cedar spends faster than expected, check volume, longer inputs, and repeated attempts first. Raise the allowance after the owner understands the change. Read the cost governance framework for the wider process and AgentShelf's budget controls for current product scope.