What the number actually is
Token counts are not bills. A useful cost tracker says which figures came from the provider and which were estimated from token mix and bundled pricing. UsageAtlas labels estimates as estimates.
That is enough to see which model carried the week, and whether today is expensive against your own baseline. It is not enough to close the books.
Tokens, cache, and model share
Spend follows fresh input, cache reads, cache creation, output, and the models behind them. UsageAtlas keeps that breakdown next to the headline so a spike has a cause.
History plots load and tracked cost day by day. Filter to one tool when you need to attribute the spend.
Questions, answered
Can UsageAtlas estimate AI coding cost from tokens?
Yes. When a supported tool does not report a cost, UsageAtlas estimates one from token counts and bundled pricing.
Is tracked cost my actual bill?
Not by itself. Use provider billing records for purchasing or accounting.
Which tools are in the cost total?
Every connected supported source. Currently Codex, Claude, Cursor, and OpenCode.