Brave Search API Adds x402: Agents Can Pay for Individual Queries Instantly Without an Account or API Key

A new settlement path for the search API

Brave announced on November 12 that its Brave Search API accepts instant, pay-per-request payments through x402. In Brave's description, a developer or autonomous agent needing search sends a request, receives a payment requirement, settles it from a command-line wallet, then gets the result. The flow does not require creating an account first, selecting a plan or storing a conventional API key. x402 is an open HTTP payment protocol; Brave currently accepts USDC on Base through its own facilitator and says other networks and stablecoins are to follow.

This does not turn public Brave Search into a paid gate. The change is for Search API callers, which use Brave's own index to add web results to an agent's answers. Developers who need occasional retrieval and do not want to distribute keys to every deployment may have fewer account and key-management steps, but wallet custody, payment approval and network choice become their responsibility.

The $0.005-per-query claim

Brave's post lists $0.005 per request, or $5 per 1,000, for endpoints covering human web search, news, images, video and local search. Its API privacy page also confirms that the Base/USDC x402 micropayment is an alternative to card payment. The post says endpoints for LLM grounding can also settle on demand, but it does not state that every endpoint has the same price. Integrators should check the current API pricing and returned payment requirement before connecting it.

Keyless does not mean unmanaged

Removing the API key does not remove sensitive credentials: the agent's environment must still hold a wallet and authority to make USDC payments. Brave says its facilitator handles settlement, but the announcement does not promise that every network, currency or region is available at once, nor does it set a default policy for automatic agent spending. Before making this a production retrieval path, teams should cap individual and cumulative spend, define a fallback for payment failure, and ensure private keys do not enter logs or container images.