{
  "data": {
    "faq": null,
    "kicker": "Research · Get found by agents · 14 October 2026",
    "lede": "An agent can find your tool and still not use it, because it can't sign up, add a card or copy a key. x402 lets it pay in the request itself. Fifteen of the tools we list accept it, from a fiftieth of a cent a call."
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/blog/how-to-let-agents-pay-you",
    "json": "https://www.anchorterminal.com/blog/how-to-let-agents-pay-you.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/blog/how-to-let-agents-pay-you.md",
    "slim": "https://www.anchorterminal.com/blog/how-to-let-agents-pay-you.min.md"
  },
  "markdown": "## One request, start to finish\n\nx402 is an open standard for paying for something over HTTP as part of the request [[1]](#ref-1). Say an agent wants a price from a crypto data API that charges per call.\n\n1. The agent asks for the endpoint like any other web request.\n2. The server answers with status 402 Payment Required and what it costs.\n3. The agent pays, usually in a dollar stablecoin, from a wallet its owner funded.\n4. It sends the same request again with proof of the payment, and gets its answer.\n\nThere'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). HTTP has reserved the 402 status for future use for a long time [[2]](#ref-2). Coinbase's developer platform built x402 on it and launched it in 2025, and in April 2026 it moved to the x402 Foundation under the Linux Foundation, with Google, Stripe, Visa, Mastercard, Shopify and Cloudflare among the members [[3]](#ref-3).\n\n## Why it matters if you want agents to use you\n\nMost 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. With x402 it needs a funded wallet and nothing else. That's why our benchmark gives a machine payment protocol on a tool's own endpoints 40 of the 100 points in Payments \u0026 pricing [[4]](#ref-4), and why a tool that adds it moves up in [pay per call](/categories/pay-per-call).\n\nIt's also how [letme](/letme/) will pay. letme routes an agent's request to the best tool for it, and we're working on x402 so the payment can happen in the same call, without the agent holding an account with every vendor [[5]](#ref-5).\n\n## Who accepts it today\n\nFifteen 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). These are the fifteen, with the cheapest priced endpoint we recorded.\n\n| Tool | What it does | Cheapest per request |\n| --- | --- | --- |\n| [Spider](/tools/spider-cloud) | Web scraping | $0.0002 |\n| [Exa](/tools/exa-mcp) | Web search | $0.001 |\n| [Honcho](/tools/honcho) | Agent memory | $0.001 |\n| [Hyperbrowser](/tools/hyperbrowser) | Browser automation | $0.001 |\n| [Massive](/tools/massive) | Market data | $0.01 |\n| [CoinMarketCap](/tools/coinmarketcap-x402-api) | Crypto data | $0.01 |\n| [CoinGecko](/tools/coingecko-x402-api) | Crypto data | $0.01 |\n| [Linkup](/tools/linkup) | Web search | $0.01 |\n| [Nansen](/tools/nansen-x402-api) | On-chain data | $0.01 |\n| [Steel](/tools/steel) | Browser automation | $0.01 |\n| [Apify](/tools/apify-mcp) | Web scraping | $1 |\n| [AgentMail](/tools/agentmail) | Agent inboxes | $2 |\n| [BlockRun.AI](/tools/blockrun-ai) | Model inference | not recorded |\n| [Browserbase](/tools/browserbase) | Browser automation | not recorded |\n| [Browser Use](/tools/browser-use) | Browser automation | not recorded |\n\nEvery priced endpoint we recorded with a network runs on Base [[6]](#ref-6). Fifteen out of 966 is under 2%, so whoever adds it now stands out.\n\n## If you add it\n\nPut 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. Publish the price per request on a public page as well as in the 402 response, so an agent can compare before it calls. Then claim your listing on Anchor Terminal and send us the endpoints, so the listing shows them with their prices and they appear on our [x402 page](/x402/) [[7]](#ref-7).\n\n## References\n\nRead on 10 October 2026.\n\n[1] x402, the protocol's site. Source for the payment flow and zero protocol fees. https://www.x402.org/\n\n[2] IETF, RFC 9110 HTTP Semantics, section 15.5.3, 402 Payment Required. Source for the status being reserved for future use. https://www.rfc-editor.org/rfc/rfc9110#name-402-payment-required\n\n[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. https://decrypt.co/363173/coinbase-linux-foundation-launch-x402-foundation\n\n[4] Anchor Terminal, the benchmark's Payments \u0026 pricing checklist. Source for the 40 points for a machine payment protocol. https://www.anchorterminal.com/benchmark/\n\n[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\n\n[6] Anchor Terminal, the directory, 10 October 2026. Source for the tools accepting x402, their cheapest priced endpoints and the network. Each listing records its x402 evidence. https://www.anchorterminal.com/x402/\n\n[7] Anchor Terminal, For builders, Claiming. Source for claiming a listing and correcting its facts. https://www.anchorterminal.com/builders/\n\n---\n\n- 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)\n- Newer: [How to make your tool agent-ready](https://www.anchorterminal.com/blog/how-to-make-your-tool-agent-ready.md)\n- All posts: https://www.anchorterminal.com/blog/index.md\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-10",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Blog",
        "url": "https://www.anchorterminal.com/blog/"
      },
      {
        "name": "Let agents pay you",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": [
      "Anchor Terminal research",
      "14 October 2026"
    ],
    "h1": "How to let agents pay you, with x402",
    "image": "https://www.anchorterminal.com/assets/og/blog-agents-pay-you.png",
    "path": "/blog/how-to-let-agents-pay-you",
    "published": "2026-10-14",
    "section": "blog",
    "title": "How to let AI agents pay you per request with x402 | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-14",
    "url": "https://www.anchorterminal.com/blog/how-to-let-agents-pay-you"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 930
  },
  "version": 1
}