A bill instead of a login

Send an unpaid request to a supported path on Brave's x402 proxy and it answers with HTTP 402, Payment Required. The response carries a machine-readable invoice: what the request costs, which token, which chain, who gets paid, and how long the offer stands.

According to Brave's documented flow, the agent signs a USDC payment for that amount and sends the request again with the payment attached. Brave verifies it, runs the search, and returns the results with a transaction receipt from the Base blockchain. There is no signup form, no key to rotate, and no monthly invoice. Brave says developers can start through Purl Wallet, a command-line wallet built by Stripe: fund the wallet with Base-native USDC and the agent can query.

The number to read twice

The price is $0.005 per request, or $5 per 1,000. That figure applies to LLM Context, Brave's endpoint that returns pre-extracted context for agents, and to the web, news, image, video and local search paths the proxy sells.

It is also the published rate for Brave's ordinary keyed API. The x402 route is not a discount on the request rate, and the announcement establishes a different payment route, not a lower published price. What a buyer gains is operational: an agent that already holds a wallet can purchase search on demand, in units of one query, without a human first creating an account and provisioning a key. Total transaction cost is a separate question while Brave covers Base gas fees, and only for a limited time.

Where the limits sit

The launch is narrower than the headline. Payment is USDC on Base only. Brave runs its own facilitator, the party that verifies and settles the payment, and says other networks and other stablecoins are coming, without a date. Gas fees on Base are covered for a limited time, again without an end date stated in the November 12 announcement. Both phrases are time-sensitive terms; treat them as current as of November 12, 2026, not as permanent features.

The proxy sells exactly eight paths, listed in Brave's own machine-readable file for the service, and a path outside that list returns a plain 404 rather than a payable 402. The exclusions have their own reasons. Autosuggest and Spellcheck are not sold because, in the file's words, those calls cost less than the fee a facilitator takes for settling one payment, so they wait on settling many queries together as one payment. Answers is not sold because it bills per query and per token, which one fixed price cannot express. The Summarizer is not sold because Brave has deprecated it. Per-request payment has a floor, and the cheapest endpoints fall under it.

An independent probe published on November 13 read an unpaid 402 response directly and found exactly one entry in its list of accepted payments: Base, USDC, $0.005, expiring after 300 seconds. There is no menu and no negotiation. The probe's author is also clear about what was not tested. No payment was completed, so the pay-then-retry loop was not verified end to end, and the covered-gas claim can only be checked in a settled transaction. The 402 invoice itself does not name the facilitator; Brave's blog post says Brave runs its own, but the invoice a client actually receives does not prove that on its own. Brave's machine-readable file says the same thing from the other side: the recipient comes from the 402 challenge at pay time.

Wallet permissions replace account provisioning

Search is a dependency most agents cannot build for themselves. Brave adds a wallet-funded alternative to its account-and-key route, and the purchase becomes something the agent itself can complete, at runtime, for half a cent. If other infrastructure follows, the practical question for agent builders shifts from "which accounts have we provisioned" to "which wallets have we funded, and what may they spend."

That shift cuts both ways. A key can be revoked centrally and its spending is visible on one invoice. A wallet's authority is set by its own permissions, and each 402 response re-states its own price: the 402 is, in Brave's own file's words, the authoritative statement of what a request costs. Deployers should check wallet permissions, spending limits and how the client validates each 402 price before authorizing payment.

Sources

  1. [1] Brave, "The Brave Search API now accepts agentic payments via the x402 protocol" (official blog, November 12, 2026)Read source
  2. [2] Brave, Brave Search x402 proxy documentationRead source
  3. [3] Brave, x402 proxy machine-readable guide (llms.txt; eight paid paths, exclusion reasons, 402 as authoritative price)Read source
  4. [4] Brave, x402 proxy OpenAPI document (paid paths with prices)Read source
  5. [5] Independent probe, "$0.005 per search: I read Brave's 402 invoice for agents" (dev.to, November 13, 2026)Read source