Skip to main content

Overview

The gateway meters token usage on completed calls, prices it at per-model rates, updates spend for the window, and enforces every applicable Quota. Limit changes reach the gateway on the next config sync. Refer to Quotas concept for how that differs from spend accrual. Quotas are workspace-scoped records. Each Quota has a subject, a USD limit, a reset window, an optional name, and an enabled flag. Subject identity is fixed at create time. Create is insert-only for each subject identity and window pair. Disabled Quotas remain listed but are not enforced. The typical workflow is:
  1. Set a Quota for the subject that owns the budget.
  2. Optionally set a Gateway Quota when spend should follow a gateway.
  3. Update, list, or remove Quotas as budgets change.

Requirements

Before you begin:
  • Authenticate to Dome and select a workspace
  • Have the subject already configured (agent, model, pool, Gateway, or a subject verified via Delegated agents as needed)
  • Use a plan that allows cost Quotas for the workspace. Cost Quotas are included on the Pro plan. Free workspaces ship with a create limit of zero.

Permissions

Quota operations require platform permissions. Each operation restates its permission inline.

Set a Quota

Create a USD spend cap for a workspace, agent, act-as subject, pool, model, or Gateway (gateway). Subject identity cannot change after create. Pass --disabled / disabled to create a Quota that is stored but not enforced until you enable it. Windows are daily (UTC midnight) or monthly (UTC month start, default monthly). Exhaustion behavior and event names are on the Quotas reference.
Requires gateway.manage.
In the dashboard, open Models → Cost quotas, choose the subject and target, set the USD limit and window, then save. Model Quotas can cover a model globally or only within a selected pool, with an optional per-caller toggle.
Workspace monthly limit
Agent daily limit
Pool monthly limit
Model budget within a pool

Set an Act-As Quota

Create a Quota for one verified end-user subject. The Quota applies only when Delegated agents verification has confirmed that subject on the call.

Set a per-caller model Quota

Create a model Quota that tracks each agent and each verified end user independently instead of combining their spend.

Set a Gateway Quota

Create a Quota that covers all LLM calls routed through a Gateway’s model pools and direct model connections. This is the Gateway-first spelling of the same gateway subject available on dome model quota set.
Requires gateway.manage.

Update a Quota

Update a Quota’s name, USD limit, window, or enabled state. Subject identity cannot change. Create a new Quota to cover a different subject.
Requires gateway.manage.
Only the fields you pass change. Disable a Quota to pause enforcement without deleting its definition or history.
For Gateway Quotas, dome gateway quota update accepts the same mutable fields and refuses non-Gateway Quota ids.
Reference: dome model quota

List Quotas

List Quotas in the workspace, including disabled ones. Listing returns each Quota’s id, subject, USD limit, window, and enabled state.
Requires gateway.view.
The Gateway list can filter to one gateway. It is a client-side filter over the workspace list.

Remove a Quota

Remove a Quota by id. Listing first is the usual way to obtain the id.
Requires gateway.manage.
Remove deletes the Quota definition. Disable the Quota instead when you need to pause enforcement and keep the record.
The Gateway remove command refuses ids that belong to other subjects.

Next steps

  • Quotas concept for how spend caps work
  • Quotas reference for subjects, windows, and event names
  • Pools for routing strategies and failover
  • Delegated agents so Act-As Quotas match live verified subjects
  • Models for the models and pools a Quota can target