· 5 min read
A researcher just indexed the entire x402 ecosystem. The finding that should keep agent developers up at night isn't the 18,986 endpoints — it's the zero.
Conway Research published an index of the x402 payment ecosystem this week. Their crawler found:
Then they checked how many of those 145 domains publish an A2A Agent Card — Google's machine-readable agent discovery format at /.well-known/agent-card.json.
Zero.
Not "a few." Not "only the big ones." Zero out of 145.
The agent payment stack has four layers. Here's the state of each in August 2026:
x402 is standardized and works. An agent hits an endpoint, gets back 402 Payment Required with X-Payment-Required: price=0.05, currency=usdc, chain=base, signs a transaction, resubmits with Authorization: x402 <signed-tx>, gets 200 OK with X-Receipt: <signature>.
Infrastructure providers: Coinbase CDP (reference implementation), Cloudflare Wallets (launched Aug 4), OSL AgentPay (launched Aug 7), Circle nanopayments, Crossmint (50+ chains), Stripe/Privy.
The handshake layer has 20+ institutional members under the Linux Foundation's x402 Foundation. It is not the bottleneck.
AIR (Agent Interop Receipts) is an open receipt format with JWS envelopes binding request digest, payment tx hash, and server identity. The IETF has a draft for DNS-based facilitator discovery (_x402.{domain} TXT records → authenticated HTTPS manifest).
Functional implementations exist. Not the bottleneck.
18,986 endpoints. Zero A2A Agent Cards. Three discovery mechanisms exist on paper:
| Mechanism | Path | Spec | Adoption |
|---|---|---|---|
| A2A Agent Card | /.well-known/agent-card.json | Google A2A v0.2+ | 0 of 145 domains |
| x402 manifest | /.well-known/x402.json | x402 ecosystem | Unknown, low |
| DNS TXT record | _x402.{domain} TXT | IETF draft-hawkins | Draft stage |
An Agent Card is a JSON manifest declaring identity, capabilities, security schemes, and tool definitions. It takes minutes to implement — a static JSON file at a well-known path. The format is stable, documented, and supported by Google's A2A protocol. And yet: zero.
Receipt chaining (agent A pays B, B embeds receipt when paying C), on-chain AgentCard registration for tamper-evident discovery, verifiable execution provenance — discussed in x402 Foundation working groups but not standardized.
Three structural reasons:
1. Builders optimize for what's visible. Getting a payment to settle is a concrete engineering challenge with a binary success criterion. Publishing a discovery manifest is invisible infrastructure — nobody notices when you do it, nobody complains when you don't.
2. The chicken-and-egg problem. Agents don't look for Agent Cards because nobody publishes them. Nobody publishes them because agents don't look for them. The protocol exists but the network effect doesn't.
3. Discovery is a different problem than payments. Payment is point-to-point (my agent pays your agent). Discovery is many-to-many (which of 18,986 endpoints should my agent pay?). A JSON manifest at a well-known path helps an agent that already knows your domain. It doesn't help an agent that doesn't know you exist.
A .well-known/agent-card.json file is necessary but not sufficient. It answers "what does this agent do?" — not "which agent should I use?"
The missing pieces:
This is why agent commerce is producing marketplaces alongside protocols. The protocol solves the payment. The marketplace solves the discovery.
Conway Research built AgentHub — a searchable index of x402 endpoints by capability, price, quality, and category, with an MCP server so Claude and Cursor can query it directly. It's a response to the exact gap their own data revealed.
Meanwhile, open marketplaces like minia2a bridge the protocol gap: agents register their endpoint, get verified as a real HTTP server, and become discoverable by capability tags and categories. Buyers get free trials on every endpoint before committing funds.
The market is deciding that discovery is a product, not a protocol.
/.well-known/agent-card.json — it's 20 lines of JSON. Even if no agent is looking today, they will be. The format is stable. The cost is zero._x402 TXT records) could become the standard fallback. Implementing it early is cheap.18,986 endpoints prove the payment layer works. Zero Agent Cards prove the discovery layer doesn't. The agent economy has money moving. What it doesn't have is a map. Building the map is the opportunity.
Data: Conway Research x402 Ecosystem Index (August 2026), x402 Foundation, IETF draft-hawkins-x402-dns-discovery-01. Analysis and opinions my own.