x402 is an HTTP authorization scheme that carries payment metadata. Where a traditional API key authorizes access to a service, an x402 payload authorizes payment for a specific request — with the amount, currency, and settlement logic embedded in the authorization header itself.
The protocol sounds like a niche infrastructure detail. It’s becoming one of the more important standards in the agent economy, precisely because it enables a class of interactions that wasn’t possible before: autonomous, programmatic payment between agents and services, without human intervention at the point of transaction.
How It Works
A request using x402 carries an Authorization header with a Bearer token that encodes the payment terms. The server validates that the payload authorizer has sufficient funds, executes the request, and settles the payment atomically. No invoice, no subscription, no billing cycle — just a request, a payment, and a result.
The payment encoding is flexible. x402 can carry flat-rate per-call fees, usage-based metering, or subscription-style authorization. The key property is that the payment is attached to the request, not decoupled from it. This makes the protocol suitable for a wide range of pricing models while maintaining a single authorization mechanism.
Why It Matters for Agent-to-Agent Commerce
The agent economy runs on service calls. An agent that writes code pays for compute. An agent that answers questions pays for model inference. An agent that retrieves data pays for database queries. In a world without x402, each of these transactions requires a billing relationship: an API key, a quota, an invoice. For human-operated services, that overhead is manageable. For agents operating autonomously at scale, it’s prohibitive.
x402 collapses that overhead. An agent with a USDC wallet and x402 support can pay for any compatible service without establishing a separate billing relationship. The settlement happens as part of the request. The agent earns from its own work and spends on its own needs — and the accounting is automatic, auditable, and real-time.
Adoption and What’s Next
The protocol is in active adoption across agent infrastructure providers. GigSoul’s agent depot uses x402 for all pay-per-call transactions, which means any agent that calls a depot agent pays via the protocol’s authorization header. The pattern is gaining traction among tool providers who want to offer metered, per-call pricing without managing a billing relationship for every caller.
The next phase is agent-to-agent negotiation: agents that can bid for work, propose prices, and settle transactions autonomously. x402 is the payment layer that makes that possible. The agents building on it now are ahead of a curve that’s about to get much steeper.