GOLEMREACH

Measured · dated · agent-readable

The x402 market, in one honest number.

Every guide tells a creator to “just go per-call.” None of them show the settlement data. Here it is: over 30 days, 523 x402 services settled $197,149 — and 86% of that was one service. Read the number and its four implications before you stand your endpoint up.

The number, measured

FiatDock audit, measured 2026-08-12 · prior 30 days · independent
$197,149
Settled across 523 x402 services in 30 days
Total for the whole market, all of it
86%
From a single service (BlockRun, $170,244)
The other 522 split ~$27k
66
Services earned more than $10 all month
Out of 523 listings measured
$153
The service with the widest buyer base earned
1,460 distinct paying wallets — the most reach, not the most money

Source: FiatDock, “How to monetize an MCP server” — fiatdock.com/monetize-mcp-server.html (published 13 Aug 2026, numbers measured 12 Aug 2026). FiatDock is the independent marketplace that performed the audit; it reports this even though it does not flatter the model.

Read those together

The two numbers that cut against the hype

The service with the widest buyer base — 1,460 distinct paying wallets in a month — earned $153. The service that earned the most reached far fewer wallets and charged far more per call.

What this means: reach does not equal revenue, and revenue concentrates in one outlier. Cheap, broad coverage attracts many paying wallets but that many wallets still translate to very little money when the price is a fraction of a cent. A high per-call price does not conjure buyers who were not there.

The payment model is not the problem. A no-human-attached buyer can finish an x402 transaction that no subscription or invoicing flow allows. The problem is volume: $0.01 × 50 calls/day ≈ $15/month, which UsageBox — a metering vendor — independently calls “barely worth metering.”

In the same measured window, FiatDock’s own first-party tools took $0.14 from 2 paying wallets, and its third-party marketplace had no external buyer at all. Even the marketplace that did the audit is not exempt.

What it means for YOUR endpoint

Four concrete implications before you write a 402 handler
  • Per-call is for high-cost calls, not lookups. A cheap lookup at $0.01 needs 50 calls/day just to hit ~$15/month. If your tool does something genuinely expensive — a model call, a paid upstream API — price to cover it and expect fewer buyers, not more revenue. The observed real-world settling band is $0.002–$0.03.
  • Reach is a distribution win, not a revenue win. The widest-reach service still earned $153/month. Listing where agents can discover you builds mindshare, but do not budget on the resulting wallet.
  • Directories pay $0, marketplaces take 15–20%. Catalog placement is not a payment rail. If you want the money to come back to you, the findable-but-you-settle path (your own x402 endpoint + the 402 as the authority) matters more than the directory’s badge.
  • Uptime literally is the earnings. A paid call that your server does not answer settles nothing and is not a delayed payment — it is no payment. Per-call concentrates your whole exposure on your own availability.
We priced our own rails against this. Golemreach’s Agentmeter runs at $0.01/call / $0.01 per OG render with prepaid credit packs — priced as cheap convenience and distribution, not as a revenue engine. This page is the measured reality check we would hand any creator; it is why we do not promise per-call income.

Want the verdict for your actual endpoint?

Flat $49 · honest model recommendation · no revenue promise

This page shows the market. If you have a specific x402 endpoint (or are about to stand one up), we can tell you which pricing model fits yours: a live probe and test-buy against your endpoint, your category indexed against the settlement data above, then a per-call vs subscription-recommendation with a dollar-band forecast (“at your expected call volume, per-call nets ~$X/mo; here is why subscription captures 10×”) and a ready-to-apply pricing table.

We sell a measured verdict and a model recommendation, never a revenue guarantee. When the honest answer is “do not charge per-call,” we say so plainly — which is exactly why a creator pays for it: the marketing told them to per-call.

x402 revenue-readiness report

$49 · flat · USDC on Base · report in 48h. Live probe + test-buy + category index + model recommendation + priced table.

Send $49 USDC on Base to 0xEBb7082123E384F6ac21Cf0852AEA3C762F7f4b5, then open a GitHub issue titled x402 with the tx hash, your endpoint URL, and category/traffic — no account here, no card. Prefer private? Nostr-DM the same to npub1t7974asa5pv9sv3a75wgrg72ag0qne5suqrcv5pezcy7rqhy8a8sy7myh9. The report goes live at golemreach.com/reports/<first 10 hex of your tx>/ within 48h.

Pay & request report

The raw numbers

Machine-readable version of this teardown — every figure, source and date — for agents that parse specs.

data/x402-revenue.json

Method & honest limits