Nautili
Documentation

Savings

Savings reporting was retired with prompt compression. What the dashboard shows instead, and the one informational figure that remains.

Savings

The Overview's savings block -- a Subscription panel and a Metered panel, the measured against estimated split, the holdout control arm, effective tokens, "Tokens removed" and "Worth" -- was retired together with prompt compression, the machinery that produced it. The savings RPCs are gone and the fields that carried them are reserved on the wire, so nothing in the dashboard renders a savings figure today.

The reason is on the record. The cost anatomy built to check the claim found that on an agentic bill the uncached input -- the only component a transform could shrink -- is one to three percent of cost, while cache reads are the dominant component. Rewriting prompts never addressed the bill.

What to read instead

  • Where the money goes -- the cost anatomy, decomposed per provider into uncached input, cache read, cache write and output. It is the single most useful thing to read before deciding what to optimize.
  • Efficiency -- waste still on the table: retries and repeated prompts, attributed to people and teams.
  • Trials -- the only path by which a cheaper model becomes a measured claim on your own traffic.

Subscription value is not a saving

The one savings-shaped figure that remains is on the Seats screen: API-equivalent value, what subscription-seat traffic would have billed on the metered API. It is plan-fit context, because nobody pays it on a flat prepaid seat.

Do not read it as a saving. It prices all subscription traffic, not a saved portion of it, and the interface labels it informational, never savings.

Seat-plan cost estimates beside it are likewise a window-prorated public list price applied to observed activity. The gateway cannot tell a departed seat from an idle one -- both are zero requests in the window -- so that figure can overstate real spend when seats have churned. See Seats.

On this page