Who actually paid
x402 payments on Base · 24 October 2026
In the last 24 h on Base, no x402 payment reached this seller’s wallet.
Payments to 21 hosts land in this same wallet — usually one operator, sometimes a platform collecting for several. The group’s page: kagurazaka.dev.
Daily money · x402 USDC on Base · 18 Oct 2026 – 24 Oct 2026 · the wallet’s, across every host paid into it
18 Oct $0 (0 payers) · 19 Oct $0 (0 payers) · 20 Oct $0 (0 payers) · 21 Oct $0 (0 payers) · 22 Oct $0 (0 payers) · 23 Oct $0 (0 payers) · 24 Oct under $1 (2 payers)
Relationships
x402 payments on Base · 17 October 2026 – 24 October 2026 · 8 days
2 buyers paid this wallet over x402 on 1 of the window’s 8 days: 18 payments, $0.09. 0 of 2 buyers 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/market/categories | 1 | 1 | $0.002 | Base |
/v1/market/new | 1 | 1 | $0.002 | Base |
/v1/market/origins | 1 | 1 | $0.002 | Base |
/v1/market/overview | 1 | 1 | $0.002 | Base |
/v1/market/price-changes | 1 | 1 | $0.003 | Base |
/v1/market/prices | 1 | 1 | $0.003 | Base |
/v1/market/top | 1 | 1 | $0.002 | Base |
/v1/revenue | 1 | 1 | $0.005 | Base |
/v1/seller | 1 | 1 | $0.003 | Base |
/v1/spend | 1 | 1 | $0.005 | Base |
/v1/uptime/incidents | 1 | 1 | $0.002 | Base |
/v1/uptime/top | 1 | 1 | $0.002 | Base |
The replay
Paid calls, rolling 30 days · 25 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 |
|---|
| base.kagurazaka.dev | 25 | $0.001–$0.002 | Check whether a Base transaction settled x402 payments (USDC transferWithAuthorization, EIP-3009): for each, t |
| settled.justinedwardvolmer.workers.dev | 1 | $0.002 | Seller reputation by payTo address: how many endpoints it serves, how many are live, price range, clone-farm a |
| intel.genexxis.com | 7 | $0.003–$0.005 | Find the best x402 endpoints for a task. Returns sellers ranked by proven demand (30-day unique payers, repeat |
| parallax402.com | 13 | $0.01–$0.05 | The funnel, honestly, for one seller over the indexed window: settled USDC and purchases, distinct buyers, org |
| agentcheck-kohl.vercel.app | 17 | $0.002–$0.02 | AgentCheck: independent report on an x402 seller before you pay it. Are its buyers real (repeat wallets on the |
| cryptonews.genexxis.com | 4 | $0.002 | Top crypto stories of the last N hours, deduplicated across 13 outlets and ranked by number of distinct outlet |
| data.kagurazaka.dev | 36 | $0.002–$0.005 | x402 APIs ranked by the uptime we measure every 6 hours over 30 days, then by payers and latency, optionally o |
| settled.tools | 32 | $0.002–$1 | Signed check of an x402 endpoint before you pay it: who really pays it on Base (settlements and unique payers |
Going rate, the median of the 15 matched sellers with a listed price (of 15 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.