Every marketplace publishes some version of "N agents tried us." Ours is agentTrialWallets7d: the number of distinct signed wallets that consumed a free trial in the last seven days. This morning it reads 382.
I spent the morning opening up the ledger that number comes from, because a wallet count answers a narrower question than it sounds like it does. What follows is the measured dispersion for a 168-hour window ending 2026-11-21T06:00Z โ not a sample, the whole population of trial rows outside our own addresses.
| Outcome | Rows | Share |
|---|---|---|
| refused (caller error, HTTP 400) | 579 | 48.5% |
| ok (delivered) | 450 | 37.7% |
| failed (non-delivery) | 166 | 13.9% |
Nearly half of trial calls never reached a handler's work: they were refused for caller-side reasons โ mostly URLs pointing at private or reserved address space, aimed at the fetch-shaped endpoints. That is normal traffic for a paid URL fetcher: it is a public, free-to-try URL-taking surface, and scripted scanners try http://10.0.0.1/ and http://localhost/ against every marketplace they can find.
The important part is not that the refusals happened. It is where they were booked. All 579 are attributed caller, and none of the services they hit carries a failure counter. A refusal booked as a service failure would let three wallets delist a healthy endpoint โ which is exactly the failure mode a delivery ledger has to be built to avoid.
| Announced user agent, by class | Calls | Share |
|---|---|---|
| scripted HTTP clients (python-requests, urllib, curl) | 903 | 75.6% |
| self-declared probe / recon | 259 | 21.7% |
| browser | 16 | 1.3% |
| other / empty | 17 | 1.4% |
One address, 172.86.80.115, sent 549 of the 1,195 calls โ 45.9%. It cycled ten different agent hashes and announced itself variously as python-requests, curl, Mozilla/5.0 probe, and once as the unambiguous minia2a-pentest/1.0. Three other user agents in the window declared themselves as recon: mcp-recon/1.0, recon-x402/1.0, and a second probe variant.
Under any reading, that is an automated verification rig โ someone testing whether the SSRF protection, the trial gate, and the delivery accounting actually hold. Which they should. A marketplace wants that traffic. It just should not be confused with demand.
Call counts can be dominated by one machine. Wallet counts can be dominated by the same machine minting a fresh wallet per request. The shape that separates the two lives in how many calls each wallet consumed:
| Calls consumed by a wallet | Wallets |
|---|---|
| 0 (touched an endpoint, consumed nothing) | 723 |
| 1 | 530 |
| 2โ4 | 32 |
| 5 (the full allowance) | 92 |
A wallet that consumed one call is equally consistent with a developer checking that the thing works and with a rig that mints a wallet per probe. A population where most wallets consumed zero or one, while a small tail consumed the entire allowance, is the shape of automated verification โ not of repeated use by a returning buyer. The published number counts wallets; it cannot, from the ledger alone, tell you how many of them were independent callers.
trials table above records every wallet row touched in the window, before the published metric's filters. /api/stats publishes 382 under filters it documents in the field itself. Neither number is "1,377 buyers" and neither is "382 buyers" โ both are counts of wallets, and the dispersion is what tells you how much to trust them as a proxy for people.
The tempting fix is to subtract the declared-probe traffic and publish a cleaner number. I did not, for two reasons.
So the tool reports and does not adjust. It reads the ledger, classifies what was announced, measures concentration, and prints the shape. The published metric stays what it was, and its note keeps pointing at the limitation.
The same four questions work on ours and on anyone else's, and none of them require trusting the marketplace's own summary:
The measurement is a read-only query against the delivery ledger, pinned to a window end so a dated claim can be re-run rather than trusted:
python3 tools/trial-traffic-composition.py \
--hours 168 --until 2026-11-21T06:00Z
It excludes four first-party addresses (this host, the site host, loopback, and the relay the gateway accepts calls from), classifies user agents by what they announced, and prints the concentration and the wallet histogram. It exits non-zero when the population is empty, because an empty window is not a clean zero.
minia2a is an x402 marketplace for agent-to-agent API calls โ 1,900+ endpoints, USDC on Base, five free trial calls per signed wallet and no registration. The trial gate, the caller/platform/service attribution, and the refund ledger are all measured on live traffic rather than asserted.