Who actually paid
x402 payments on Base · 28 October 2026
one payer In the last 24 h on Base, 21 x402 payments ($0.17) reached this seller’s wallet, all of them from one wallet.
In the full record: the wallets that paid it, each with its payments, and the share the busiest three sent. 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.
Daily money · x402 USDC on Base · 22 Oct 2026 – 28 Oct 2026
22 Oct $0 (0 payers) · 23 Oct $0 (0 payers) · 24 Oct $0 (0 payers) · 25 Oct $0 (0 payers) · 26 Oct $0 (0 payers) · 27 Oct $0 (0 payers) · 28 Oct under $1 (1 payer)
Relationships
x402 payments on Base · 21 October 2026 – 28 October 2026 · 8 days
1 buyer paid this seller over x402 on 1 of the window’s 8 days: 21 payments, $0.17. 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 12 endpoints in the registry, by paid calls over 30 days; price and chain per endpoint.
| endpoint | paid calls | payers | price | chain |
|---|
/v1/crawl | 2 | 1 | $0.06 | Base |
/v1/diff | 2 | 1 | $0.003 | Base |
/v1/fetch | 2 | 1 | $0.003 | Base |
/v1/section | 2 | 1 | $0.003 | Base |
/v1/text | 2 | 2 | $0.005 | Base |
/v1/batch | 1 | 1 | $0.015 | Base |
/v1/map | 1 | 1 | $0.005 | Base |
/v1/pdf | 1 | 1 | $0.005 | Base |
/v1/scrape | 1 | 1 | $0.005 | Base |
/v1/scrape/residential | 1 | 1 | $0.02 | Base |
/v1/screenshot | 1 | 1 | $0.003 | Base |
/v1/search | 1 | 1 | $0.005 | Base |
The replay
Paid calls, rolling 30 days · 29 October 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 |
|---|
| mach402.dev | 7 | $0.005 | Extract readable content from any URL as clean Markdown. Strips navigation, ads, footers. Returns title, autho |
| nojunk-web-read.mick8511.workers.dev | 2 | $0.002 | Read any public web page as clean JSON: title, description, site name, publish date, language, readable text ( |
| agent-reader.gm-tools.workers.dev | 9 | $0.002–$0.003 | Fetch a public web page and return only its metadata: title, description, canonical URL, language, site name, |
| extract.genexxis.com | 3 | $0.002 | Fetches a public web page URL and returns its main article content as clean Markdown with title, byline and ex |
| x402-agent-tools.nerolabs.workers.dev | 114 | $0.001–$0.5 | Fetches one public web page and returns its main article text, cleaned of menus, ads and footers (Mozilla Read |
| x402-preflight-grokbot.netlify.app | 1 | $0.002 | Safe Read: fetch one public web page and get its clean main text, title, metadata, a sha256 content hash, and |
| api.qocgpiywhm.com | 106 | $0.004–$0.01 | Use to fetch page metadata from a URL: title, description, Open Graph, favicon, HTTP status, and content type. |
| web-scraper-api-production-bf20.up.railway.app | 10 | $0.002 | Fetch a URL and extract clean main-content text with title, description, word count, and char count; boilerpla |
Going rate, the median of the 68 matched sellers with a listed price (of 68 matched): $0.005 a call. This seller’s endpoints run $0.003–$0.06, and the going rate falls inside that range — so no single over/under verdict is fair. Compare per endpoint.