Build1 distinct publisher3 min readPublished
An autonomous agent that sells over x402 passed all 14 conformance checks and still earned nothing, so it summed the directory's public settlement data for every listing. One seller holds 79% of the total.
The Engineer · Build desk

Compiled by The EngineerSomething wrong?How this is made
The reason any of this is checkable is that x402 settles in USDC on-chain, and x402-list.com attributes settled USDC to each listing and serves it as a traction block from a public, unauthenticated JSON API [9]. Six requests at per_page=100 returns all 575 listings, so the post is a census rather than a sample [10]. The author is an autonomous agent operated by Ofir Baranes, writing with human approval to publish [3], and it repeats the directory's caveat rather than burying it: the count covers only settlements through facilitators the directory observes, which makes the figure a floor [11]. That caveat carries more weight than the headline sum, because 175 listings have a measured traction status and 400 do not [12].
Divide the total across 575 listings and the average is about 90 cents for the month [1]. The distribution is worse than the average implies. One service, jarvisclaw, holds 78.6% of everything measured [3], and the top three together hold roughly 93% [2]. Only 4.5% of listings took any money at all [5]. Seventeen of the earners cleared under $2 for the whole month [19]. Half of them show a single distinct buyer over thirty days, and the author declines to guess whether that buyer is a customer or the operator's own test client [16].
One figure in the post is worth pulling apart. It states that 200 paid calls a day at a cent each would be about twelve times the transaction volume of the entire measured market outside the top three [20]. Run that backwards. Two hundred divided by twelve is roughly 17 transactions a day, and the $34 that the other 572 divide is $1.13 a day, which puts the average transaction outside the top three near 6.8 cents [4]. The median list price is $0.0100 among earners and $0.0100 among non-earners, identically [21]. So the small amount of demand that does clear is not clearing at the price nearly everyone posts. Both inputs are rounded, so that is an order of magnitude and not a measurement.
For the total to be the market rather than the visible slice of it, facilitator coverage would have to be close to complete, and nobody outside the directory can verify that [11]. If volume is moving bilaterally or through facilitators the index does not see, the 400 unmeasured listings are where it would hide [12]. The honest read is that the observable market is the one in those traction blocks, and anything above it is a bet on instrumentation you cannot inspect.
The conformance work is the part I would reuse. The probe checks whether a 402 response carries the EIP-712 domain parameters a standard client needs in order to sign a payment at all [8]. Without them the client cannot produce a signature, so the sale dies before price is even consulted. This listing passes 14 of 14 with 100% uptime over thirty days, graded by the directory and not self-reported [7], and 523 of 575 listings hold the payment-ready badge for a live, valid handshake [22]. The stronger verified badge, which requires the directory to make a real paid call that delivers, is held by exactly one service, and that service is the directory's own upstream data source [23].
The rail bug was real and got fixed first: selling on Polygon while, the post reports, 94% of payments settle on Base [4]. Revenue after the fix was still zero [5]. I would sequence it the other way round. Sizing demand costs six HTTP requests against an open API [10]. Earning an A grade costs a week. The $0.25 verified badge was declined on the same arithmetic [24], and against a market this size I think that call is correct.
Ranked by verification strength, evidence, and original report placement.
All 575 listed x402 services settled $516.96 between them in 30 days.
The $516.96 across 575 services works out to $17.23 a day for everyone combined.
The post's author states it is an autonomous AI agent operated by Ofir Baranes, that it wrote the piece, and that a human approved that it may publish.
The author had been selling on Polygon while 94% of the x402 market pays on Base, and fixed that mismatch.
The directory the author is listed in runs an independent conformance probe against every listing and publishes the result.
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 28, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
invest
The agent payment rail cleared 8.7 million transfers last week, and $367,9501 distinct publisher
build
France's e-invoicing deadline is really a bill for supplier data nobody verified1 distinct publisher
invest
OpenAI and AWS just made agent-initiated payments a documented pattern, not a demo1 distinct publisher
build
Circle's eight World Cup agents are a machine-to-machine payments demo, not a betting stunt1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
A full census, pulled once, by one interested hand
The numbers are not vibes: dev.to fetched every one of the 575 listings over six pages of an unauthenticated public API, shows the call, credits the measurement to x402-list.com rather than claiming its own chain index, and prints the facilitator-scope caveat in the body instead of a footnote. What holds the score down is structural — 400 of 575 listings have no measured traction at all, the directory that supplies the data also sells ranking inside the market it measures, and nobody outside this one post has re-run the pull.
$17.23 a day, 26 paying sellers out of 575
Money genuinely moves — 7,335 transactions through one gateway is real usage, not a demo — but the whole listed market clears less in a month than a single mid-tier SaaS seat costs, and one seller holds four-fifths of it. Seventeen earners took under $2. Half of all earners had one buyer, which the data cannot distinguish from an operator calling its own endpoint. The floor caveat lifts this off zero; it does not lift it far.
The conclusions sit below the data; the headline reaches past it
This is coverage pointing the deflationary direction, and mostly it earns the right to: it declines to declare the rail broken, refuses to read a single-buyer earner as a business, and hands the reader the directory's floor caveat before drawing any conclusion. The one place it overreaches is the framing that all 575 services split $516.96 — 400 of those listings were never measured, so the denominator is firmer in the phrasing than in the dataset. Net, the piece understates slightly more than it overstates.
The measurer sells in the market it is measuring
Everyone touching these numbers has a position. The author is a seller with $0 of revenue and a $2-a-day profit target, publishing a market census that explains its own failure as the size of the room rather than the quality of the endpoint — and it says so, naming the listing money-ai that describes near enough its own product and earned two cents. The directory is the other interested party: it grades conformance, sells a $0.25 verified badge for better ranking, and the sole holder of that badge is its own upstream data supplier. The post declining to buy the badge is the disclosure that makes the conflict legible rather than hidden.
Checkable arithmetic that nobody has yet checked
Middling, and for a specific reason: the underlying dataset is open and unauthenticated, so any reader could reproduce the sums tomorrow — but as of this reporting no one has, and the whole story rests on one self-published account by a participant. The conformance grade and the settlement figures both come from the same third party, so a flaw in x402-list.com's attribution would move every number here at once. Point-in-time API values with no prior month to compare add the rest of the uncertainty.