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 $0 (0 payers) · 15 Oct $0 (0 payers) · 16 Oct $0 (0 payers) · 17 Oct $0 (0 payers) · 18 Oct under $1 (1 payer) · 19 Oct $0 (0 payers) · 20 Oct $0 (0 payers)
Relationships
x402 payments on Base · 13 October 2026 – 20 October 2026 · 8 days
2 buyers paid this seller over x402 on 2 of the window’s 8 days: 2 payments, $0.10. 0 of 2 buyers came back on another day (0%).
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 8 endpoints in the registry, by paid calls over 30 days; price and chain per endpoint.
| endpoint | paid calls | payers | price | chain |
|---|
/v1/cve/check | 2 | 2 | $0.05 | Base |
/v1/deps/check | 2 | 2 | $0.05 | Base |
/v1/evm/tx-inspect | 2 | 2 | $0.1 | Base |
/v1/legal/cite-check | 2 | 2 | $0.1 | Base |
/v1/ai-act/obligations | 1 | 1 | $0.1 | Base |
/v1/btc/tx-context | 1 | 1 | $0.1 | Base |
/v1/btc/tx-inspect | 1 | 1 | $0.1 | Base |
/v1/deps/version-check | 1 | 1 | $0.05 | 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 |
|---|
| mcp-snowy-dew-9447.fly.dev | 3 | $0.003 | Checks whether an npm, PyPI, or crates.io package is safe to install: confirms it exists, flags malicious or t |
| pkgsafe.adrwent.fyi | 4 | $0.005 | Call before installing or updating an npm or PyPI dependency. Returns a verdict (ok, caution, avoid, unknown) |
| api.vrsai.tech | 9 | $0.01 | Check an exact npm or PyPI package version immediately before installation using current registry, vulnerabili |
| factstamp.agentrails.workers.dev | 18 | $0.02–$5 | Check a citation before repeating it. Give a DOI, an arXiv ID or a paper title; the answer says whether the wo |
| pkgpulse.letom1176.workers.dev | 5 | $0.01–$0.02 | Rank up to 5 alternative npm packages and get a recommendation with the gap quantified: full disclosed-rubric |
| packages.cfsoft.us | 11 | $0.02–$0.1 | Is this WordPress plugin, npm package or PyPI project abandoned? Status, 0-100 abandonment-risk score, months |
| vuln-intel.x402tookit.com | 8 | $0.02–$0.05 | Known vulnerabilities for an exact package version (npm, PyPI, Go, Maven...): fixed version, exploited-in-the- |
| depscout.vercel.app | 1 | $0.02 | Check an npm package, PyPI package, or GitHub repo and return a DepScout install verdict. |
Going rate, the median of the 8 matched sellers with a listed price (of 8 matched): $0.02 a call. This seller charges $0.05–$0.1, which is over it on every endpoint.