Use case
Developers or team leads using Claude Code, Codex or Gemini CLI who, at month-end settlement or project review, need to turn token consumption scattered across local session logs into a cost breakdown searchable by model, project and date.
Manually checking each tool's usage page, exporting bills into spreadsheets, or skipping accounting entirely and controlling usage by feel.
AI coding spend is buried in subscription or API bills and cannot be attributed per project, so overspend or client settlement cannot be explained and must be estimated.
xOcto's call
Demand is evidenced
Trend: AI coding assistants are now part of daily development, which creates a need to account for model spend per project rather than yet another code-writing tool. Entry: start with outsourcing teams and independent developers running several projects, wiring usage bills into client invoicing or budget alerts; public materials do not disclose pricing, so whether it charges per seat or per project remains unverified.
Reason to use it
Why users would choose it
Compared with opening each vendor's usage page and aggregating by hand, it reads existing on-machine session logs and aggregates by model, project and date, removing the cross-tool copying and conversion step, so developers running several projects who must justify spend to clients or budgets would pick it at settlement time; this is workflow inference from product capability, with no retention or payment evidence yet.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Compared with opening each vendor's usage page and aggregating by hand, it reads existing on-machine session logs and aggregates by model, project and date, removing the cross-tool copying and conversion step, so developers running several projects who must justify spend to clients or budgets would pick it at settlement time; this is workflow inference from product capability, with no retention or payment evidence yet.
Entry and what to borrow
Trend: AI coding assistants are now part of daily development, which creates a need to account for model spend per project rather than yet another code-writing tool. Entry: start with outsourcing teams and independent developers running several projects, wiring usage bills into client invoicing or budget alerts; public materials do not disclose pricing, so whether it charges per seat or per project remains unverified.