Verify in browser
The verifier page takes a receipt as a file, as pasted JSON, or by trace_id. The receipt is not uploaded anywhere for checking. The page fetches the public key and the proof from the gateway, and the anchor from GitHub.
Every successful, billed call through honest-router returns a receipt. This page says what is in it, what a verifier checks, and where the checks stop.
| Field | Meaning |
|---|---|
trace_id | Identifier of the call. It starts with t_. |
requested_model | The model slug you sent. |
resolved_provider | The provider that answered. |
upstream_model | The model name the gateway sent to that provider. |
request_commit_hash | A hash that commits to the bytes of your request. |
response_metadata_hash | A hash over metadata of the response. |
signing_key_id | The gateway key that signed the receipt. |
trace_signature | The Ed25519 signature. |
prev_trace_hash | The hash of the account's previous receipt. The receipts of one account form a chain. |
The receipt arrives in the response body as _a2auth.receipt and in the X-A2Auth-Receipt header. A streaming response carries it in the last SSE event. Anyone can fetch it again with GET /v1/receipts/<trace_id>; no key is needed.
The receipt is signed with Ed25519. The matching public key is published at /.well-known/honest-router-pubkey.
The receipt commits to the exact bytes of your request through request_commit_hash.
The gateway groups up to 1,024 receipts into a batch, computes one root hash for the batch and signs it. The verifier checks that your receipt is in the batch. The proof exists once the batch has closed, which takes up to 5 minutes.
Each batch root is published to two independent places: a GitHub repository and the Software Heritage archive. The verifier compares the root with both.
The anchor check has limits. It does not show that the commit is still on the branch today, and the GitHub repository belongs to the operator of the gateway, which is us.
The verifier page takes a receipt as a file, as pasted JSON, or by trace_id. The receipt is not uploaded anywhere for checking. The page fetches the public key and the proof from the gateway, and the anchor from GitHub.
honest-verify checks a receipt from a terminal. With --pubkey-hex and --no-external it makes no request to GitHub or Software Heritage.
You receive both tools with early access.
The gateway stores hashes of the request and the response, not their content. One exception: for some requests sent with an Idempotency-Key, it keeps the first response, for 14 days by default. The provider you call receives your request body; what it does with it is governed by that provider's terms.