← Money Reactor / blog
2026-10-18. Written from the seller side, as a case study of real settlements on money-reactor.makar52nn2016.workers.dev.
If you are wiring an AI agent to buy data over x402 (HTTP 402 + USDC on Base), the question to ask about any seller is not "is the demo good?" — it is "show me a settled payment for your own endpoint, on-chain, right now." Talk is free; a Base transaction with a block number is not. This article walks through exactly that proof, and distills it into a five-minute checklist you can run against any seller before your agent signs its first payment.
On October 18, 2026 the PayAPI Market buyer wallet paid $0.01 on Base mainnet for one call of our Token Verdict endpoint. Anyone can check it: transaction 0x4da88c38503029e744a1b2f92cfb6c839795210c4f2a06ce361023d261ca9b09 on Basescan (block 52758984, USDC to the operator wallet). The listing now carries the settlement-verified badge — PayAPI enforces at the database level that the badge cannot exist without a matching on-chain settlement.
What did the $0.01 buy? A real verdict, not an echo: grade GREEN, score 86 for USDC itself — quote-side of the Aerodrome pair, ~$42M liquidity, 1136 days of pair age, 28 pools. That is the same output any agent gets today for $0.01.
1. Settled transaction. Ask for a tx hash of a paid call to their endpoint. Check it on Basescan: USDC amount, recipient wallet, block. A seller who never got paid cannot show you one — that is the point.
2. Badge with database-level enforcement. On PayAPI Market the settlement-verified badge is set only when their own buyer wallet paid and received product. "Listed" only means a 402 challenge exists — a weaker signal.
3. Independent uptime probing. nohumans.directory re-probes every listing on its own infrastructure every 15 minutes and moves listings between unverified / verified / failing automatically — never self-reported.
4. Coinbase validator. The official CDP x402 validator simulates a full payment flow against any resource:
curl -X POST https://api.cdp.coinbase.com/platform/v2/x402/validate \
-H "Content-Type: application/json" \
-d '{"resource":"https://money-reactor.makar52nn2016.workers.dev/api/crypto-price","method":"GET"}'
We ran it on our six paid routes: five came back valid=true, outcome=accepted; the sixth (token-verdict, a 2–3s upstream-heavy call) still passed the flow simulation. Run it yourself against any seller — it is free and needs no API key.
5. Discovery declarations. A serious seller ships extensions.bazaar metadata (input + output examples) inside every 402 challenge, plus a machine-readable catalog: openapi.json, llms.txt, and MCP at /mcp for Claude Desktop / Cursor.
Money Reactor runs 12 endpoints from $0.001: the funded bounty feed (free demo), token safety verdict ($0.01), honeypot repo screen, live crypto price, crypto news, ERC-20 balance, URL-to-text, weather, plus uuid / time / block-number probes — the canonical $0.001 target for testing your own x402 client. Full catalog: no signup, no API key — the complete list.
Autonomous agents cannot read marketing. They read 402 challenges, badges and on-chain receipts. The x402 ecosystem is converging on exactly those artifacts: settlement-verified listings, independent probes, validator outcomes, declared discovery metadata. Sellers who publish proof get found by agents; sellers who do not stay invisible — no matter how good the product is. Demand the tx hash. Publish the tx hash. That is the whole game right now.