A truth service has to apply its own standard to itself. This page lists every claim the project makes and the public evidence behind it — including the claims that are still false.
Eight exact-x402 payments have settled in real USDC to the payee. Six are the operator's own calls — two 0.03 USDC route settlements on 2026-11-18 and four calls to the other paid routes (0.05, 0.10, 0.05 and 0.05 USDC). Two are outside payments of 0.03 USDC each on 2026-11-19, from wallets the operator does not control. The outside payers look like automated x402 agents; the receipts are public.
The four other operator calls are at blocks 59,157,271–59,157,334; the activity page lists every on-chain transfer the index has seen.
Proven on-chain, earlier: one testnet settlement
A payer paid, the seller received, and the verdict travelled inside the settlement receipt. It was the operator's own funds on the testnet — the scope of the proof.
The activity page lists this call and the three later testnet calls read live from the chain, with explorer links.
Receipt
0x11121007…a9324a
Base Sepolia · payTo 0xAeEF086DD4e436c69d6d0F684b4c9F43392df9cb
Audited. It lost.
An independent agent built a harness against the source and publicly reproduced two defects in the paid-recovery contract: recovery was recorded before settlement success, and a companion alias could borrow a second budget. Both were verified against the source and fixed the same day; the companion alias was later removed entirely because a public content hash must never be a replay credential. The regression tests remain in the suite.
The audit trace: public harness, public failure
The gist runs against commit cd59b105 and shows the naive contract returning 200 where it should have stopped at the paywall.
The fix: fail-closed, then re-tested
Commit 4bf3c9c: settlement stages inert, promotion only on the official onAfterSettle hook matched on the actual response bytes; one projection everywhere; per-operation replay cap. Suite 34/34.
Proposed, not adopted: an x402 extension
The recovery contract was written up as an optional extension to the x402 spec: declared evidence projection plus settled-response retry recovery, with the fail-closed rule as the normative core. It is a proposal, not a standard.
Two outside wallets have paid for a call — 0.03 USDC each, from automated x402 agents. The free tier and the RPC calls are operator-funded. The first outside payments are recorded above, with their transactions, on the day they landed.
The numbers to check before believing the ledger: a paid call counts only when the payer is not the operator; a repeat payer is an outside payer with two or more settled calls; a disputed verdict is one a payer formally contested with evidence. Counts come from settlement records reviewed by hand, so a zero month stays visible instead of being quietly dropped.
Month
Outside paid calls
Repeat payers
Disputed verdicts
Records checked
2026-10 (from 19 Oct)
0
0
0
2026-11-10
2026-11 (to 10 Nov)
0
0
0
2026-11-10
2026-11 (11–19 Nov)
2
0
0
2026-11-19
First published 10 November 2026, after the 1 November date first promised in public. The first outside payments landed on 19 November 2026; both transactions are above. This table is maintained from reviewed settlement records, not read from a dashboard, so a zero month stays visible.
Reproduce it: don't trust this page.
Everything here is public: the source, the tests, the chain. The suite runs offline against recorded fixtures, and the settlement is on a public explorer.