Quotas

This page lists subject types and exhaustion behavior, reset windows, model Quota options, and audit event names. For how spend caps work, see the Quotas concept. To create and manage Quotas, see Set Usage Limits.

Subjects

Subject	What the Quota covers	Exhaustion behavior
Workspace	Aggregate governed LLM usage in one workspace	Rejects affected calls with HTTP `429`
Agent	Calls made by one agent	Rejects that agent’s affected calls with HTTP `429`
Act-as	Calls made under one verified end-user OIDC subject	Rejects that subject’s affected calls with HTTP `429`
Gateway	Every LLM call routed through one Gateway	Rejects calls through that Gateway with HTTP `429`
Pool	Every call routed through one model pool	Rejects calls to that pool with HTTP `429`
Model	Calls dispatched to one model, globally or within one pool	Removes the exhausted model from pool routing when another member remains; otherwise rejects with HTTP `429`

A model Quota can also use per-caller scope. Each agent and each verified end user then receives an independent budget against that model. Quota scope is cumulative. A request proceeds only when every applicable limit has remaining budget.

Windows

Cost limits are stored in micro-USD. CLI, MCP, and dashboard expose them in USD. On the API, 1000000000 micro-USD is $1,000.00.

Window	Reset
`daily`	UTC midnight
`monthly`	Start of each UTC calendar month

The default window on create is monthly. One Quota may exist for each subject identity and window pair.

Model Quotas

A model Quota can be global, limited to one pool, or per-caller:

Option	What it counts
Global	Direct calls and calls through every pool
Within one pool	Only dispatches from that pool
Per-caller	Separate counter for each agent and verified end user

Exhausted within-pool model Quotas spill to another eligible pool member when one remains. Direct exhausted model calls do not spill. Refer to Quotas concept.

Observability

Event	When it fires
`llm.model_call.completed`	Completed model call with token counts
`access.denied` with `QUOTA_EXCEEDED`	Quota exhaustion (includes exhausted subject type)
`llm.quota.created`	Quota created
`llm.quota.updated`	Quota updated
`llm.quota.deleted`	Quota deleted

Next steps

Create Quotas from the how-to. Routing and Act-As subjects show up in pools and delegated agents:

Quotas concept for cumulative scopes, spillover, and passthrough
Set Usage Limits to create, update, list, and remove Quotas
Pools for routing strategies and failover
Delegated agents for Act-As subjects
Events reference for the broader audit catalog

Get started

Core concepts

Connect

Govern

Operate

Manage

Develop

Reference

Subjects

Windows

Model Quotas

Observability

Next steps

​Subjects

​Windows

​Model Quotas

​Observability

​Next steps

Subjects

Windows

Model Quotas

Observability

Next steps