> ## Content Index
> Fetch the complete content index at: https://claudefox.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Brave Search API now takes per-request payments over x402, with no account or API key
- URL: https://claudefox.com/brave-search-api-x402-agent-payments/
- Published: 2026-11-13T10:07:35.000Z
- Updated: 2026-11-20T03:29:26.000Z
- Description: Brave's Search API now accepts pay-per-request payments through the x402 protocol, so an agent can search without an account or API key. The eight paid paths cost $0.005 each in USDC on Base. How the payment loop works and how to try it with purl.
- Author: hupicake
- Tags: Tools

*Updated November 20, 2026: Expanded with the payment headers, a working purl command, the endpoint list and what is not sold yet.*

Brave announced on November 12 that its Search API accepts payments through x402, an open protocol built on the HTTP 402 Payment Required status code. Instead of signing up, choosing a plan and managing an API key, a developer or an autonomous agent pays for each search as it makes it, in USDC stablecoin on the Base blockchain. The signed payment acts as the credential.

## How a paid request works

The paid service runs at search.agent.s.brave.app, with the same paths as the regular api.search.brave.com and query parameters passed through unchanged. Brave's agent-facing instructions describe the loop:

- Send the request with no payment. Brave answers 402 with an empty body; the price and payment details sit in a Payment-Required header (base64 JSON).
- Sign a USDC payment that matches one of the offers in that challenge, unchanged. A modified amount, asset or recipient is refused.
- Retry the identical request with a Payment-Signature header.
- Brave verifies the payment, runs the search, settles, and returns results with a Payment-Response receipt for the Base transaction.

A few rules matter for anyone writing retry logic. Challenges expire, and an x402 offer is payable for 300 seconds, so fetch a fresh 402 rather than reusing an old one. Only x402 version 2 is accepted; an older client's X-Payment header is not recognised and just gets another 402\. Sending an Authorization header alongside the payment returns a 400\. There is no session or balance: each request carries its own payment, and a receipt covers that one response. Because Brave verifies first and settles only after the search runs, a failed search is never charged and retrying it costs nothing extra.

## Try it with purl

Brave points to purl, a curl-like command-line tool from Stripe for HTTP requests that require payment. Install it with Homebrew, add a wallet (purl recommends a dedicated one), fund it with Base-native USDC, then buy a search:

```
brew install stripe/purl/purl
purl wallet add
purl --max-amount 5000 'https://search.agent.s.brave.app/res/v1/web/search?q=rust'
```

The --max-amount flag caps what purl will pay, in the token's base units, and 5000 is exactly one search, or $0.005\. purl also has --dry-run to preview a payment, --confirm to ask before paying, inspect to show a resource's payment requirements and balance to check your wallet. purl does not print Brave's Payment-Response receipt, so to confirm a payment settled you look the transfer up on the Base chain. Other x402 V2 clients, such as @x402/fetch and mppx, also work. For machine discovery, GET /openapi.json on the agent endpoint lists every paid path with its price. That document is cached for five minutes and does not include the payment recipient, which comes only from the live 402 challenge, so Brave treats the 402 as the authoritative price.

## Errors you will meet

- 402 with a "did not verify" body: the payment matched no current offer, was already used, or was refused. Fetch a fresh 402 and pay exactly what it advertises.
- 502 "payment facilitator unavailable" or "upstream error", and 503: not charged; retry later.
- 502 "payment could not be settled": the search ran but the money did not move and the result is withheld. Retry with a new payment; the same one is refused.
- 404 means the path is not sold; 405 means use GET or HEAD.

## What it costs and what is included

The paid paths, web search, LLM Context (Brave's endpoint for grounding agents), news, video, image, place search, points of interest and descriptions, each cost 5000 base units: $0.005 per request or $5 per 1,000\. Brave says it will cover Base transaction fees for a limited time, without giving an end date, and that other networks and stablecoins are coming.

Some endpoints are not sold this way. The Answers API bills per query and per token (on the regular plan, $4 per 1,000 requests plus $5 per million tokens), which one fixed price cannot express. Autosuggest and Spellcheck cost less than the fee for settling a single payment, so they wait on batching many queries into one payment. Those three still need a regular API key. The Summarizer is not offered at all, because Brave has deprecated it.

## x402 or a regular plan?

Brave's regular Search plan charges the same $5 per 1,000 requests, includes $5 in free credits every month and offers 50 queries per second. It runs on prepaid credits, not a subscription, though signing up asks for a credit card; invoicing is listed only for Enterprise. Brave's announcement does not mention free credits, rate limits or support for x402 payments. The trade is setup: instead of an account, you hold a wallet funded with Base-native USDC and manage that wallet yourself. In our view, x402 suits an agent that needs search now and then, or a short experiment where nobody wants to create accounts. For steady volume, the account plan and its monthly credit look easier to manage.

## Related on claudefox

- [DeepSeek opens its app's search, file, voice and safety features to the API](https://claudefox.com/deepseek-app-api-search-ocr-asr-tts-pricing/)
- [Google's Gemini Decisions API scores up to 1,000 yes/no and multiple-choice questions in one call](https://claudefox.com/gemini-decisions-api-fast-classification/)

## Our take

Brave's version is easy to follow: a well-known API, a flat price per call and a documented loop an agent can run on its own. The never-charged-on-failure rule and the --max-amount cap limit what a single bad call can cost, but in our view you should still give an agent a dedicated wallet, as purl recommends, and keep only a small balance in it. Whether other APIs adopt the same pattern will decide, in our opinion, whether agent wallets become routine.

Source: [The Brave Search API now accepts agentic payments via the x402 protocol (Brave)](https://brave.com/blog/search-api-agentic-payments/?ref=claudefox.com), [Agent payments (Brave Search API documentation)](https://api-dashboard.search.brave.com/documentation/guides/agent-payments?ref=claudefox.com), [llms.txt for the Brave Search agent endpoint](https://search.agent.s.brave.app/llms.txt?ref=claudefox.com), [stripe/purl (GitHub)](https://github.com/stripe/purl?ref=claudefox.com), [Brave Search API plans](https://brave.com/search/api/?ref=claudefox.com)

This story first appeared in the [claudefox daily briefing for November 13, 2026](https://claudefox.com/daily-2026-11-13/).