Brave Search API adds per-request x402 payments in USDC for AI agents

What Brave announced

Brave has wired the x402 payment protocol into its Search API, turning the developer product into something that can be paid for one request at a time. According to the company's announcement, which reached the Hacker News front page, developers and autonomous AI agents can now query Brave's own web index and settle each call in real time, without signing up for an account, picking a plan or managing a traditional API key.

The payment rails are crypto-based. Brave operates its own facilitator that accepts USDC stablecoin on the Base blockchain, and says support for additional networks and other stablecoins is on the way. The intended workflow is simple for agent operators: fund a wallet with USDC over Base, and the agent pays for exactly what it consumes, whether that is the "LLM Context" endpoint built to ground model answers in search data, or general web, news, image, video and local search.

How the payment flow works

The mechanism rests on the HTTP status code the protocol is named after: 402, "Payment Required." Brave says its x402-enabled endpoints demand payment on every request instead of authentication.

An unpaid request gets an HTTP 402 response that quotes the price of that specific search along with the payment details needed to settle it. The calling agent then signs a USDC payment for that amount and retries the request with the signed payment attached. Once Brave verifies the payment, the search runs and the results come back together with a receipt for the transaction, which is recorded on the Base blockchain.

Because every request carries its own payment, Brave notes that a Search API account is no longer needed to use the service at all.

Pricing and setup

Pricing follows Brave's published API rates. LLM Context, the endpoint designed to hand agents search context for grounding their responses, is listed at $0.005 per request, or $5 per 1,000. The web, news, image, video and local endpoints carry the same rate. Gas fees for transacting on Base will be covered by Brave for a limited period.

For setup, Brave points to Purl Wallet, a command-line wallet for agents developed by Stripe. Install it, top it up with Base-native USDC, and the agent can begin querying straight away, with no provisioning step in between.

Why it matters

This is a notable production deployment of the open x402 protocol by an established search provider, and it points at a plausible future for how software, and especially AI agents, buy services from other software.

The traditional API model assumes a human somewhere in the loop: someone signs up, chooses a plan, receives a key and wires it into configuration. That friction is tolerable for applications with steady usage, but it fits autonomous agents poorly. An agent's consumption is unpredictable and often short-lived, and per-request settlement matches that reality far better than prepaid tiers. With x402, an agent can discover a price in a 402 response, pay it and receive the result, all without an account ever existing.

The Stripe connection is also worth noting. Purl, the recommended wallet, is a Stripe-built tool, which suggests serious payments-infrastructure interest in machine-to-machine commerce rather than a purely crypto-native experiment.

There are caveats. Adopters must be comfortable operating wallets and stablecoin balances, gas fee coverage is temporary, and the model binds usage to on-chain settlement, which not every organisation will accept. But as a demonstration that metered, self-serve, pay-per-call access to a mainstream search index can work in practice, Brave's launch is one of the clearest signals yet that agentic payments are moving from concept to shipping product.