Receipts & analytics
Every request produces a signed receipt and a full economic breakdown, including what every rival would have charged.
Most inference bills are a monthly total you take on faith. On Omnious every request settles individually, so every request can be audited individually: a signed receipt for what happened, and a full economic breakdown of the auction that priced it.
The receipt
GET /v1/receipts/:id returns the signed usage record for a request: token counts in and out, the cleared per-token prices, what was authorized, what was charged, the payment and refund references, and the measured time to first token. No prompt, no reply; the router keeps receipts, not transcripts. The record is signed by the router, so it is non-repudiable evidence of what you were charged and by whom.
The economic breakdown
GET /v1/analytics/requests/:id answers the question a receipt cannot: was this a good price? Because the router logs every admitted quote with its TTL, it can reconstruct the exact live book at the moment of any past request and replay the auction you won. The breakdown shows:
- The reconstructed auction. Who competed, who won, and who set the clearing level. Losing rivals appear as stable positional labels in ascending cost, so you see what the market bid without any competitor's exact quote being named.
- Rival counterfactuals. What every other live quote would have charged for your exact token counts, computed with the same billing formula production uses, down to the rounding. These are exact figures, not estimates.
- The second-score premium. The gap between the winner's own bid and what you paid: the price of keeping truthful bidding dominant, disclosed on every request rather than hidden in a spread.
- The fee split. Where each base unit of your charge went: the provider's share and the router's 7% of cleared volume.
Tamper-evident books
A router that keeps its own books could, in principle, rewrite them. Each hour's records are therefore hashed and anchored on-chain at epoch close, and every payment, refund, and payout must reconcile to zero per epoch, checkable by an independent script. A receipt you fetched today cannot be quietly edited tomorrow without breaking the anchor. The full argument is on Tamper evidence.
The Price Advantage Index
Counterfactuals aggregate. If the analytics can price every request against every rival quote, they can also price your history against what a posted-price router would have charged for the same tokens: your running savings from clearing at auction instead of paying a list. That running figure is the Price Advantage Index. The pieces exist today per request and per key: the breakdown above, plus GET /v1/keys/bestex, which compares your fills to the market's token-weighted average price and itemizes the second-score premium you paid. The named, always-on index across your whole history is on the analytics roadmap.
- router/src/analytics.ts auction reconstruction and rival counterfactuals
- router/src/records.ts the usage-record schema behind every receipt