Two x402 Marketplaces, Two Philosophies: Curated vs Open Discovery in the Agent Economy

As of August 2026, there are two production x402 marketplaces serving the agent-to-agent economy. They share a payment protocol — HTTP 402 with USDC settlement on Base — but represent fundamentally different philosophies about how agent services should be discovered. Understanding the difference matters because it shapes what kinds of services agents can find, who decides what gets listed, and whether discovery is a gate or a public utility.

The Landscape: Two Markets, Two Models

The numbers tell the story. Agentic.Market lists roughly 50 services — almost all well-known API brands. minia2a lists 323 — from token security checkers and gas price oracles to CAPTCHA solvers, ENS resolvers, and Polymarket data feeds. One is the App Store. The other is the web.

Why the Difference Exists

This isn't an accident of timing. It's a structural consequence of how each marketplace is governed.

Agentic.Market is Coinbase-operated. Every service listed there was either onboarded by Coinbase directly or invited. The quality floor is high — you won't find a broken endpoint or an unmaintained service. But the ceiling is low: if you built an x402-enabled API yesterday, there's no public path to being listed tomorrow. The directory's growth is bounded by Coinbase's curation bandwidth.

minia2a is self-serve. Any agent operator registers, configures pricing, and goes live. The long tail includes services that would never pass a curation process — niche utilities, experimental endpoints, single-purpose tools. Quality varies, but the aggregate value is in coverage: agents can find a service for almost any atomic task, even if it's not from a brand-name provider.

The tradeoff is real: curation buys trust at the cost of coverage. Open registration buys coverage at the cost of trust. Neither model is strictly superior — they optimize for different things.

What Both Models Miss: Federated Discovery

Here's the structural problem that neither marketplace solves on its own: an agent shouldn't have to know which directory to search.

If you're building an autonomous agent that needs to find a token security checker, it shouldn't matter whether that service is listed on Agentic.Market, minia2a, or a third marketplace that launches next month. The agent should query once and search across all of them.

This is exactly the gap the x402 discovery extension (PR #2979) — now also an IETF Internet-Draft — is designed to fill. By standardizing /.well-known/x402 manifests and DNS TXT records, it makes any x402-enabled domain self-describing. A crawler can walk the web and build a federated index that includes services from every marketplace — and services hosted on independent domains that aren't listed anywhere at all.

The discovery extension doesn't replace marketplaces. It makes them regenerable caches rather than primary authorities. The same way a search engine indexes websites without asking permission, a federated x402 index could list services without going through any marketplace's curation process.

What the Data Says About Where Services Actually Live

The PR #2979 discussion surfaced census data that's worth examining. As of early August 2026, a crawl of 1,521 hosts serving /.well-known/x402 found 982 distinct manifests (661 unique registrable domains). Of those 1,521 hosts, 394 — roughly a quarter — sit on platform suffixes like vercel.app (202 hosts), workers.dev (72), and railway.app (66).

These are individual developers and small teams deploying x402 services on their own domains. They're not on any curated directory. They may never be. But they're live, they're serving 402 Payment Required responses, and they're part of the agent economy whether a centralized directory acknowledges them or not.

The agent economy is already bigger than any single directory. Federated discovery isn't a nice-to-have — it's catch-up infrastructure for a network that's already decentralized.

The Path Forward: Complementary, Not Competitive

The right framing isn't "curated vs open" as a battle. It's "curated AND open" as complementary layers:

• Curated directories (Agentic.Market) serve agents that need guaranteed quality — the "I need Claude and I need it to work every time" use case.
• Open marketplaces (minia2a) serve agents that need coverage and discovery — the "find me any service that can extract text from a PDF for under $0.01" use case.
• Federated discovery (x402 spec extension) serves the ecosystem itself — making all services findable regardless of which marketplace they're on.

The agent economy doesn't need one directory to win. It needs all services to be discoverable, all payments to settle, and all agents to find what they need. The payment rails are built. The discovery layer is being standardized right now. What remains is making sure the standard serves both the curated and the open model — because the real network includes both.

What to Watch

Three signals will determine how this plays out over the next quarter:

1. Does the x402 discovery extension ship with language that supports aggregator/broker discovery? The current draft's resources[] is same-domain-only, and peers[] multi-facilitator routing doesn't cover the aggregator case. If marketplaces can't express their listings through the standard, federated discovery remains incomplete.
2. Does Agentic.Market open a public submission path? If Coinbase keeps the directory invite-only, the gap between the curated catalog and the real deployed network will only grow.
3. Do agents start using /.well-known/x402 directly? The moment an agent framework bakes in "check .well-known/x402 before falling back to a directory," the power dynamic shifts from gatekeepers to service operators.

The x402 protocol solved the payment problem. The discovery problem is being solved right now, in public, with real census data from the deployed network. The question isn't whether agent services will be discoverable — it's whether that discovery layer will be open or gated. The spec says open. The market will decide.