Skip to main content
Use Reports → Agent usage to find where a cost increase came from, then inspect the agent and its runs. You need access to Reports and traced agents in the scope you want to compare.

​
Match the scope

  1. Open Reports → Agent usage.
  2. Choose the workspace scope and time range. Use the same scope when comparing figures with a profile or another report.
  3. Check What changed for spend, runs, active agents, span error rate, and cost per run.
A larger billable workload can increase spend while cost per run stays flat. Compare run count and cost per run before investigating model prices.

​
Find the agent

  1. Sort the agent table by spend or cost per run, or search for an agent by name.
  2. Compare Tokens / run and Span error rate with cost. More tokens can come from longer context, more model calls, or retries.
  3. Open the agent and select Usage.
  4. Review its model, tool, and cache breakdowns, then open a run from Recent runs.
In the full trace, check whether one expensive model call, repeated tool failures, or repeated context explains the change.

​
Check how the run was priced

Open Models & rates and find the model and workspace used by the run. Check whether its price comes from negotiated rates, a seller discount, or a public list price. Cache reads and writes have separate rates. Rates apply when telemetry is priced. Editing a rate does not recalculate existing runs. A name without a matching configured model may use a public estimate; an unknown price is marked Unpriced. See How run cost works.

​
Verify the result

After changing the application or its rates, send new runs and compare them over the same scope. Check answer quality with evals as well as cost: fewer tokens alone do not show that the agent still meets the task. For the definitions behind the charts, see Usage and cost measures.