# How to let agents pay you, with x402 (slim)

> An agent can't sign up, add a card or copy an API key. x402 lets it pay inside the HTTP request instead. How a payment goes, who runs the standard, and the fifteen tools we list that accept it, with their prices.

- Full: https://www.anchorterminal.com/blog/how-to-let-agents-pay-you.md (~1,450 tokens) · this version ~930 tokens · JSON https://www.anchorterminal.com/blog/how-to-let-agents-pay-you.json · canonical https://www.anchorterminal.com/blog/how-to-let-agents-pay-you
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-14

## One request, start to finish

x402 is an open standard for paying for something over HTTP as part of the request [[1]](#ref-1).

1. The agent asks for the endpoint like any other web request.
2. The server answers with status 402 Payment Required and what it costs.
3. The agent pays, usually in a dollar stablecoin, from a wallet its owner funded.
4. It sends the same request again with proof of the payment, and gets its answer.

There's no account and no key anywhere in that, and the site says the protocol itself takes no fee, only the payment network's [[1]](#ref-1).

## Why it matters if you want agents to use you

Most APIs start with a person signing up in a browser, confirming an email, adding a card and copying a key, and an agent can't do any of that on its own.

It's also how [letme](/letme/) will pay.

## Who accepts it today

Fifteen of the 966 tools we list accept x402 on their own endpoints, and 23 more support it in part, on some endpoints, through a third party or only as tooling for paying others [[6]](#ref-6).

| Tool | What it does | Cheapest per request |
| --- | --- | --- |
| [Spider](/tools/spider-cloud) | Web scraping | $0.0002 |
| [Exa](/tools/exa-mcp) | Web search | $0.001 |
| [Honcho](/tools/honcho) | Agent memory | $0.001 |
| [Hyperbrowser](/tools/hyperbrowser) | Browser automation | $0.001 |
| [Massive](/tools/massive) | Market data | $0.01 |
| [CoinMarketCap](/tools/coinmarketcap-x402-api) | Crypto data | $0.01 |
| [CoinGecko](/tools/coingecko-x402-api) | Crypto data | $0.01 |
| [Linkup](/tools/linkup) | Web search | $0.01 |
| [Nansen](/tools/nansen-x402-api) | On-chain data | $0.01 |
| [Steel](/tools/steel) | Browser automation | $0.01 |
| [Apify](/tools/apify-mcp) | Web scraping | $1 |
| [AgentMail](/tools/agentmail) | Agent inboxes | $2 |
| [BlockRun.AI](/tools/blockrun-ai) | Model inference | not recorded |
| [Browserbase](/tools/browserbase) | Browser automation | not recorded |
| [Browser Use](/tools/browser-use) | Browser automation | not recorded |

Every priced endpoint we recorded with a network runs on Base [[6]](#ref-6).

## If you add it

Put x402 on every paid endpoint, not one, because partial support is what most of the 23 have, and an agent that meets a 402 on one call and a sign-up wall on the next gives up.

## References

Read on 10 October 2026.

[1] x402, the protocol's site.

[2] IETF, RFC 9110 HTTP Semantics, section 15.5.3, 402 Payment Required.

[3] Decrypt, Coinbase and Linux Foundation launch x402 Foundation, 2 April 2026. Source for who built x402, its 2025 launch and the foundation's members.

[4] Anchor Terminal, the benchmark's Payments & pricing checklist.

[5] Anchor Terminal, Why we built Anchor Terminal, 8 October 2026. Source for letme's plan to pay over x402. https://www.anchorterminal.com/blog/why-we-built-anchor-terminal

[6] Anchor Terminal, the directory, 10 October 2026. Source for the tools accepting x402, their cheapest priced endpoints and the network.

[7] Anchor Terminal, For builders, Claiming.

---

- Older: [How to make your site and tool ready for agents](https://www.anchorterminal.com/blog/how-to-make-your-site-ready-for-agents.md)
- Newer: [How to make your tool agent-ready](https://www.anchorterminal.com/blog/how-to-make-your-tool-agent-ready.md)
- All posts: https://www.anchorterminal.com/blog/index.md