Reconcile a closed bill against the prices that stood over it.
Zero retention · Bounded when list prices moved mid-month · Evaluating a forward vendor quote? Check single-rate terms at /quote →
At list, the 100,000 priced units of this window cost $800.00, covering every unit that ran. The stated spend of $960.00 is 20 percent above list.
| SKU | Units | List Per Unit | Window List Cost |
|---|---|---|---|
| anthropic/claude-sonnet-5 | 100,000 | $0.008000 | $800.00 |
List prices only: what was actually paid is whatever the bill says. A supplied spend line is compared here and stored nowhere.
Cost only, where no production success rate is recorded at or before the window's end. Cost per successful unit is derived only from a measurement somebody entered, never assumed at 100.
Reconciled in memory with zero retention; supplied vendor invoice lines and usage counts are never stored.
Bounded arithmetic rather than interpolated guesses.
Bounds instead of interpolation
When a vendor changes list prices mid-month and your usage export carries only a monthly total, Vitna reports the exact minimum and maximum list cost bounds rather than assuming uniform daily traffic.
Whole-window coverage rule
A SKU with a coverage gap inside the billing dates is marked unpriced and excluded from the sum rather than silently priced at zero, and whole-window discounts are refused unless 100% of units are covered.
Zero retention by construction
Realised spend and monthly token volumes are bilateral operational data. Both this page and POST /api/v1/reconcile compute in memory and discard the payload on return.
