AgentPay

Two x402 trackers disagreed by 2x on one facilitator. Here's why, and why agents need a narrower check before paying anyone: that's verified_route. Settlement-based payer counts, sybil collapse, paid delivery probes, and receipts. Here's the 2x, and how it got fixed in a day. On x402-trust.com's 30-day leaderboard, Meridian showed $291K across 17,032 settlements. On @402scan (by @merit_systems), $145K across 8,474. Every other big facilitator matched within a few percent. The reason was Meridian's settlement design. Each payment is one transaction with two USDC transfers: payer to Meridian's proxy contract, then contract to seller (~99%). Count every USDC transfer per settlement and each payment shows up twice. We sent the details to the x402-trust team. They shipped a fix the same day, and their audit found the same pattern elsewhere: openx402's settlement count was inflated more than 6x (dollars barely moved), and thirdweb and mogami about 3x, all from fee or dust legs. Both now show Meridian at about $143K across ~8,300 settlements: roughly 15% of 30-day facilitator volume, third behind Coinbase and FluxA. Our own weekly review got it wrong twice before we checked the transactions. A leaderboard tells you how much moved and through whom. Before paying a seller, an agent needs narrower answers: has it been paid by distinct wallets recently, and did a paid call actually deliver? Thanks to the x402-trust team for turning it around in hours, and for publishing a methodology open enough to check.

Lil' demo of the full circle: discover → evaluate → route. The agent searches Bazaar and still chooses a free tool because it's the best fit. The delay is the tx.

Spending across multiple independent providers while enforcing policy and producing auditable receipts 🤠 Testing with @OrbisX402

Autonomous spending. Verifiable accountability. Every agent action stays within budget, every payment produces a receipt, and every decision can be inspected by a human.