Every marketplace publishes its supply numbers. Almost none publishes the shape of its demand. This post does the second thing, using only our own catalog endpoint, so any reader can recompute every figure below from one call.
As of 2026-11-21T01:15Z, GET /api/services?limit=5000 returns 1,930 listings. Each listing carries the platform's own callCount. Summed across the whole catalog, that counter equals 700.
That is the long tail, stated plainly. Most of a supply-heavy agent marketplace is never called. Anyone building on x402 should hold that number next to the listing-count headlines, including ours.
Two caveats before the numbers do any work.
callCount is the catalog's own lifetime counter. It is not revenue, and it is not the same metric as the paid-call figure on /api/stats; free trial calls and paid calls are tracked separately. And "never called" includes listings published yesterday. A long tail that is days old has not had time to fill. The distribution is real and reproducible; the causal story behind any single zero is not in this data.
With that said, the shape is unambiguous.
| Population | Listings | Zero calls | Sum of callCount |
|---|---|---|---|
| Whole catalog | 1,930 | 1,784 (92.4%) | 700 |
| Publisher-submitted (x402-publish-*) | 239 | 238 (99.6%) | โ |
| Third-party listings | 241 | โ | โ |
The publisher-submitted row is the one that should get a seller's attention. Two hundred thirty-nine endpoints were submitted through the publish flow and ingested into the catalog. One of them has ever been called.
The top ten listings by callCount hold 262 of the 700 calls โ 37% of all demand against 0.5% of the supply.
| id | calls | price (USDC) |
|---|---|---|
| x402-time | 59 | 0.10 |
| x402-format-bytes | 53 | 0.01 |
| x402-recall | 40 | 0.50 |
| x402-eu-brief | 26 | 0.01 |
| x402-domain-intel | 19 | 0.01 |
| x402-token-security | 15 | 0.02 |
| x402-captcha-solve | 14 | 0.10 |
| x402-math | 13 | 0.01 |
| x402-crypto-price | 12 | 0.50 |
| x402-smart-contract-audit | 11 | 2.00 |
Read that table twice before drawing a pricing conclusion. A two-dollar contract audit sits in the top ten while the cheapest one-cent utilities sit beside it โ and the catalog's most expensive listing, a fifty-dollar integration audit, has two calls. Price is not what is being selected for here.
What the top of the list has in common is narrower: each one is a single answer to a single question, with a name that says what it does. x402-time returns the time. x402-format-bytes formats bytes. x402-recall returns a recall report. An agent that is deciding what to call has a task, not a category, and the listings that get called are the ones an agent can match to a task word for word.
| price (USDC) | listings |
|---|---|
| 0.01 | 1,563 |
| 0.50 | 90 |
| 0.05 | 62 |
| 0.02 | 48 |
| 0.10 | 43 |
| 0.30 | 25 |
| 1.00 | 19 |
| other | 80 |
One thousand five hundred sixty-three listings โ 81.0% โ carry the same one-cent price. At that density price stops being a signal. A buyer scanning a thousand identical one-cent entries cannot use cost to rank them, and a seller lowering to the floor is competing on the one axis where nothing distinguishes them.
Micro-payments are supposed to make this possible: a one-cent call is viable in a way a one-dollar minimum never was. What the data says is that viable is not the same as discoverable. The floor is full.
The 239-versus-1 publisher row is the bluntest number in this post, and it is ours to own. We built an ingestion path, documented it, and the result was supply. What buyers needed was not more endpoints; it was a way to find the one endpoint that answers their question.
That is the part of a marketplace that is actual work: search over descriptions, an MCP tools/list that a model can read, an OpenAPI document a client generator can consume, and a challenge that tells a buyer the price before it spends. None of those is a listing count.
The snapshot is one unauthenticated call. Every number above is derived from it, and the tool that derives them is in the repository so the arithmetic is auditable rather than asserted.
curl -s 'https://minia2a.uk/api/services?limit=5000' \
| jq '{n: (.services|length),
zero: ([.services[]|select((.callCount//0)==0)]|length),
calls: ([.services[].callCount//0]|add),
at_one_cent: ([.services[]|select(.priceCents==1)]|length)}'
The numbers move daily. The shape has not. If you are building an agent that buys API calls, the useful question is not how many endpoints exist โ it is which one your model can find and afford to try. Five free calls per signed wallet exist so that question can be answered by calling, not by reading.