Ledger verifier
Check the chain yourself.
Re-derived in your browser. Nothing is sent anywhere.
- claude-sonnet-4-5$0.146862—Deriving
- claude-sonnet-4-5$0.145392—Deriving
- claude-sonnet-4-5$0.077398—Deriving
- gpt-4.1-nano$0.000049—Deriving
- claude-sonnet-4-5$0.170979—Deriving
- claude-sonnet-4-5$0.073132—Deriving
- claude-sonnet-4-5$0.189384—Deriving
- claude-sonnet-4-5$0.164490—Deriving
- claude-sonnet-4-5$0.063947—Deriving
- claude-sonnet-4-5$0.075856—Deriving
- claude-sonnet-4-5$0.132441—Deriving
- claude-sonnet-4-5$0.082800—Deriving
Deriving.
The published recovea-chain-v1 recipe over the sample month’s ledger. Field order in the docs.
An armed cap refuses the request before it reaches your provider, and answers 402.
Designed to fail open: if the gateway degrades, traffic goes straight to your provider. The only stop is a cap you armed.
Read the contract- 402
- insufficient_quota
- budget_exceeded
- 580 of 580Probes answered 200 while a bad deploy rolled itself back. One drill, one service, not an availability claim.
- 8m 42sTime for a deliberately broken revision to trip the alarm. It rolled back 43 seconds later.
- 41 rowsProduction receipts exported and re-derived outside our systems. The chain head matched.
Take the ledger and check it without us.
Export the chain and verify it offline, with a tool that has none of our code.
Download the ledger — 75,037 rows. Regenerate the month from seed 20260831, hash it under the recipe, and the head is ed6c…0e57.