Skip to main content

Your AI bill doubled.
Can you say why? We can.

Know where your AI coding spend goes

Your bill, split by project, person, task type, and model. Then the seats to cancel and the plans to upgrade.

Product demo: the Quesma usage overview, cost breakdown by project, and suggested changes to agent usage.

When the bill doubles,the reasonslook like this:

Illustrative AI coding usage bill showing token usage and amount due
  • Marketing started using Claude Code

    A team you didn’t expect found a use for the tools.

  • Heavy work with Fable 5

    The default model got smarter, and pricier.

  • Security fixes before the audit

    The work ran hot for three weeks because you asked it to.

Check where your money goes

Every agent session, sized by what it cost and grouped by the work it did: features, investigations, reviews, fixes. Open a cluster to see the sessions behind it.

Explore the live demo

Sessions by task type

Each dot is a session, sized by its cost.

Fix the problems
Find good practices

Cost tools only find things to cut. Quesma also finds problems recurring across teams, and the skills, tools, and routines used in one part of the company but nowhere else.

Patterns worth fixing

Checked in every session, priced by what they waste.

  • Context past 200k$6,784494 sessions, 12%
  • Cache rebuilt after a break$1,583132 sessions, 3%
  • Stopped turns$26090 sessions, 2%

Fix "autoCompactWindow": 200000

Where it costs most

Projects by share of sessions past 200k. Start top right.

$10$100$1,0000%50%100% firmware-reverse: 82 sessions, 10% of the project, $2,744 analytics-platform: 105 sessions, 22% of the project, $2,178 compiler-core: 2 sessions, 33% of the project, $608 edge-collector: 37 sessions, 15% of the project, $353 recomp-toolkit: 5 sessions, 45% of the project, $181 session-replay: 154 sessions, 7% of the project, $115 eval-suite: 3 sessions, 50% of the project, $68 mobile-app: 1 sessions, 100% of the project, $64 marketing-site: 23 sessions, 32% of the project, $61 infra-config: 1 sessions, 100% of the project, $36 search-index: 2 sessions, 67% of the project, $28 bench-harness: 4 sessions, 67% of the project, $16 firmware-reverseanalytics-platformcompiler-coreedge-collector$10$100$1,0000%50%100% firmware-reverse: 82 sessions, 10% of the project, $2,744 analytics-platform: 105 sessions, 22% of the project, $2,178 compiler-core: 2 sessions, 33% of the project, $608 edge-collector: 37 sessions, 15% of the project, $353 recomp-toolkit: 5 sessions, 45% of the project, $181 session-replay: 154 sessions, 7% of the project, $115 eval-suite: 3 sessions, 50% of the project, $68 mobile-app: 1 sessions, 100% of the project, $64 marketing-site: 23 sessions, 32% of the project, $61 infra-config: 1 sessions, 100% of the project, $36 search-index: 2 sessions, 67% of the project, $28 bench-harness: 4 sessions, 67% of the project, $16 firmware-reverseanalytics-platformcompiler-core

How concentrated it is

3 sessions make half of the $6,784 past 200k.

Largest session
$2,625
Top 3 together
$3,486
The other 491
$3,298

Effort by model

66% of the spend ran at high effort or above.

Modellowmediumhighxhighmax
claude-opus-5-5$4,428$4.4k$5,959$6.0k$7$7
gpt-6-astra$56$56$2,267$2.3k$1,761$1.8k$1,377$1.4k$70$70
claude-fable-5-1$30$30$4,633$4.6k$11$11$174$174
claude-opus-5$2,892$2.9k
gpt-6.1-sol$1,116$1.1k$598$598

Bring clarity to your AI coding budget

Early access opens soon. The open-source collector runs in your environment and the session data stays in your cloud. Contact us to be one of the first teams.