Usage & limits

See balances and consumption, configure limits, and understand the current model-spend caveats.

The Usage & limits pane shows usage attributed to your organization and lets an admin cap it — for managed-model spend, and only where a member's gateway enrollment attributes it to the org rather than to them personally.

Scope
Who	Owner or admin only — the pane is admin-only. Members see their own LLM usage in the app sidebar, not here
Applies to	The managed gateway — local work is not metered
Plan	Billing enabled on the organization
Affects	The organization and individual members

What the pane shows#

Balances, a consumption timeseries over the selected range, and a per-member usage drill-down — all live, reflecting usage attributed to the organization as above. This is the admin view of the whole organization; a member's own LLM meter lives in the app sidebar.

Configuring limits#

Each limit is one row. Add an organization-wide row that applies to everyone, or a per-member row for a single person.

Per row, set:

Resource — LLM spend, capped in USD.
Window — Daily or Monthly.
Cap — the amount for that window.
Enabled — a per-row switch; a disabled row is kept but not applied.

Rows take effect when you Save.

Enforcement#

Every applicable enabled limit is evaluated in its own UTC daily or monthly window. Reaching any applicable limit blocks that resource.

Org LLM limits are incomplete today. A configured LLM limit applies only to gateway usage attributed to the organization — not to all managed-gateway usage. Because normal enrollment can attribute spend to a member's personal subject rather than to a shared organization subject, treat org-level LLM budgeting as incomplete today. Usage on your own keys or gateway is outside it entirely.

Two details in how usage is attributed are why:

Normal agent authentication renders a member's personal model-gateway enrollment, not the organization's, so gateway spend is attributed to the member rather than to a shared organization subject.
Which organization a member's usage lands against resolves through the server's current membership, not the org selected in Desktop, so for a member in more than one organization it can attribute to a different org than expected.

Note

The pane manages and stores these limit rows and evaluates them per window. It does not change what a member's own provider keys or a bring-your-own gateway allow. See Model gateways.

What members see when blocked#

When a session can't start for a billing reason, the banner names the cause instead of a generic error:

What members see	What it means
Model gateway unavailable	Gateway-routed model calls are unavailable or have reached their configured budget.
Payment or account needs attention	Managed access is paused until the account issue is resolved.

The member-facing walkthrough of these states is Billing issues.