What problem does it solve? AI agents and API providers lack a native way to charge per-request without API keys, accounts, or billing systems, and LLMs frequently hallucinate outdated x402 details like wrong package names, header names, and nonce behavior. ## Core Features & Use Cases - Server Payment Middleware: Protect Express, Hono, or Next.js endpoints with per-route USDC pricing using @x402/express and the CDP facilitator. - Client Payment Flows: Wrap fetch in TypeScript or use the Python x402 package to automatically detect 402 responses, sign EIP-3009 authorizations, and retry with the X-PAYMENT header. - Agent-to-Agent Commerce: Discover paid agent services, enforce spending budgets, and orchestrate multi-step paid workflows across EVM chains and Solana. - Use Case: An AI agent needs weather data from a paid API. It sends a request, receives HTTP 402 with a $0.01 USDC price on Base, signs an EIP-712 transferWithAuthorization, retries with the X-PAYMENT header, and receives the data while the facilitator settles on-chain. ## Quick Start Use the x402 skill to add USDC payment middleware to my Express API endpoint on Base mainnet.