Skip to main content
Agent Registry prices every recorded run at the rates your organization pays, so you can compare agents on the same basis and tell a contract price from an estimate.

​
Run pricing

When a run’s trace arrives, Agent Registry multiplies each token count on the trace by the model’s matching rate:
Token counts come from the model provider’s response. If Agent Registry cannot price a run, the cost shown is the one reported with the trace. The cost is fixed when the run is recorded: changing a rate later does not change runs already priced.

​
Rate sources

Rates are set per workspace, per model, in Models & rates. For each of the four rates, the first source that applies wins: List price unavailable means the public price could not be looked up at that moment, not that the model has no price. Every member can view rates; only an organization Admin can change them.

​
Where costs appear

  • Reports → Agent usage: Spend and cost per run across agents. See Compare agent usage.
  • Agent profile → Usage: One agent’s spend and recent runs.
  • Models & rates: How each model is priced. See Models & rates.

​
Example

An organization negotiated input and output rates for one model but not cache rates. Models & rates shows it as Negotiated · partial: input and output use the negotiated rates, and cache reads use the seller discount. A run that reads a large cache shows a low cost beside a high token count, because cache reads are priced lower than plain input.

​
What run cost does not tell you

  • Your invoice. Costs are computed from traces and rates, not matched to the provider’s bill. A List price cost is an estimate; Negotiated and Seller discount costs reflect your contract.
  • Past runs at new rates. Changing a rate affects only runs recorded afterward.
  • Missing data as zero. A value shown as unavailable could not be read; it is not a zero.

​
See also