# x402: which products let AI agents pay per request

9 of 151 products we drove offer x402. What it is, which products take it, and how to let agents pay you per request.

Source: https://agentdrives.com/standards/x402 · Updated 2026-10-24 · as data: https://agentdrives.com/standards/x402.json · licence CC BY 4.0

x402 is an open standard for agentic commerce: a product charges for a request with an HTTP 402 answer. The agent pays in a stablecoin and sends the request again, with no checkout or account.

## The numbers

From our drives of 151 products, 1–24 Oct 2026 (https://agentdrives.com/data/facts?via=md):

- Offer x402: 9 of 151 (https://agentdrives.com/data/facts?via=md#pay.x402)
- Offer any agent payment: 26 of 151 (https://agentdrives.com/data/facts?via=md#pay.offers_rail)
- Our side proved an agent payment: 5 of 151 (https://agentdrives.com/data/facts?via=md#pay.native)

## What it is

The current spec is protocol version 2 (spec v2.0) [1]. A server answers a paid route with 402 and the ways it accepts payment; the agent pays and sends the request again; the server answers with a receipt. Three headers carry it: `PAYMENT-REQUIRED`, `PAYMENT-SIGNATURE` and `PAYMENT-RESPONSE`. [2]

There is no checkout page, card form or sign-up [3]. A facilitator checks and settles the payment, so a seller needs no blockchain code of its own. [4]

## How many products offer it

9 of 151 products we drove offer x402, seen or paid. 26 of 151 offer at least one way for an agent to pay. At 5, our side made and proved a payment.

## How to add it

1. **Pick the routes worth paying for.** One call, one result: a search, a lookup, a render. Keep your free tier as it is.

2. **Answer them with a 402.** Put the payment requirements in the `PAYMENT-REQUIRED` header. [2] The schemes in the spec are exact, upto, batch-settlement, auth-capture [1].

3. **Settle through a facilitator.** Stripe takes x402 payments in stablecoins and settles them through the Coinbase facilitator. [5] [The pay-per-call guide](https://agentdrives.com/fixes/let-agents-pay-per-call) has the steps.

4. **Let agents find the price first.** List the paid routes in your OpenAPI document with their price. [6]

## Check it yourself

1. **Call a paid route without paying.** You want a 402 with a `PAYMENT-REQUIRED` header.

   ```
   curl -si https://example.com/api/paid-route | grep -i -E "^HTTP|payment-required"
   ```

## Products that offer x402

- [AgentMail](https://agentdrives.com/tools/agentmail.md?via=md): L4 Runs on its own
- [Apify](https://agentdrives.com/tools/apify.md?via=md): L1 Needs a person
- [Brave Search API](https://agentdrives.com/tools/brave.md?via=md): L1 Needs a person
- [Browserbase](https://agentdrives.com/tools/browserbase.md?via=md): L2 Gets in
- [Exa](https://agentdrives.com/tools/exa.md?via=md): L2 Gets in
- [Parallel](https://agentdrives.com/tools/parallel.md?via=md): L4 Runs on its own
- [Pinata](https://agentdrives.com/tools/pinata.md?via=md): L1 Needs a person
- [Steel](https://agentdrives.com/tools/steel.md?via=md): L2 Gets in
- [Tavily](https://agentdrives.com/tools/tavily.md?via=md): L3 Does the work

## Questions

**Does the agent need an account?**

No. The payment pays for the request. A product can still give a paying agent a key for later calls.

**Can I take x402 and MPP?**

Yes. A 402 can offer more than one way to pay, and Stripe takes both.

## Sources

1. [x402 specification, version 2](https://raw.githubusercontent.com/x402-foundation/x402/main/specs/x402-specification-v2.md)
2. [x402 over HTTP](https://raw.githubusercontent.com/x402-foundation/x402/main/specs/transports-v2/http.md)
3. [x402 on Coinbase Developer Platform](https://docs.cdp.coinbase.com/x402/welcome)
4. [x402: the facilitator](https://docs.x402.org/core-concepts/facilitator)
5. [x402 on Stripe](https://docs.stripe.com/payments/machine/x402)
6. [MPP: discovery](https://mpp.dev/advanced/discovery)

## More standards

- [MCP](https://agentdrives.com/standards/mcp.md): A server that turns a product's actions into tools an agent can call.
- [llms.txt](https://agentdrives.com/standards/llms-txt.md): A Markdown map of a product's docs, written for language models.
- [OpenAPI](https://agentdrives.com/standards/openapi.md): A machine-readable description of every route of an API.
- [Web Bot Auth](https://agentdrives.com/standards/web-bot-auth.md): An agent signs each request; a site's bot check can verify who sent it.
- [Signed agents](https://agentdrives.com/standards/signed-agents.md): Agents a bot-check vendor has verified, which a site can let through.
- [robots.txt for AI agents](https://agentdrives.com/standards/robots-txt-ai.md): The file that tells crawlers and agents which pages to leave alone.
- [MPP](https://agentdrives.com/standards/mpp.md): A 402 payment challenge an agent pays by card or stablecoin.
