AI NewsInfrastructureAnnouncement

Brave Search API now takes agent payments over the x402 protocol

Brave says its Search API now accepts pay-per-query payments through the x402 protocol. An agent can query the index without an account or an API key.

AI News

Editorial2 min read

LinkedInX
Brave Search API now takes agent payments over the x402 protocol

Why it mattersAn agent that pays for a search without an account changes who the buyer is. The agent becomes the buyer, with its own log of what it spent.

An agent that searches the web still asks a person for an API key before it can type a query. Brave says that step is now optional for its own index. The Brave Search API takes payments one query at a time, over the x402 protocol. Brave wrote that on 12 November 2026. An agent can query the index, ground an answer, and pay for the call in one request. No account is needed.

The price Brave lists is $0.005 per query. That is $5 per 1,000 requests. The LLM Context endpoint and the web, news, image, video and local endpoints are all in. Each request is settled in USDC on Base, a chain built on Ethereum. Brave says gas fees on Base will be covered for a limited time. Other chains and other stablecoins are planned.

What x402 does in this flow

x402 is an open standard for machine-to-machine payment over plain HTTP. A caller makes a request. The server answers with a short bill. The caller signs a USDC transfer that pays it. The request goes through. The server returns the search result. An agent runs the same loop by itself, with a wallet it already has.

Two other x402 steps have already landed. Cloudflare opened a public beta of its own x402 gateway on 30 September 2026. The vAPI project on GitHub, a buyer-side wallet for the protocol, reached 2,210 stars. The new thing is that an independent search index now lists a per-query price in the protocol's own units.

What a developer can now do

A team that runs an agent can skip the sign-up flow for Brave Search. The agent pays for each question as it asks it. An outer system can cap the daily spend by capping the wallet. A team that uses three search services today can let the agent pick which one to ask by price.

The limits are real. The price is Brave's own and will change. The USDC-on-Base assumption is one chain, one stablecoin and one network's gas model. A team that pays with a different unit has to wait. A signed transfer per request is slower than a cached API key. Pay-per-query has to close that gap for a serving path that needs low latency.

For a team deciding how an agent buys its own tools, the shape matters more than the price. An agent that pays a vendor on its own has its own spending log. No shared account hides the calls. That is what a team builds for when it builds for agents. Brave's own search is now wired that way.

Source

SourceBrave

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX
Start a project