DEV Community

Conway Research
Conway Research

Posted on

I Indexed 18,986 AI Agent Endpoints — Here's What the x402 Ecosystem Actually Looks Like

#ai #web3 #api #opensource

We built AgentHub to index and search the x402 ecosystem, and the current numbers paint an interesting picture.

What Is the x402 Protocol?

The x402 protocol turns the internet's forgotten HTTP 402 "Payment Required" status code into something useful: a standardized way for AI agents to pay for API calls in real time, using cryptocurrency.

Here's how it works in practice. An AI agent makes an HTTP request to an endpoint. Instead of getting a 200 OK or a 403 Forbidden, it receives a 402 Payment Required response that includes payment details — how much, to what address, on which blockchain network. The agent makes the payment, resubmits the request with proof, and gets the response. No API keys. No monthly subscriptions. No human in the loop.

This is significant because it means AI agents can autonomously discover, negotiate with, and pay other agents or services. The entire transaction happens in seconds, programmatically, without any human signing up for an account or entering credit card details.

The State of x402 Adoption: Real Numbers

  • 18,986 live endpoints responding to x402 requests
  • 145 unique domains hosting these endpoints
  • Multiple blockchain networks handling payments (Base being the most common)
  • Quality scores ranging from single digits to 85+ on our 0-100 scale
  • Categories spanning AI/ML, DeFi, data feeds, weather, financial analysis, and more

To put this in perspective: 18,986 endpoints is not a toy ecosystem. That's comparable to the early days of the REST API economy in the 2010s. But unlike traditional APIs, these endpoints don't require authentication setup, account creation, or billing negotiations. An agent just pays and calls.

How x402 Differs From Traditional API Monetization

Traditional API monetization looks like this:

  1. Developer signs up for an account
  2. Developer gets an API key
  3. Developer adds a credit card
  4. Developer reads the pricing page
  5. Developer makes API calls
  6. Monthly invoice arrives

x402 monetization looks like this:

  1. Agent calls endpoint
  2. Endpoint returns 402 with price
  3. Agent pays
  4. Agent gets response

Steps 1-5 of the traditional flow disappear entirely. This is why x402 matters for AI agents specifically — they can't sign up for accounts or read pricing pages, but they can make micropayments on a blockchain.

The Discovery Problem: x402's Missing Layer

Here's the most surprising finding from our research: of the 145 unique domains we indexed, zero have published A2A Agent Cards.

A2A (Agent-to-Agent) is Google's protocol for agent discovery and communication. An Agent Card is essentially a machine-readable business card that tells other agents what services you offer, what protocols you support, and how to interact with you.

The fact that zero domains have Agent Cards means the x402 ecosystem has a discovery problem. The payment infrastructure is ahead of the discovery infrastructure by a wide margin. Agents can pay each other, but they can't find each other without someone maintaining a directory.

This gap is exactly why we built AgentHub — a searchable, quality-scored registry that lets any agent discover x402 endpoints by capability, price, quality, or category.

How to Use x402 Endpoints Today

Finding Endpoints

Using AgentHub's free search (no key required):

# Search for weather endpoints
curl "https://api.agenthub.dev/search?q=weather"

# Find high-quality AI/ML endpoints on Base
curl "https://api.agenthub.dev/search?category=AI/ML&network=base&minQuality=70"

# Get the cheapest endpoint for a capability
curl "https://api.agenthub.dev/search?q=sentiment+analysis&sortBy=price"
Enter fullscreen mode Exit fullscreen mode

Calling an x402 Endpoint

The flow from your agent's perspective:

// 1. Discover the best endpoint
const discovery = await fetch(
  'https://api.agenthub.dev/search?q=smart+money&sortBy=quality'
);
const { results } = await discovery.json();
const endpoint = results[0];

// 2. Call the endpoint (you'll get a 402 with payment instructions)
// 3. Make the payment on-chain
// 4. Resubmit with payment proof
// 5. Get your response
Enter fullscreen mode Exit fullscreen mode

The Three Protocols: x402, A2A, and MCP

The AI agent ecosystem is converging on three complementary protocols:

x402 — Pay-per-call HTTP. The payment layer. Agents pay for individual API calls using cryptocurrency.

A2A — Agent-to-Agent (Google). The communication and discovery layer. Agents publish Agent Cards describing their capabilities.

MCP — Model Context Protocol (Anthropic). The context layer. Allows AI models to access external tools and data sources in a standardized way.

AgentHub indexes all three protocols in a single search, which means an agent looking for "weather data" gets results from x402 paid endpoints, A2A agent services, and MCP context providers — ranked by quality and relevance.

What's Next for x402

Based on current growth trends, we expect:

  1. Discovery standards to catch up. The zero-Agent-Cards finding won't last. As the ecosystem grows, discovery becomes the bottleneck.
  2. Quality differentiation matters. With 18,986 endpoints, there's already meaningful variation in quality.
  3. Multi-protocol agents become standard. The agents that thrive will speak x402 for payments, A2A for discovery, and MCP for context.
  4. Pricing competition. Multiple endpoints offering similar capabilities at different price points means market dynamics will drive prices down and quality up.

Getting Started

If you're building AI agents and want to integrate x402 endpoint discovery:

  • Search the registry: AgentHub
  • No API key required — just make requests

The x402 ecosystem is real, it's growing, and it's bigger than most people realize. 18,986 endpoints is just the beginning.

Published by the AgentHub team. Data based on our live crawl of the x402, A2A, and MCP ecosystems as of March 2026.

Top comments (0)