GET /v1/costs or the get_costs tool.
Everything here is in dollars. A credit is one cent at list price, so $12.40 of spend is 1,240 credits anywhere that still counts in credits. The gauge, Settings → Money, Cost history, the banner under the composer, Settings → Billing and the API 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.
Cost history
Settings → Money → Cost history shows one billing month at a time. Open it from the Cost history row in the settings menu, the Cost history link under Money → Details or under Settings → Billing → Where the budget went, or by typing “cost history” or “csv” in the search palette.- Month: this month or any of the eleven months before it (a year in all). An older month opens from a link with its
?period=. The month is in the address (?period=2026-09), so a link you paste opens on the same month. - Brand: when your organisation has more than one brand (workspace), narrow the month to one of them. The brand is in the address too (
?brand=). - Tiles: what the month cost against its budget, the month-end forecast (for the current month only; a closed month says so), your plan’s monthly fee, and your balance now.
- By project, By brand (with two or more brands) and By kind of work, with a share bar and each project’s or brand’s cap. The kind-of-work table gives how many pieces were delivered and how many are waiting on you; these are counts, never prices. A line under it splits the month into agent work and data.
- Export CSV downloads the month as it is on screen, narrowed to the brand if you chose one. It is the same document as
GET /v1/org/costs.csv, so its spend rows add up to the totals on the page. - Top up opens the credit purchase.
/costs address is gone; it returns a 404.
The breakdown
GET /v1/costs and get_costs take a month (period, this month by default) and, optionally, one workspace. They return the month’s spend (spent_usd), the forecast (forecast_usd), and the sections below. The budget, the caps, the balance and how it is funded are not in them: those are in Settings → Money and Settings → Billing.
By project
by_work_area: each project’s spend this month. 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’s own monthly cap is set in Settings → Billing.
- Unassigned (a
nullwork_area_id) is a workspace’s spend that no project was named for: chats and the Chief of staff. - Spend from a project that has since been deleted is still listed. The money was still spent.
By kind of work
by_type: spend by what the work produced, with how many were delivered this month (delivered):
not tracked yet (
null) means we do not count that kind of work. It never means zero delivered.
by_kind splits the month by where the money was spent:
agent_work, data, paid_placement and creators are always listed; nothing is charged under the last two today. unattributed appears only when a charge could not be placed.
By workspace
by_workspace: each workspace’s spend, which matters when you have several, as an agency does. A workspace’s monthly cap is set in Settings → Billing.
- Across workspaces (an empty
workspace_id) is spend that belongs to the organisation rather than to one workspace, such as background crawls.
Delivered and waiting on you
by_type lists each kind of work (articles, page fixes, listing fixes, outreach pitches) with what was spent on it and two counts:
These are counts of work, never prices. Work is sold only as credits: each piece is charged the credits it used, and a budget does not commit us to a number of deliverables.
credited_back_usd is what was credited back to your balance for the month under the work guarantee that was retired on 1 November 2026. It is 0 for every month since.
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:- The balance. At zero, nothing new starts. Top up, or turn on auto top-up.
- 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
askas well as automations. - The project’s cap. New work for that project stops, chats filed under it included; other projects carry on.
- The workspace’s cap. Automation runs in that workspace stop, whether scheduled or started by hand. Chats and
askare not held by it.
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.
Reading it from code
GET /v1/costs and the get_costs tool return the breakdown above. Both leave out the budget, the caps, the balance and how it is funded: those are yours to set, in the dashboard.