Skip to main content
FinOps puts a cost on every agent run from the traces your agents already send. Pricing needs no provider keys, billing access, or invoices: Atlan Trident prices each model call from its model name and token counts, then rolls cost up by run and agent for the workspace you choose. Compare agents over the same period, open the costly runs, and check the rates behind each cost. A run’s cost is each model call’s tokens times its rates, summed over the run; see How cost is calculated. Each rate has a price source: Negotiated, Seller discount, or List price. In a trace, a priced cost is tagged Customer price or Estimate: whether it was worked out from your own price or the public list price. A call with no rate is Unpriced: its cost reads zero, which does not mean free. Fresh input, output, cache reads, and cache writes are token categories, each priced separately.

From first trace to your own rates

1

Send traces

Bring an agent into Atlan Trident and send its traces with the atlanai SDK or an OpenTelemetry exporter. Its runs are priced at public list prices as they arrive and tagged Estimate. A model with no public list price stays Unpriced until you enter a rate for it.
2

Or route calls through Model Gateway

Model Gateway prices every call it serves with the same rules, and its usage views show spend by model, person, and agent without any tracing code. The models on the deployment’s own provider — what the provider grid shows as Built in — are the exception: your seller discount doesn’t apply to their calls, and you can’t change their rates. See Review model usage. Gateway usage and FinOps reports are separate records, so don’t add them together.
3

Enter your rates

When you want costs at what your organization pays, an organization admin opens Model Gateway studio, under Spend › Rates and discounts. Layer the discount each provider gives you on top of its list prices, or enter negotiated rates per model; a negotiated rate wins over the discount. Runs recorded afterward are priced at those rates and tagged Customer price; runs already recorded keep their cost. See Set model rates and discounts.

Core offerings

Compare agent usage

Compare spend, runs, tokens, and errors across agents.

Investigate agent cost

Open Reports → Agent usage, find the agent behind a spend change, and check how its runs were priced.

Understand run pricing

See which rate prices each model call and where admins set negotiated rates and discounts.

Read cost measures

Interpret tokens, cache use, and averages correctly.

Choose where to start

FinOps reports what your agents spend with model providers. For what your organization pays Atlan (plan, usage, and payments), see Manage billing. Costs come from traces and your configured rates: a List price cost is an estimate, and Atlan Trident does not reconcile any cost with your provider’s invoice. A rate change applies to runs recorded afterward; existing runs keep their cost. Reports cover only runs that reached Atlan Trident and that you can access, and a value shown as unavailable is not zero. Only an organization Admin can change rates; every member can view them.

See also

  • Trace attributes: The model, token, and cost keys Atlan Trident reads from spans.
  • Public API: Agent, skill, and user trace statistics queries.