# What Is the x402 Protocol? HTTP 402 Payments for AI Agents

DevFeed: [What Is the x402 Protocol? HTTP 402 Payments for AI Agents](<https://devfeed.tech/articles/what-is-the-x402-protocol-http-402-payments-for-ai-agents-10450.md>)

Original publisher: [Read original article](<https://dodopayments.com/blogs/x402-protocol/>)

Author: Ayush Agarwal

Published: 2026-09-08T00:00:00Z

Content type: article

Language: en

Sources: [Dodo Payments Blog](<https://devfeed.tech/sources/dodo-payments-blog.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [API Monetization](<https://devfeed.tech/topics/api-monetization.md>), [A2A protocol](<https://devfeed.tech/topics/a2a-protocol.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [a2a](<https://devfeed.tech/tags/a2a.md>), [about](<https://devfeed.tech/tags/about.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [card](<https://devfeed.tech/tags/card.md>), [guide](<https://devfeed.tech/tags/guide.md>), [handshake](<https://devfeed.tech/tags/handshake.md>), [headers](<https://devfeed.tech/tags/headers.md>), [http](<https://devfeed.tech/tags/http.md>), [payment](<https://devfeed.tech/tags/payment.md>), [payments](<https://devfeed.tech/tags/payments.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [rails](<https://devfeed.tech/tags/rails.md>), [required](<https://devfeed.tech/tags/required.md>), [what-is](<https://devfeed.tech/tags/what-is.md>), [works](<https://devfeed.tech/tags/works.md>), [x402](<https://devfeed.tech/tags/x402.md>), [x402-protocol](<https://devfeed.tech/tags/x402-protocol.md>)

## AI overview

x402 lets a client pay for one resource request without an account or API key: the server returns HTTP 402 with payment requirements, the client signs a payment and retries with `PAYMENT-SIGNATURE`, and the server verifies and settles it before returning the resource. An optional facilitator handles `/verify` and `/settle`, sparing the seller chain infrastructure; servers can also handle those steps themselves. The protocol supports multiple payment options, but a transaction requires the client and facilitator to support the same scheme and network. Its `exact` scheme covers fixed amounts; other schemes remain under development. x402 suits machine-to-machine micropayments, but requires a funded wallet and token settlement and does not provide subscriptions, chargebacks, tax handling, invoicing, or fiat payouts. The article recommends pairing it with a separate billing rail when serving human subscribers.

## Source excerpt

A technical guide to the x402 protocol: how the HTTP 402 payment handshake works, the PAYMENT-REQUIRED and PAYMENT-SIGNATURE headers, facilitators, payment schemes, and where x402 fits next to card rails.