A long request should leave a readable bill.
This is a synthetic example of the fields AIWave exposes for review. It is not a customer record and contains no production request ID.
All request fields are emphasized.
Repository analysis · synthetic run
Separates the full prompt footprint from the completion. The real version lives in the Console request record.
Shows the repeated prefix that used the cache-hit rate. The real version lives in the Console usage ledger.
Makes the uncached portion visible instead of blending it into one input number. The real version lives in the Console usage ledger.
Shows the completion charge basis. The real version lives beside the response usage fields.
Ties the charge to the exact route tested. The real version lives in the request record.
Anchors the event in time for a review. The real version lives in the Console activity view.
Explains the multiplier applied to the base rate. The real version lives in account and token settings.
Lets an operator trace one event without guessing. The real version lives in the Console request detail.
Adds the visible classes into one reviewable amount. This sample uses the dated VIP ×1 snapshot rate.
300K × input + 700K × cache hit + 12K × output · VIP ×1The total is calculated from the AIWave pricing snapshot used by /pricing on 2026-08-27; reconcile against the live rate card before relying on it.
What the record gives an operator.
A ledger is useful when it answers a question without another spreadsheet: what ran, which route handled it, how much context was reused, and why the charge has this shape.
Request evidence before expansion