Skip to main content
Org Admin > Usage Limits sets a monthly spending cap for the people and service accounts in your organization. Caps are in US dollars, count spend since the start of the current calendar month (UTC), and reset when the month rolls over. Caps are a safety net against runaway automation and accidental expense, not a billing mechanism — see Pricing for how consumption is charged.

Setting caps

Default monthly limit applies to everyone who has no cap of their own. Leave it blank for no limit. User limits override the default for an individual. Leave a user’s field blank and they fall back to the default (or to no limit, if there is no default). Select several users to set them in one go. Service account limits work the same way. Service accounts follow the organization-wide default unless you give one its own number — worth doing, since an automation can consume far more than a person without anyone noticing. A personal cap replaces the default for that member whether it is higher or lower, so you can raise a cap for one analyst without lifting it for everyone.
When someone reaches their cap they cannot start new agent turns until the month rolls over. Lowering a cap below what a member has already spent this month blocks them immediately.
Changes are staged until you click Save. Until then, the status boxes preview your unsaved changes and show how each count would move.

Reading the status

The page shows three boxes for users, and three more for service accounts. Each box counts the capped members in one state:
  • have reached their monthly limits — at or over the cap; no new turns until the month ends.
  • are projected to exceed their monthly limits — on pace to hit the cap before the month is out.
  • are projected to stay within their monthly limits — on pace to finish the month under the cap.
Click Show users (or Show service accounts) on a box to list the emails behind its count, starting with whoever has used the highest percentage of their cap. Members with no cap are left out of the boxes. A note below them gives the count, for example “4 users do not have a monthly limit and are not included above.” The page doesn’t show individual spend. To see each capped member’s spend so far, percent used, and projected month-end percent, use get_spend_caps over MCP.

Seeing what was actually spent

Org Admin > Usage reports consumption across your whole organization:
  • Range — choose Reporting period to pick a listed period, or Date selector to pick your own dates (with Last 7 days and Last 30 days presets).
  • Overview — the Organization Summary tiles: Total Users, Agent Users, Data App Users, Agent Turns, and Data App Views.
  • User Breakdown — activity and spend for each user.
  • Data App Breakdown — views and users for each Data App.
  • Cost — what the period cost, broken down the way your contract is billed.
The report always covers every workspace; there is no workspace filter. Caps use their own month-to-date spend measure, so a member’s spend on this report won’t necessarily match what counts toward their cap.

Seat limits

Seat limits are a different control: they come from your contract and cap how many people can hold each role. They are shown under Org Admin > Users, not on the Usage Limits page, and changing them is a contract change. See User Management & Roles for assigning the roles themselves.

From your own tools

Org admins can manage all of this over MCP instead of the web app — get_spend_caps and set_spend_caps for the caps, get_usage_report for the usage report, and get_seat_limits for the contract limits. The tools are told to confirm with you before changing a cap. See Org admin tools.