Brave has added a pay-per-request route to its Search API for software agents. Instead of creating a Brave API account and attaching a long-lived API key, a client can pay for each eligible query through the x402 protocol using USDC on the Base network. Brave announced the change on November 12. It is a new way to buy search requests, not a new search index or a guarantee that an agent's answer is correct.
What happens when an agent makes a request?
The flow is built around HTTP 402, the status code for Payment Required. A request to the agent-facing endpoint without payment receives a response describing the price and payment options for that request. A compatible client signs the stablecoin payment and retries the same request with that signed payment attached. After verification, Brave returns the search response and a payment receipt. The signed payment functions as the credential for that individual request; the developer does not first create a Search API account or manage a conventional API key for this route.
Brave's announcement describes a facilitator that accepts USDC on Base. Its documentation says `https://search.agent.s.brave.app` provides the API without an account or key, and that each request carries its own payment. The 402 response is the authoritative price for a specific request. Developers can also inspect the endpoint's OpenAPI description to see the currently listed paid paths and their prices.
What does one search cost?
Brave's announcement lists $0.005 per request, or $5 for 1,000, for LLM Context and the web, news, image, video and local search endpoints. The announcement says Base gas fees are covered for a limited time; it does not promise that they will remain covered indefinitely. Because rates and routes can change, the live 402 response and API documentation should be checked before an agent pays.
The API guide says Answers, Autosuggest and Spellcheck are not available through this x402 endpoint and still require an API key. So this is not a replacement for every Brave Search API feature. Brave also says other payment networks and stablecoins are planned, but the announcement does not describe them as available today.
Brave announcement: supported search endpoints, published rates and Base gas promotion
Brave agent-payments guide: 402 handshake, current endpoint and price discovery
What developers need to handle
The agent needs a funded wallet and a client that can create the payment, respect a spending ceiling and retry correctly. Brave points to Purl, a command-line wallet, as one route for testing. A per-request price makes the cost easy to reason about, but an automated loop can still make many requests. Developers should define maximum payments and request budgets in their own code, keep wallet keys outside prompts and logs, and record receipts alongside the work that caused each search. Those are implementation safeguards, not controls Brave says it applies on a developer's behalf.
This payment design can suit an agent that needs occasional web grounding without a separately provisioned API plan. A long-running or high-volume service still needs to compare total spend, wallet operations, rate limits and support needs with conventional account-based billing. A search receipt shows a payment occurred; it does not certify that the returned result is relevant or that the agent used it faithfully.
For makers, the notable change is that a software workflow can acquire search one request at a time. The useful design question is therefore not only which search endpoint to call, but also which agent is allowed to spend, how much it can spend, and what evidence the application keeps when a query is paid for.
Compare an agent-powered web-answer API and its access model