Building x402 APIs from Scratch: How I Made AI Agents Pay for Data

#webdev

The Web Has a Forgotten Status Code

Everyone knows 200 (OK), 404 (Not Found), and 401 (Unauthorized). But there's one HTTP status code that's been sitting unused for 30 years: 402 Payment Required.

The HTTP spec literally says: "This code is reserved for future use."

The future is here. It's called x402, and it lets AI agents pay for API calls autonomously using Solana micropayments.

The Problem: Agents Can't Sign Up for Things

Every useful API today requires:

Create an account
Verify your email
Get an API key
Maybe add a credit card
Deal with rate limits and subscription tiers

This works fine for humans. It's a brick wall for autonomous agents.

The x402 Solution

Here's the flow:

Agent -> GET /v1/prices/BTC
Server -> 402 Payment Required
          { recipient, amount: 0.0001 SOL }

Agent -> [signs Solana tx, sends payment]

Agent -> GET /v1/prices/BTC  
          X-Payment-Signature: <tx_sig>
Server -> 200 OK
          { asset: "BTC", price: 64971.53 }

No account. No API key. No subscription. The agent has a Solana wallet, it pays, it gets data.

Bundling Services Behind MCP

The Model Context Protocol (MCP) is how AI agents discover tools. One config line gives your agent 9 tools:

{
  "mcpServers": {
    "apiforchads": {
      "url": "https://mcp.apiforchads.com/mcp"
    }
  }
}

Tools: get_crypto_price, get_clob_price, quick_research, deep_research, render_page, screenshot_page, extract_content, render_pdf, get_status

What I Learned

1. Sub-penny pricing changes behavior. At $0.02/request, agents call freely.

2. MCP discovery is the real moat. Anyone can build an API. Getting agents to find it is the hard part.

3. Solana is perfect for micropayments. Sub-second finality, ~$0.0005 tx fee.

4. x402 + MCP is an empty intersection. Almost nobody is building APIs that agents can both discover and pay for without human intervention.

Try It

The agentic web needs infrastructure. We're early.

DEV Community