Ledger
What it cost, and what it would have cost. Every call, priced twice.
A cost-reduction tool that cannot show its work is asking for faith. The Ledger is the answer to "prove it".
Two numbers per call
For every request through the Gateway, Operant records the real cost — provider, model, token counts, cache hits — and a counterfactual: what the same call would have cost had it gone to the model your code originally named, with the context you originally sent.
The difference is the saving. Aggregated across a workload, it is the number the Ledger reports.
What the second number is, and is not
The counterfactual is an estimate computed from a stated methodology. It is a good-faith one, and it is not a guarantee, not a warranty, and not a billing basis unless an order form makes it one. Clause 9 of the Terms says so in the language that matters.
What else it carries
- Spend and call counts per API key, so a runaway job has a name.
- Cache-hit rates — usually the first place a bill is leaking.
- Per-workload breakdowns, which is how a repetitive workload becomes visible as a candidate for Cortex.
Book a waste audit and we will read yours with you.