x402 protocol compatibility

x402 is an open payment standard by Coinbase that embeds stablecoin payments directly into HTTP requests — bringing native payments to the web protocol layer.

What is x402?

The HTTP 402 Payment Required status code was reserved in 1999 but never standardized. The x402 protocol finally gives it meaning:

1. Server returns 402 with payment requirements
2. Client makes a stablecoin payment
3. Client retries request with payment proof
4. Server verifies on-chain and serves the content

This enables machine-to-machine payments, pay-per-API-call billing, and AI agent commerce.

Inzi + x402

Inzi is tracking x402 development and plans to support:

• x402-compatible checkout endpoints — merchants can accept x402 payments through Inzi
• Inzi as x402 facilitator — abstract multi-chain settlement for merchant APIs
• AI agent payments — autonomous agents can pay for services via Inzi’s x402 gateway

Why it matters for developers

If you’re building:

• APIs with paid tiers — x402 lets clients pay per-request without subscriptions
• AI agents — agents can autonomously pay for data, compute, or services
• Content paywalls — micropayments without credit card friction

Inzi will handle the blockchain settlement so you just add an x402 middleware to your API.