Who actually paid
x402 payments on Base · 31 October 2026
In the last 24 h on Base, no x402 payment reached this seller’s wallet.
Payments to 2 hosts land in this same wallet — usually one operator, sometimes a platform collecting for several. The group’s page: reference-data-api.onrender.com.
Relationships
x402 payments on Base · 24 October 2026 – 31 October 2026 · 8 days
No x402 payment reached this seller’s wallet on Base in the window, so it has no buyers to read relationships from.
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. Bought alongside and the switches leave out wallets that paid more than 30 sellers in the window: a wallet that pays everyone says nothing about what goes together.
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 8 endpoints in the registry, by paid calls over 30 days; price and chain per endpoint.
| endpoint | paid calls | payers | price | chain |
|---|
/v1/energy-calendar | 1 | 1 | $0.017 | Base |
/v1/lei | 1 | 1 | $0.012 | Base |
/v1/meeting-window | 1 | 1 | $0.013 | Base |
/v1/sun-moon | 1 | 1 | $0.014 | Base |
/v1/timezone | 1 | 1 | $0.013 | Base |
/v1/treasury-rate | 1 | 1 | $0.015 | Base |
/v1/vat | 1 | 1 | $0.016 | Base |
/v1/vin | 1 | 1 | $0.018 | Base |
The replay
Paid calls, rolling 30 days · 1 November 2026
One stored day so far. Movement appears from the second.
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 |
|---|
| x402-filings.datalayer.workers.dev | 41 | $0.01–$0.03 | Decode any 17-character VIN into the vehicle it describes: make, manufacturer, model, year, series, body class |
| api.vindexapi.dev | 65 | $0.01 | Normalized NHTSA vPIC VIN decode (?vin=) — make/model/year/engine/body/… with fetch provenance, plus ORIGINAL |
| vin-verify.iykykblog.workers.dev | 8 | $0.05 | Decode a 17-character VIN: ISO 3779 structural validation (check digit), WMI manufacturer lookup, model year, |
| foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev | 12 | $0.003–$0.01 | Decode a VIN into make, model, model year and vehicle attributes using NHTSA vPIC. Use when an agent has a VIN |
| vehicle-recall-check.iykykblog.workers.dev | 4 | $0.05 | Check NHTSA safety recall campaigns for a vehicle by make, model, and year — or by VIN (decoded live via NHTSA |
| x402-v2-mint-nhtsa-recalls.vercel.app | 1 | $0.020144 | NHTSA vehicle safety recalls by make/model/year (keyless). POST {make}/{model}/{modelYear}. Unpaid empty → 402 |
| x402-api-24223879872.us-east1.run.app | 2 | $0.02 | Validates an 18-digit Mexican CLABE (sent as a JSON body, not a query param): check digit, bank identification |
| api.apex-db.org | 1 | $0.1 | Search normalized vehicle variants by brand, model, model year, powertrain, market, or free text. |
Going rate, the median of the 15 matched sellers with a listed price (of 15 matched): $0.01 a call. This seller charges $0.012–$0.018, which is over it on every endpoint.