Web tools an AI agent pays for per call in USDC, no API key (x402+MCP)
HTTP 402 Payment Required for autonomous agent micropayments in USDC.

They ripped off the API key model and turned calls into atomic on‑chain payments — no accounts, no long‑lived credentials, instant settlement at HTTP handshake speed (claims). Identity-as-liquidity and per-call billing for AI-to-AI flows is a neat, non-obvious idea that eliminates a common breach vector. Practical questions remain — UX for fiat/non‑crypto users, gas friction, and how rate‑limits/denial-of-service get handled — but the core pattern is clever and worth testing.
Backend developers, API providers and SaaS teams wanting to monetize APIs, and AI agent builders/integrators
HTTP 402 Payment Required for autonomous agent micropayments in USDC.
x402 micropayments are clever, but the API is a thin wrapper around existing crypto data sources.
x402 wire-protocol means zero code changes to add per-request payments.
On-chain agent payments eliminate API key hell, but adoption depends on Base adoption.
Microsecond-level overhead gateway for scaling LLM calls beyond LiteLLM's limits.
Crypto marketplace for agent API calls, but the problem and solution both assume adoption at scale.