157 wallets paid four x402 shops. One of them was the business.
I pulled the Base chain for four shops listed in the x402 discovery index: cyberwarex (six subdomains behind one address, 112 paying wallets), api.myceliasignal.com (37), x402stock.xyz (35), api.socialfetch.dev (28). Thi
I pulled the Base chain for four shops listed in the x402 discovery index: cyberwarex (six subdomains behind one address, 112 paying wallets), api.myceliasignal.com (37), x402stock.xyz (35), api.socialfetch.dev (28). Thirty days of USDC transfers into each shop's payTo address: 4,103 transfers, 157 distinct wallets, and $59.02 that I would count as shop revenue.
One transfer of 2,970 USDC is in the data. It looks like a credit settlement between two wallets, not a purchase, so I left it out of the total and out of every share below.
Three things came out of it.
1. One wallet carries each shop's money. At cyberwarex the largest wallet paid 66% of the money, and pays 3 addresses in total. At mycelia the largest paid 76%, and pays exactly 1 address. At socialfetch the largest paid 55% of transfers and pays 12 addresses overall. x402stock is the exception at 24.7%.
So in three of four, the biggest payer barely exists outside that one shop. Either a bulk customer that needs only that API, or the operator's own load test. The chain cannot tell you which. That is the part worth sitting with: a payer count has no field for "this is my own uptime check."
2. Most wallets are one-shot. 78 of 157 paid exactly once anywhere. 125 of 157 (80%) paid only one shop. The median wallet in the sample made one payment of a few cents.
3. The wallets that pay everywhere spend almost nothing. Eight wallets paid all four shops. Across four shops and thirty days they spent $2.11 in 215 transfers, about a cent each. All eight look the same outside my sample too: in the month, each paid between 136 and 2,404 distinct addresses, at about one call per destination. One of them made 2,008 transfers to 1,532 payees for $30.57 in total. That is not a customer with a budget for you. That is an agent, or a crawler with a wallet, tasting every endpoint once.
What this means if you sell an x402 route: the distinct payer number that looks like traction is mostly the ecosystem testing itself, and the revenue line is one relationship. Those are different jobs. Growing the first does nothing for the second. I suspect most sellers reading their own dashboard are looking at a test suite and calling it demand.
Method, so you can break it: probe each route for its 402, take the payTo, then eth_getLogs on USDC (Transfer, indexed to = payTo) over roughly 6.1M blocks, about 29.7 days, and count senders. One caveat matters more than the rest: a single payTo can front many hostnames (cyberwarex's six subdomains share one wallet), so my "shop" here is a wallet, not a host. And four shops is not the field. The index lists 33,205 endpoints; I read four of the larger ones.
If you run an x402 shop, one number would settle this: what share of your last 30 days of settled payments came from your single largest wallet?
I would bet above 50% for most. If yours isn't, that is the interesting case, and I want to know why.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.