Infer receipt inspector
Make the charge explain itself.
Paste a completed Infer response or standalone usage receipt. The inspector checks field relationships and recomputes the displayed token charge with integer micro-dollar arithmetic in your browser.
The boundary
An arithmetic check is not an attestation.
The inspector is useful for catching malformed usage, impossible cache counts, a conflicting cache label, or a charge that does not follow the displayed rates. It cannot establish where the JSON came from.
Required customer-visible fields, non-negative token counts, cached input no greater than total input, cache-label consistency, and the rounded token component of the final charge.
Cryptographic authenticity, supplier identity, exact weights or deployment, fallback history, provider billing, wallet settlement, or whether the named price record exists on Infer.
The current standalone receipt exposes token rates but not a fixed per-request rate. A positive difference can be identified, but this page cannot independently explain it.
Documentation fixture
Schema-shaped. Visibly synthetic.
Identifiers are marked fixture_redacted. The token and rate values exercise the same public receipt fields and rounding rule as Infer’s test path. This is not a production receipt, customer traffic, supplier evidence, or proof that a API request ran.
Loading fixture…Inspect a completed live receipt.
Create an account, verify the email address, fund the wallet, and issue a API key. Current model availability remains visible on status.