OUR OWN ROW, DISCLOSED
Agent402, for comparison
We run the index, so we keep ourselves out of the ranking above. Here are our own figures instead, from our sales ledger: settlements and rails count paid settlements from outside buyers only, and the proof-of-work row is a lifetime count of free calls, excluding our own monitoring probes.
| proof-of-work free calls, lifetime | 24,681 |
|---|
| rails with an outside settlement | 12 of 15 |
|---|
| outside settlements, 30 days | 33,182 |
|---|
| distinct outside buyers, 30 days | 476 |
|---|
| outside settlements, since 2026-07-03 | 48,810 |
|---|
| outside settlements over the MPP wire | 2,284 |
|---|
METHOD
How the number is built
01Discover sellers from the x402 Bazaar discovery listing plus our own crawl, refreshed every 4 hours.
02Read each seller's advertised payTo addresses out of its x402 manifest.
03Pull settlement transfers to those addresses from Base event logs with eth_getLogs.
04Count a transfer when it matches a price that seller publishes, up to a price-match ceiling ($25.00). Anything matching none of their prices is held to a per-call ceiling ($0.75), so treasury movements, gift cards and stablecoin conversions are not counted as tool calls.
05Aggregate by payTo, group wallets belonging to one seller, and rank.
What the Base table cannot see: settlements on other chains (Solana is read separately above, as inbound transfers), payments to addresses a seller never advertised, and which specific tool was bought. Those are limits of on-chain data, not of the crawler.
What this is not: an assessment of any business or its operators. Every figure is an on-chain reading as of the snapshot above. A concentrated row is the ordinary shape for a seller with one large integration partner, a seller in its first weeks, or a seller whose buyers run many agents from one wallet, and we are not asserting that any flagged row is inauthentic.
Corrections: readings go stale, and wallets can fold to the wrong operator. A seller who believes their row misreads them can write to mike@agent402.tools and we will re-scan and correct or withdraw it.