Usage & billing
Usage & billing is where organization admins see how much agent work costs — model usage, agent runs, cloud compute, and related activity — and set budget policies so spend stays predictable.
This is not where you change your commercial plan or contract. Your plan defines what's included each month; budgets are your internal house rules — how strictly you warn, cap, or stop before spend adds up. Usage works alongside Settings, Model control, and Members.
What this page is for
Usage shows spend and lets admins set budget policies. The same Manage budget dialog also opens from Settings. Your included allowance and commercial entitlement come from your agreement — configured in the Console by operators, not in Usage. If numbers don't match your contract, see Contracts & capacity or Help.
Who can see and change what
If you cannot open Usage, your role may be member only — ask an admin in Members. Members still consume included allowance when they run agents; they just may not see org-wide dashboards.
Why usage tracking matters
Usage works best together with Model control — cheaper defaults and a smaller model catalog often save more than raising the budget alone.
How usage fits together
Think of Usage as the spend dashboard; other modules set the rules that affect what shows up here:
When someone says a run was "blocked for budget," check Usage denials and Model control — both can stop runs, but only model usage drives spend.
In practice
What you see on Usage
Usage rolls up for your organization over a time window you choose. Depending on your plan, you may also break it down by team, project, member, model, or repository.
Policy denials from Model control show up here too — they don't cost money, but they explain why someone couldn't start a run.
When spend jumps after a release, filter by surface first: a CLI or cloud automation change often shows up before you drill into individual members.
Included vs on-demand
Every org summary splits spend into two buckets:
The included allowance comes from your plan. Admins see the same reference line on Usage and in Settings when setting budgets — your internal cap should stay at or below what your plan allows.
What drives spend
Use surface filters (desktop, CLI, cloud) when a spike lines up with a pipeline or automation change.
Set a budget
Budgets are your internal caps — stricter than your plan, never looser.
Open Manage budget
From Usage (budget meter) or Settings → Organization, open Manage budget. Requires admin or super admin. See Members for roles.
Choose a cap
Pick a monthly USD cap that fits your plan and how aggressively you want to control spend. Some orgs use a range cap for a short experiment or release window instead of a full calendar month.
Pick enforcement
Choose what happens as usage approaches the cap:
Many admins start with warn during rollout, then move to soft or hard once caps are tuned and the team knows what to expect.
Save and tell the team
Save — the policy applies org-wide and is audited. If you move from warn to hard stop, warn team leads so CI and cloud automations aren't a surprise.
Hard stop blocks new runs that would incur spend. Scheduled CI or cloud jobs may fail until the cap resets or an admin adjusts policy. Prefer warn or soft stop while pipelines are still being tuned.
Team and project budgets
On larger plans, you can allocate slices of org budget:
Team and project budgets narrow org capacity — they cannot grant spend beyond org policy or your plan.
Monthly check-in
A short admin rhythm keeps spend predictable:
Check included vs on-demand
Is the team living inside Included, or burning On-demand every month? If included runs out early, talk to your account contact about capacity — don't only raise internal budget without plan headroom.
Find the top drivers
Sort by project and model. Common culprits: CI on a heavy reasoning model, a long cloud migration, or a new team without its own cap.
Review denials
A jump in denials may be Model control, not budget — check both.
Tune before you raise
Tighten model catalog, lower a project cap, or switch CLI defaults to a lower-cost model before increasing the org cap.
Export if needed
Download CSV for finance or chargeback when exports are enabled on your plan.
Budgets vs your plan
Budgets are internal house rules. Your plan defines entitlement. You can set budgets stricter than your plan allows — never looser. Entitlement changes go through Contracts & capacity, not Usage alone.