Directory of developer tools and APIs supporting x402 HTTP 402 micropayments. Pay-per-call pricing for AI agents — no signup, no API keys.

x402 Payment Protocol — Developer Services Directory

Published 2026-04-14 · Not yet reviewed

The x402 protocol enables AI agents to pay for API calls via HTTP 402 micropayments — no signup, no API keys, no accounts. Just a USDC wallet on Base. This directory tracks all 6 developer services in our index that support x402.

6
x402 services
4
Categories
USDC
Settlement

How x402 Works

  1. Agent sends request — standard HTTP request to any x402-enabled API endpoint.
  2. Server returns 402 — response includes payment amount, recipient address, and chain (Base L2).
  3. Agent pays — signs a payment authorization. No gas fee for the agent.
  4. Agent retries with receipt — original request + payment proof in headers.
  5. Server verifies & responds — on-chain verification, then normal API response.

All x402-Enabled Services

6 developer services accepting x402 micropayments across 4 categories.

ServiceCategoryFree Tierx402 CostChain / Settlement
Browserbase Browser Automation Free $0.12/hour Base / USDC
Tavily AI AI / ML Free $0.01 / call Base / USDC
Pinata IPFS Storage Free $0.10/GB * 12 Base / USDC
Exa AI / ML Free $0.007 / request Base or Solana / USDC
Hyperbrowser Browser Automation Pay-per-use $0.10 per hour Base or Solana / USDC
Strale Dev Utilities Pay-per-use — Base / USDC

Services by Category

Browser Automation 2 services

Browserbase $0.12/hour

Free

Headless browser infrastructure — Free Plan $0/mo Get started with Browserbase

Hyperbrowser $0.10 per hour

Pay-per-use

Pay-per-use cloud browser sessions for AI agents — x402 micropayments, no API key needed

AI / ML 2 services

Tavily AI $0.01 / call

Free

Real-time web search API for AI agents, with search, extract, crawl and research endpoints

Exa $0.007 / request

Free

Web search API for AI agents with Search, Contents, Answer, Monitors and Agent endpoints

Storage 1 service

Pinata IPFS $0.10/GB * 12

Free

IPFS pinning and file storage with an API

Dev Utilities 1 service

Pay-per-use

Business data APIs for AI agents: 298+ capabilities across 25 countries by Strale's count (read 2026

Frequently Asked Questions

What is the x402 payment protocol?

x402 is an open HTTP-native payment protocol that uses the HTTP 402 status code to enable machine-to-machine micropayments. When an agent hits a 402 response, it reads payment requirements from the response, completes a USDC payment on Base, and retries with proof of payment. No accounts or API keys needed. Joined the Linux Foundation in April 2026 with founding members including Coinbase, Cloudflare, Stripe, Google, Visa, Mastercard, AWS, and Shopify.

How does x402 work for AI agents?

An AI agent sends an HTTP request to an x402-enabled API. If payment is required, the server returns HTTP 402 with payment details (amount, recipient, network). The agent signs a payment authorization and retries with it in a header. The server or a facilitator verifies and settles it on-chain. The facilitator pays the gas. The server returns the response.

How many developer services support x402?

We currently index 6 developer services with x402 support across 4 categories.

Do x402 services require crypto knowledge?

No. Modern x402 client libraries handle the payment flow automatically. The agent needs a funded USDC wallet on Base — that's it. Libraries like @x402/fetch and @x402/axios abstract the payment negotiation entirely.

What are the costs of using x402?

Each service sets its own price, and this page lists a cost only where the vendor's own docs state it. The agent pays no gas fee; the facilitator covers it. There are no monthly minimums, no commitments, and no signup fees. You only pay for what you use, per-request.

API: /api/offers?payment_protocol=x402 · /api/agent-payments?protocol=x402 · MCP: search_deals({payment_protocol: "x402"})

Full payment protocol directory: Agent Payments (x402 + MPP) · x402.org ecosystem