Skip to main content

​
FinOps

Agent Registry calculates a cost for every recorded run at the rates your organization pays. Use it to compare agents on the same basis and to tell a contract price from an estimate.

​
How a run is priced

Agent Registry prices each run as its trace arrives. It reads the token counts on the trace and multiplies each by the matching rate for the model.
Token counts come from the model provider’s response. Rates come from Models & rates. 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 that are already priced.

​
Where the rate comes from

Rates are set per workspace, per model. For each of the four rates, the first source that applies wins. List price unavailable means Agent Registry could not look up the public price at that moment. It does not mean the model has no price. Only an Org admin can change rates. Every member can view them in Models & rates.

​
Read a cost figure carefully

  • Check how a model is priced in Models & rates before comparing costs. A List price cost is an estimate; Negotiated and Seller discount costs reflect your contract.
  • Cache tokens are priced differently from plain input tokens. A run that reads a large cache can show a low cost and a high token count.
  • Cost per run is an average for the selected period. Compare it with run volume before treating a change as a trend.
  • A value shown as unavailable means the report could not read its source. It is not a zero.

​
Availability

​
Learn more

Models & rates

Connect a LiteLLM proxy and set the rates your organization pays.

Agents usage

Compare spend and cost per run across agents.

Agents

Inspect an agent’s profile, sessions, usage, and recent runs.

Traces

Verify that execution evidence reached the intended scope.