What did your agents cost last month?

Token spend scatters across providers, repos, and developers. Ask in plain English — the analytics agent answers with a number you can audit, not a guess.

Without the session

The spend is scattered across provider bills.

bills
anthropic console $?
openai console $?
by repo / by dev —

You ask which repo burned the budget. The bills don’t say.

You

Which repo cost the most in tokens last month?

Agent

I can’t tell from here — provider billing isn’t broken down by repo or developer. You’d have to export each console and reconcile it by hand.

no aggregatemanual reconciliation

Provider bills total the spend. They don’t tell you where it went.

With the session

Ask in plain English. Audit the number.

You ask the analytics agent, and it queries your session read model. Each row keeps the query behind it, so the number is auditable.

You

What did each repo cost in tokens last month?

Agent

Last month checkout led at ~$58 (4.2M tokens), then web at ~$16 and infra at ~$5. Each row keeps the query_read_model call behind it.

groundedfrom your read model

With analytics, the spend has a name, a repo, and a receipt.

How it works

The analytics agent turns your plain-English question into a query_read_model call over the projections Capacitor builds from every session — counts, tokens, timings — and answers with a table or chart plus the exact query behind it. It reads aggregates only, never your transcripts. See Analytics.

More ways teams use Capacitor

All features →

Put a number on your agents’ token spend.

Start free and ask your first question — who spent what, on which repo, with which model.

Start free Rather start a conversation? Talk to the team
Built by the team behind KurrentDB — event streams in production are what we do. Coding agents just produce a new kind.
Session recap · yesterday 16:42

Fix flaky auth-token refresh test

Tried mocking the clock first — abandoned after the race persisted. Root cause: token cache TTL rounding. Patched in auth/cache.ts, added regression test. Two approaches rejected, one shipped.

claude-code41 min12.4k tokenscontinue →