Brave Search API Takes USDC Per Request, No API Key, at $0.005 a Call

Brave Search API will take a stablecoin payment on each request instead of an account and an API key, Brave said in a November 12 post. The price listed for every covered endpoint is $0.005 a request, paid in USDC on the Base network.

The mechanism is the x402 protocol, which revives the HTTP 402 "Payment Required" status code. According to Brave's announcement, an unpaid request gets a 402 response listing the price and payment details. The caller signs a USDC payment for that amount and retries with the payment attached. Brave verifies it, runs the search and returns a transaction receipt with the results.

The post says "a Brave Search API account is no longer needed to use the service." Brave runs its own payment facilitator, the service that verifies and settles each payment. It suggests Purl, a command-line wallet developed by Stripe, as the client, and says gas fees on Base are covered "for a limited time" without giving an end date.

What the $0.005 covers, and what it does not

Web, news, image, video, local and LLM Context endpoints are all priced at $0.005, or $5 per 1,000 requests, which the post says follows Brave's published API rates. LLM Context is the endpoint meant for grounding an agent's answers.

The documentation page narrows the list. Paid requests go to search.agent.s.brave.app, a different host from the usual api.search.brave.com, with the same paths and query parameters. Answers, Autosuggest and Spellcheck are not covered and still need an API key.

Here is the sticking point. The announcement says $0.005. The docs page does not repeat that figure, calls the 402 response "the authoritative price" and points readers to an llms.txt file. Its only worked example passes --max-amount 10000, which the page says equals $0.01. That is a ceiling on what the client will pay, not the price, but a reader copying the example would authorise twice what the post advertises.

Item	Brave	Tavily
Price per request	$0.005	$0.01
Network and asset	USDC on Base	USDC on Base
Account or key needed	No	No

How it compares with Tavily and Linkup

Brave is not first. Tavily's x402 documentation lists a POST endpoint at x402.tavily.com/search at $0.01 a call, always at the advanced search depth, on Base mainnet. Tavily says it refunds USDC automatically to the signing wallet if its upstream call fails after settlement, and recommends self-custodied wallets for production because refunds to exchange wallets land at the exchange.

Linkup published the same flow on May 5. Its post, written by co-founder and CEO Philippe Mizrahi, says payments settle through Coinbase's facilitator and results come back with a transaction hash. The post does not list a price.

1. Brave Search API0.01 USD
2. Tavily (advanced depth)0.01 USD

Source: Brave announcement and Tavily x402 documentation, accessed 2026-11-13

The two prices are not like for like. Tavily's endpoint is fixed at advanced depth and Brave's is a plain index lookup, so a per-call comparison says nothing about result quality.

What agent builders still have to work out

Brave's pages do not state rate limits, a refund policy, a minimum balance, or the list of other networks and stablecoins it calls "coming soon." The docs also do not name the facilitator's chain or the specific stablecoin, which the blog post supplies. Anyone wiring this into an agent has to read two pages to assemble one answer.

The task it fits is narrow: an agent with a funded wallet that needs a handful of searches and has no human to open an account. Agent tooling is spreading fast on GitHub, where Chrome's Modern Web Guidance for coding agents gained 1,875 stars in a day. Not every business is welcoming agents, though: United revised its contract of carriage on November 11, and Rule 6.J.6 bars AI agents from making or servicing tickets.

Brave has not said when the first non-Base network arrives, and the docs list no date.