Tracking usage
Four views of the same ledger, each answering a different question: how much, where, on what, and how much is left.
Who can see it
Usage and billing are organisation-level and reach only owners and admins. Everyone else works against the balance without seeing it, which is why the spend cap and low-balance alert matter on a team — they are the only signals a member gets.
Credit burn
Daily spend, stacked over the period. This is the chart to read when a bill is larger than expected: a single tall day is usually a bulk upload, while a raised plateau is usually a table in auto mode quietly keeping up with documents as they arrive.
Spend by workspace
Which workspace the spend came from, and selecting a row filters the other charts to it. This is the level attribution works at: spend is attributable to a workspace, not to an individual table. If you need a table to be independently accountable, give it its own workspace.
Work volume
What produced the spend, which separates large jobs from expensive columns. Two very different problems can produce the same total: a lot of pages read once, or a modest set of documents asked a lot of expensive questions. The first is an ingest decision — you now own those documents. The second is a column decision, and it repeats every time you rerun.
Balance
The closing balance each day, which is the line to watch for runway rather than for cost. Read with credit burn beside it, it answers the only question that has an operational consequence: at this rate, when does work stop?
Because credits sit in lots with their own expiries, the balance also shows what is expiring and when. A balance that looks healthy can still have a large lot about to lapse.
Purchase history
The billing page lists recent purchases and grants. It is a glance at recent activity rather than an accounting record — for accounting, use the invoice issued for each purchase. Your company details are what heads that invoice; they do not gate the purchase itself.