Who actually paid
x402 payments on Base · 20 October 2026
In the last 24 h on Base, no x402 payment reached this seller’s wallet.
Daily money · x402 USDC on Base · 14 Oct 2026 – 20 Oct 2026
14 Oct under $1 (1 payer) · 15 Oct $0 (0 payers) · 16 Oct $0 (0 payers) · 17 Oct $0 (0 payers) · 18 Oct $0 (0 payers) · 19 Oct $0 (0 payers) · 20 Oct $0 (0 payers)
Relationships
x402 payments on Base · 13 October 2026 – 20 October 2026 · 8 days
1 buyer paid this seller over x402 on 1 of the window’s 8 days: 1 payment, $0.002. 0 of 1 buyer came back on another day (0%).
Paid on 1 day of the window: came-back facts need 2 or more days.
In the full record: its most loyal buyers, what is bought alongside it, who left it for whom, who came to it from where, and its early buyers, each with the counts behind it. How to get it: the $0.001 check over x402, Atlas Pro at $49 a month and for the seller itself, the Your buyers report at $29 a month.
Relationships are patterns in the x402 payments we observe on Base over the window: a buyer is a wallet that paid this seller’s payTo wallet, and came back means it paid on two or more different days. A wallet is not an agent, and a relationship is a pattern of payments, not a claim about who anyone is or who runs a wallet.
Is this your service? See who your buyers are: every wallet that paid you, day by day, and where the ones that left went, in one report.
Endpoints
The busiest of this seller’s 2 endpoints in the registry, by paid calls over 30 days; price and chain per endpoint.
| endpoint | paid calls | payers | price | chain |
|---|
/json/validate | 3 | 3 | $0.002 | Base |
/url/preflight | 3 | 3 | $0.005 | Base |
The replay
Paid calls, rolling 30 days · 13 October 2026 to 21 October 2026
2026-10-132026-10-21
Selling something like this
Matched automatically from each seller’s own short description. It will sometimes be wrong; tell us and we fix it.
| seller | paid calls | price | sells |
|---|
| projectx402-production.up.railway.app | 5 | $0.002 | Validate JSON against a JSON Schema. Checks LLM and agent output and API request payloads, returning structure |
| validate.yankii.fr | 4 | $0.01 | Validate JSON data against a JSON Schema (draft-07, Ajv). Returns valid + detailed errors with instance paths. |
| contract-api-production-c176.up.railway.app | 3 | $0.02 | Validate up to ten JSON documents against JSON Schema draft-07 or 2020-12. Returns per-document validity and a |
| jsonschema.openverbs.com | 2 | $0.004 | Validate a JSON value against a JSON Schema (draft-07, with the standard string formats enabled). An invalid s |
| api.coregroupimmo.com | 11 | $0.002–$0.003 | Use this service before importing or publishing JSON to check it against a restricted draft-07 schema. Send da |
| rescue.agent.amnt.io | 1 | $0.03 | API Rescue - Detect API failures, validate responses against schema or baseline, diagnose causes, and propose |
| x402.deepsense.stream | 14 | $0.001–$0.005 | Infer a JSON Schema (draft 2020-12) from an example JSON value: nested objects, arrays, required keys, integer |
| gate-network.matsutake-lab.workers.dev | 4 | $0.005 | Twilio SMS and messaging send preflight. Validate a Twilio Messages.create payload before sending SMS/MMS or o |
Going rate, the median of the 11 matched sellers with a listed price (of 11 matched): $0.005 a call. This seller’s endpoints run $0.002–$0.005, and the going rate falls inside that range — so no single over/under verdict is fair. Compare per endpoint.