Use case
Developers or team leads using Claude Code, Codex or Gemini CLI who, at month-end settlement or project review, work with token consumption records scattered across local session logs of several tools, and need a cost breakdown attributed by model, project, date and activity.
Manually opening each vendor's usage page and copying numbers, exporting bills into spreadsheets, or skipping accounting entirely and controlling usage by feel.
AI coding spend is buried in subscription fees or API bills and cannot be attributed per project, so overspend or client settlement cannot be explained and must be estimated by feel; with several CLI tools, each vendor's usage page must be checked separately.
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, and it requires no account, no API key and keeps data local, so developers running several projects who must justify spend to clients or budgets and care about logs not leaving the machine would pick it at settlement time; this is workflow inference from product capabil
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, and it requires no account, no API key and keeps data local, so developers running several projects who must justify spend to clients or budgets and care about logs not leaving the machine would pick it at settlement time; this is workflow inference from product capabil
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.