Cost & limits
Cost & limits (Administration ▸ Access & Billing) answers three questions for owners and admins, one per tab: what am I spending, what will stop me, and where is it going.
- 1
Overview: what this month has cost
The month’s total, the number of caps currently in force, and how many things are within 20% of one. The figures come from the same ledger your invoice is built from, so this page and your bill cannot disagree. If usage billing is not switched on for your workspace it says so: “used” and “owed” are different sentences.
- 2
Limits: what will stop you, and what enforces it
Every ceiling the server can name, grouped by area (workspace, phone and SMS, email, AI agents, automations and the API), each with its current value, what actually enforces it, and where it is changed. A ceiling marked “shared” is a platform-wide one held in common with every other workspace, not yours alone. The four ceilings that stop an automation (webhook calls a day, actions in one run, steps in a chain, branches from one point) are listed here as well as on the Automations page, because a rule that goes quiet at teatime looks broken rather than capped.
- 3
Spend detail: line by line
Every metered item this month with its quantity, unit rate and amount, adding up to the total on the Overview tab. These are the exact lines an invoice is built from.
- 4
Automatic alerts
When a capped resource crosses 80%, 90% or 100%, owners and admins get an in-app (and, if email is configured, emailed) alert, once per band, so you are warned before you hit the wall rather than spammed.
- 5
Cap AI agents
Set a maximum number of runs, tokens, or dollars, per day or per month, and agent runs stop before the model is called when any of them is reached. All three legs are real: every agent run records its token count and its cost, priced from the model that actually ran, so a dollar cap fires the same way a run cap does. (Until v1.170.0 the dollar leg was stored but never fed - runs reported tokens and zero dollars - and this page said so. The warning retires itself on the first priced run after the upgrade, not before.) Failed and cancelled runs hand their run-count back - you are never billed a per-run fee for a run our provider dropped - though the tokens they really consumed stay on the meter. Chief chat, enrichment sweeps and background watches are not agent runs and are not on this ledger.
- 6
Workspace AI budget (everything else AI)
Separate from agent-run caps, a platform admin can give each workspace a daily AI budget in dollars, or one platform-wide default, under Console ▸ AI ▸ Spend & limits (Manage budgets). It covers every on-request AI helper: Chief chat, briefs and setup blueprints, the writing assistant, the agent builder, agent proposals and enrichment, meeting minutes, AI fields, the document composer and the docs help assistant. Quill’s whole-sentence correction spends against the same budget and is the one thing here that runs without anybody pressing a button, so a workspace that wants nothing spent unprompted switches it off on the Quill page. At the budget those features pause politely until the daily reset, and anything that needs no AI call keeps working. Meeting and call transcription meters its spend into the same budget but never stops a recording already made. No budget is set by default, so nothing changes until one is set; a budget of zero pauses a workspace’s AI deliberately.
- 7
Workspace AI credit (what it costs, not how fast)
The daily budget above is a speed limit: it stops one workspace burning a fortune in an afternoon and it resets every night. AI credit is the separate question of how much that workspace has bought. Every workspace is given a small amount free when it is created, the balance goes down as AI is used at the rate card price, and it is shown on the Billing page in money and as a rough number of questions. A platform admin sets the free starting amount, and whether an empty balance actually pauses anything, in one place. It ships NOT pausing anybody: a workspace that reaches zero today carries on exactly as before, and that will not change without notice. The two limits are independent and both apply: a workspace can be inside its credit and still be stopped by the daily budget, and the messages say which one it was, because a daily budget comes back at midnight and an empty balance does not come back at all. You are warned before it runs out: when the balance drops to the low mark, owners and admins get one notification a week (AI credit is running low, with a link to Billing to top up); a workspace that has never used AI is not nagged, and you can turn the warning off under My notifications.
- 8
Operators: platform totals
Platform admins see an extra “Platform totals, all workspaces” panel with cross-tenant email/SMS/agent spend for the month, so runaway cost across the fleet is visible at a glance. It is labelled as our cost, not any customer’s.
Every cap on the Limits tab is enforced in the database, not in the screen, and each row names the function that enforces it so you can check. The page reports the same money the enforcer compares against: where the two ever differed, the enforcer was moved to match the page, never the other way round. The page is read-only apart from the agent caps, and visible only to owners, admins and platform staff.