500xEngineer.

All postsSHORT2 min read

Brave Search Lets AI Agents Pay With x402 Without an Account

Brave Search costs $0.005 per request over x402. How USDC payments replace API keys, what our unpaid 402 test showed, and the catch.

Half a cent buys your agent a Brave search. How does it pay without an account? The signed USDC payment is the credential. We sent an unpaid request ourselves and got the price back in an HTTP 402 response.

Video not loading? Watch the Short on YouTube

What changed

Brave announced x402 support for its Search API on Nov 12, 2026. An agent can pay for each request without creating a Brave Search API account, choosing a plan or managing an API key.

x402 is an open standard for payments over HTTP. Brave currently accepts USDC on Base. It says support for other networks and stablecoins is planned.

How a paid request works

An unpaid request receives HTTP 402 Payment Required with the price and payment details. The agent signs a USDC payment for that amount and retries with the signed payment attached. Once verified, the search runs and returns results with a receipt of the transaction on Base.

Each request carries its own payment. The agent can't choose its own price: Brave checks the payment against the requested path's price. The 402 response is the authoritative quote for that request.

What our 402 test showed

On Nov 13, 2026, we sent an unpaid web search request to:

https://search.agent.s.brave.app/res/v1/web/search?q=rust

It returned HTTP/2 402. The decoded payment-required header said Payment required, with amount 5000, asset name USD Coin and network eip155:8453, which is Base mainnet. Brave's agent instructions identify 5000 token base units as $0.005.

That test confirms the unpaid response and quoted price. The paid retry and results flow above comes from Brave's documentation.

What it costs

A search costs $0.005, or $5 per 1,000. That's the same as Brave's regular API rate. The listed x402 endpoints include LLM Context, web, news, image, video and local search.

Brave covers Base gas fees for a limited time. That coverage is temporary.

The catch

You need a wallet funded with USDC on Base. Brave points to Stripe's purl, a CLI for HTTP requests that require payment, as the easiest client to start with. The purl README recommends a dedicated wallet.

Answers, Autosuggest and Spellcheck still require an API key. They aren't sold through this x402 service yet.

Start with the Brave agent payments docs for the request and wallet setup.

The builder angle (my opinion, no income guaranteed)

I'd offer an x402 setup to a client who owns an API or a data service. Add the payment middleware, set a price per call, then list the endpoint in the x402 directories so agents can buy the data without signup.

The x402 repo shows one middleware call in its server example. Its directory list includes x402scan.com, Agentic.Market, Pay.sh, app.ampersend.ai/discover and x402-list.com.

For production mainnet routes, the project says to choose a facilitator explicitly: use a production facilitator provider, run your own, or self-facilitate. The public x402.org facilitator isn't the assumed production path for mainnet EVM routes.

That's the setup service I'd pitch. It's an offer idea, with no income guaranteed.

Daily email

Get each breakdown in your inbox.

One email each evening, right after the Short goes live: the AI tool it covers, the full write-up with sources, and how to get paid for it. Free, and you can unsubscribe anytime.

Read past emails on Substack

Sources

All postsWatch on YouTube