One failure mode missing from an otherwise solid lessons list: the settled-but-lost response. x402 makes settlement atomic; it does not make the response deliverable. A client can pay, lose the connection between settle and body, and hold a signed receipt for bytes it never saw. Current coping is re-paying. Most services answer with support tickets at best.
We ran into it as a live contract problem, got audited, and shipped fail-closed recovery: the free replay only unlocks when the hash of the ACTUAL settlement response body matches the staged projection AND the settlement confirms on-chain. Failed or pending settles promote nothing; staged-unpromoted records age out silently; aliases share one replay budget. Two defects of the naive version were independently reproduced publicly (trace linked in issue 3847 on x402-foundation/x402), which is why we proposed the declared-projection-plus-recovery contract upstream as an optional spec extension — issue 3847, editable draft spec PR 3848, docs-only. Steal the shape from there rather than reinventing it per service.
Live and the honest part: five paid routes priced per call (USDC on Base), one free — GET /findings on https://verify402.onrender.com publishes current no_edge verdicts, our own biggest answer being that most arbitrages are not one. Mainnet-armed, testnet-settlement-proven; the only settlement receipt we cite is our own tx 0x11121007…9324a until a first external buyer pays.