Quotas and consumption

Every call to an AI model consumes tokens, and every token has a price. Quotas are the monthly caps the platform applies to that consumption.

Without a quota configured, a scope has no limit. Quotas exist so that a poorly calibrated experiment doesn't eat the whole month's budget.

The scopes

The same consumption is counted at more than one level at once, and each one can have its own cap:

• Organization: the company's total.
• Workspace: a team's or project's total.
• User: how much one person can consume within the workspace.
• Project key: how much a programmatic integration can consume.

You can also cap per provider, when one of them is more expensive than the others and deserves its own ceiling.

The Organization quota takes precedence over the Workspace quota. Once the company's cap is used up, no workspace continues, however much headroom it has under its own limit.

Caps are set in cost or in tokens, and apply to the current month. The turn of the month resets accumulated consumption. A blank field means "no limit"; a limit of zero blocks every request in that scope.

What happens when a cap is exceeded

When consumption goes over the cap, the call is refused and whoever is in Chat gets a quota-exceeded warning. The platform doesn't degrade the answer or switch models: it blocks.

The block applies to the scope that went over. A user who hit their own limit can no longer use the platform, while the rest of the workspace carries on.

Temporary grants

Raising the quota policy fixes the problem of the day and rarely comes back down. For one-off cases there is the temporary grant.

It works like this:

• It adds an extra allowance on top of the current limit, for a set period, with a recorded reason.
• It expires on its own. There is no routine to undo it: the platform simply stops counting expired grants.
• When it expires, the scope goes back to the policy cap and blocks again if the month's consumption has already passed it.

Where to see consumption

Three screens answer different questions:

• Workspace › Dashboard: the workspace summary, with tokens consumed, total cost and usage per Agent.
• Quotas, in the Organization or the Workspace: limits, usage for the month and the projection to the end of it.
• Observability: the per-model detail, with filters and traces for each execution.

The projection on the Quotas screen is the most useful signal mid-month: it shows whether the current pace will exceed the cap before the month turns.

Next steps

• Understand where the per-token price comes from in Providers and models.
• See who can change quotas in Roles and permissions.