Skip to main content
The Costs page answers one question: what has this month cost, and where did it go. Open it from the spend gauge in the top bar of every screen. Everything on it is in dollars. A credit is one cent at list price, so $12.40 on Costs is 1,240 credits anywhere that still counts in credits. The gauge, the Costs page, the banner under the composer, Settings → Billing and the CSV export all read the same figures, so none of them can disagree with another. A month here is a UTC calendar month: it starts at 00:00 UTC on the 1st. Billing, the budget and the workspace and project caps all count the same month.

​
The spend gauge

The gauge sits at the top right of every screen and shows this month’s spend against your budget.
  • Below 80% of the budget it is neutral: spend is a number, not an alarm.
  • From 80% it turns amber and says how much of the budget is used.
  • When the budget is reached (110% of it if you allow 10% over) it stays amber and says new work is paused.
  • With no budget set it shows the month’s spend and Set a budget.
It opens Costs in every state. Nothing is drawn until the month has been read, so you never see a $0 that is only a page still loading. Under the composer, a banner appears when the month reaches 80% of the budget, with the month-end forecast and a link to Costs; you can dismiss it. When the budget is reached the banner says new work is paused, including the chat you were about to start, and offers Raise budget.

​
What the page shows

Choose This month or Last month at the top. Export CSV downloads the month, and Top up adds to your balance.

​
The four numbers

When a budget is set but nothing can fund it, a line under the tiles says so: Add a card so your budget can fund work when there is no card on file, or that auto top-up is off. Until then, work stops when the balance runs out, before the budget does.

​
By project

Each project’s spend this month, its share of the total, and its own monthly cap if it has one. A project is a piece of work inside a workspace with its own crew of agents; the API calls it a work area (work_area_id). A project whose new work is stopped for money (the budget, its workspace’s cap or its own cap) is marked Paused.
  • Unassigned is a workspace’s spend that no project was named for: chats and the Chief of staff.
  • Removed project is spend from a project that has since been deleted. The money was still spent.

​
By kind of work

Spend by what the work produced, with how many were delivered this month: not tracked yet means we do not count that kind of work. It never means zero delivered. Below the table, Where it went splits the month by where the money was spent: A line with nothing on it this month is left out.

​
By workspace

Shown when the month’s spend falls on more than one line: several workspaces, as an agency has, or one workspace beside spend that belongs to none. Each workspace’s spend and its monthly cap.
  • Across workspaces is spend that belongs to the organisation rather than to one workspace, such as background crawls.
  • Removed workspace is spend from a workspace that has since been deleted.

​
Committed vs delivered

When a budget is set, it commits us to a volume of work for the month, and this table holds us to it. For each kind of work: How the credit is worked out is on Plans.

​
Ad spend

Ad spend is shown on its own line under the tables. It is paid to the ad platform directly, so it is never part of your spend, your budget, any share bar or any total on this page. With no ad account connected, the line reads Not connected.

​
How the forecast works

The forecast is a straight line you can check by hand: the month’s spend so far, divided by the days elapsed, times the days in the month.
  • It is blank for the first three days of a month. Too few days make a line a guess.
  • For a month that is over, the forecast is what the month cost.

​
Caps

A budget bounds everything the organisation spends in a month. Below it, two caps stop one part of the account from spending another’s share: Every cap is a monthly dollar amount, and a cap of zero means no cap. A workspace cap is the same value as the workspace’s monthly credit cap, shown in dollars rather than credits. A cap counts everything charged to its scope in the month: agent work and the data reads it pays for. Daily prompt readings use your plan’s response budget, not credits, and are not counted. Only an organisation admin can change the budget or a cap, from the dashboard. An agent cannot change them, and neither can an API key or an MCP connection: an agent that needs more room has to ask you.

​
When a cap or the budget is reached

New work is checked against each wall before it starts, never while it runs. In order:
  1. The balance. At zero, nothing new starts. Top up, or turn on auto top-up.
  2. The budget. Once the month’s spend reaches the budget, nothing new starts until you raise the budget or the month turns. This holds chats and ask as well as automations.
  3. The project’s cap. New work for that project stops, chats filed under it included; other projects carry on.
  4. The workspace’s cap. Automation runs in that workspace stop, whether scheduled or started by hand. Chats and ask are not held by it.
A run already under way always finishes and is charged in full. So a month can pass a budget or a cap by at most one run, and runs that start at the same moment can each pass on the same reading. When scheduled work is stopped, the workspace gets one row in the Inbox for that wall, and one email. The budget’s row and a project’s row carry a Raise cap button that opens the setting. The row closes itself when the work runs again. Topping up does not lift the budget or a cap; raising it does. The full list is on Credits.

​
Pausing at the budget

Under Settings → Billing → When the budget runs out, choose what happens at the budget:
  • Pause and ask me (the default): new work stops at the budget.
  • Allow 10% over: new work keeps starting until spend reaches 110% of the budget, then stops.
This changes where new work stops. It does not change the commitment, which is always worked out from the budget itself.

​
Export

Export CSV downloads the month as one spreadsheet built from the same figures as the page. Each row names its section in the section column: total, by_project, by_workspace, by_kind, by_type, committed, credited_back or ad_spend. Amounts are in whole cents (spent_cents) and in dollars (spent_usd). The spent_cents of each spend section (by_project, by_workspace, by_kind, by_type) adds up to the total row. Committed work, credits back and ad spend are rows of their own and are never part of that total. To read the same month from your own code or an assistant, use GET /v1/costs or the get_costs tool. Both leave out the budget, the caps, the balance and how it is funded: those are yours to set, in the dashboard.