Budgets and credits

Seats pay for the office: the Inbox, approvals, the activity log and roles. Credits pay for the work: model turns, browsing minutes and tool calls that cost money. One credit is roughly one step of work. A typical delegation uses between eight and thirty.

What each plan includes

Extra credits cost $10 per 250 on any plan.

Three kinds of cap

Per delegation

Set in the composer. The run stops at the cap and files a checkpoint. It never finishes quietly over budget.

Per agent

A ceiling for one member of staff across its runs, set on the agent's page.

Per workspace

An owner-set ceiling below the plan's own limit.

What happens at the cap

At 80 percent of a delegation's cap the agent files a budget checkpoint: here is what is done, here is what is left, raise the cap or accept what is here. At 100 percent it stops. The card in the Inbox reads: Stopped at the budget cap. Raise it or accept what is here.

Cost per step

Every step on the Progress timeline shows its own cost. The delegation's total is on the list, in the detail sidebar and on the Home tile for spend this month. Totals update in the same transaction as the ledger, so the number you see is never behind.

Workspace limits

At 80 percent of the included credits a banner appears and admins are notified. At 100 percent plus any purchased balance, new delegations are refused. Runs already going finish their current step, then raise a budget checkpoint. Nothing is cut off mid-step.

Why costs are visible

A runaway loop is a defect, not a revenue line. Caps stop it; visible per-step cost teaches tighter briefs. Routine steps such as parsing and classifying run on cheaper models where they pass the template's checks, and the estimate in the composer already reflects that.

Preview: no credits are metered and no charges are made in the current build. The figures above match the pricing page and apply when billing opens.