News · 2026-11-13
Brave's Search API now accepts x402 payments: an agent pays $0.005 per request in USDC and needs no account or key
Brave announced on November 12, 2026 that its Search API accepts agentic payments through the x402 protocol: an AI agent can buy search results at $0.005 per request using a signed USDC payment, with no account, plan or API key. In Brave's design the signed payment is itself the credential, and the response includes a receipt for the transaction on the Base blockchain.
Key facts
- Who and when: Brave, November 12, 2026, in its announcement post.
- Price: $0.005 per request ($5 per 1,000), covering LLM Context (agentic grounding) and the web, news, image, video and local endpoints.
- Payment rail: USDC on Base today, with other networks and stablecoins "incoming soon"; Brave runs its own facilitator and covers Base gas fees "for a limited time."
- Docs: Brave's agent payments guide names the paid host
https://search.agent.s.brave.app.
How the flow works
Brave's post describes three steps. First, a request with no payment gets HTTP 402 Payment Required; the response states the price and payment details. Second, the agent signs a USDC payment and retries with it attached. Third, after verification the search runs, and the results return with a receipt for the transaction on Base. Because the payment is the credential, there is no signup, billing plan or key to manage, which is the point for an autonomous agent that would otherwise need a human to provision an account.
Brave's docs add practical details. The paths match those on api.search.brave.com, /openapi.json lists every paid path with its price, and agents are told to read /llms.txt before paying, with the 402 response as the authoritative price. Answers, Autosuggest and Spellcheck are not sold this way and still need an API key. The example caps a single purchase with a --max-amount option, so a per-call limit exists on the client side. Brave calls Purl Wallet, a Stripe-developed command-line wallet, "the easiest path."
What x402 is
x402 is named for the long-unused HTTP 402 status code and describes itself at x402.org as an open, neutral standard. Its claims of "millions of transactions" and zero protocol fees are the project's own and were not independently checked. Attribution of its origin to a specific company rested on a search snippet of an HN comment and is left out here for that reason. Our lesson on tool use and function calling covers how agents call external services, and our piece on scoped credentials for agents covers the other side of the access question.
Reception
The Hacker News thread had 167 points on November 13; the planning figure of 205 is likely a later snapshot. The overall mood, as far as could be checked, was mixed to skeptical about adoption and price, with some anti-crypto remarks, but individual comments were not re-read for this article.
Caveats
This is a vendor announcement, and uptake is unproven: no volume numbers were published. Per-request pricing at half a cent adds up for agents that run many searches, and the payment rail is a cryptocurrency, which some teams cannot use for compliance reasons. The structural point stands regardless: a credential that is also a payment removes account friction for agents, and shifts risk to spending limits and key custody.
Key questions
How does an agent pay Brave with x402?
How much does it cost?
Which Brave endpoints are not covered?
Cite this
APA
Ground Truth. (2026, November 13). Brave's Search API now accepts x402 payments: an agent pays $0.005 per request in USDC and needs no account or key. Ground Truth. https://groundtruth.day/news/brave-search-api-accepts-x402-agent-payments-no-account-no-api-key.html
BibTeX
@misc{groundtruth:brave-search-api-accepts-x402-agent-payments-no-account-no-api-key,
title = {Brave's Search API now accepts x402 payments: an agent pays $0.005 per request in USDC and needs no account or key},
author = {{Ground Truth}},
year = {2026},
month = {nov},
url = {https://groundtruth.day/news/brave-search-api-accepts-x402-agent-payments-no-account-no-api-key.html}
}
Comments are replies to this story on Bluesky — reply with any Bluesky account to join in.