Tracked seller-wallet receipts · Base + Solana · full UTC day 2026-08-25 · why totals differ
I pay for these APIs with my own wallet and publish what happened. The volume this market gets quoted by is mostly wallets paying themselves, so I read the payments off the chain myself. I check whether the answer that comes back is actually right, against a source that cannot be the seller. And the verdict an agent gates on is backed by money that moved. The sweep covers every USDC payment agents make on Base and Solana, every day. Free MCP server for your agent →
Why this differs from the x402 dashboard total
This headline counts USDC received at the seller wallets we track, on Base and Solana, over the last complete UTC day. Of it, $34,336 settled on Base and $98,653 on Solana (Solana is mostly Bitrefill and Laso). The /x402 dashboard sweeps Base only, so it shows roughly the Base portion; a rolling-24h window there also differs from a calendar day by a few percent. Every figure on this site carries its scope for exactly this reason.
Every term on this site, defined once. If a grade, a score, or a verdict is unclear anywhere else, it is explained here. Machine-readable definitions travel in the MCP tool descriptions too.
Grades, earned by paying
Grade (A+ to F)
A letter grade for ONE measured behaviour of a seller, earned by actually paying it. One seller can hold two at once, for example price honesty A and accuracy C. A dash means we have not bought from it yet, which is not a bad grade.
Delivery grade
Did the paid response return every field the seller promised? delivered = all promised fields present; short = paid but missing promised fields (confirmed on two calls); inconclusive = no usable response to grade, never an accusation. Works for every category, because every seller declares what it will return.
Accuracy grade
For the six categories with an objective ground truth (crypto price, stock, FX, gas, wallet balance, weather), how close the returned value was to a primary source that cannot be a reseller, for example an exchange median or the chain itself. An extra grade on top of delivery, only where a right answer exists.
The pre-pay verdict
Preflight verdict
One gate to read before paying an unfamiliar API: CLEAR nothing alarming, HOLD pay but resolve the reasons, ABORT do not pay without checking the live 402, UNRATED no data yet. A red ABORT fires only from hard evidence (a payTo mismatch, a phantom paywall, a reverified severe underdeliver), never from a soft signal.
Confidence
How much a verdict is backed by, separate from the light: verified = we have paid this seller and recorded what came back; checked = the free live probe passed but no money has moved; unproven = listed, not yet checked. A CLEAR you can lean on is a verified one.
Demand and volume
Reported volume
Raw USDC a seller settled. The number every other leaderboard ranks by, and the one a wash trader can inflate: one wallet paying itself a thousand times outranks a thousand real buyers.
Organic Demand Score
The SHAPE of the money as one number from 0 to 100, not its size. Three parts: breadth (how many distinct wallets paid, up to 40), spread (how evenly the dollars fell across them, up to 40), repeat (share of buyers who came back, up to 20). Revenue is excluded on purpose. A high score is a flag cleared, not a clean bill of health: one large genuine customer looks identical to a wallet paying itself.
Wash / circular / recycled
A seller that pays out almost everything it takes in (90% or more of its inflow flows straight back out). Its settled volume is a loop, not net demand. A flag, not an accusation, since some passthrough is legitimate.
Sends back %
The share of a seller's inflow that leaves its wallet again. At or above 90% it is marked circular.
Demand shape (broad / thin / one wallet)
broad = 20+ buyers, none above 35% of the dollars; one wallet = a single wallet holds 90%+; thin = five buyers or fewer. These count WALLETS, not people: one wallet may be a customer, a fleet, or a seller paying itself.
Unique / repeat payers
How many distinct wallets paid a seller, and how many came back. A buyer who returns is stronger evidence of real demand than one who paid once.
Payment and settlement
x402 / HTTP 402
The pay-per-call protocol: a server answers an unpaid request with HTTP 402 and a price, the client pays in stablecoin, and the request goes through. Settles in USDC on Base and Solana.
The live 402 / payTo
The payment challenge the seller returns on an unpaid call, carrying the price and the payTo address. The one rule that overrides everything: read the payTo and the amount from the live 402 and sign against those, never against a listing.
Phantom paywall
A seller that quotes a price for a route that cannot exist, so the price is not evidence of a real endpoint.
Settlement / the tape
USDC a seller actually received, swept daily straight from Base and Solana chain logs. The accumulated record is the tape: a rolling 24h sweep, so a missed day is gone forever and cannot be recomputed.
Receipt
A hashed, self-verifying record of one paid call: what was promised, what was paid, where it went, and whether delivery matched. Re-derivable offline, so nobody has to trust us.
Scope (why totals differ)
The home total counts tracked seller-wallet receipts on Base AND Solana over a full UTC day. The x402 dashboard sweeps Base only, so it shows roughly the Base portion. Every figure on this site carries its scope for exactly this reason.