Brave Search API vs Exa for AI agents
As of 15 Oct 2026, Exa gets an AI agent further: L2 · Gets in against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: Can't get a key.
- Use: Work not reached.
- Pay: Tried to pay: The payment failed on the seller's side.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
Stopped at key: blocked. Next: let an agent get a key on its own
Brave Search API is a web/news/image/video/place search service for developers. Without any account, an agent could run real searches in the browser-based docs playground, but getting its own API key requires an activated plan, and every plan, even the free one, needs a credit card. The agent stopped at that card form.
Driven 14 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: No key needed, pay per call.
- Use: 20% of the work.
- Pay: Pays per call for part of it: Paid $0.001 a call (x402), 15 Oct.
- Leave: Leaves on its own: Nothing to cancel, made nothing to delete.
In on its own; 20% of the work done. Next: do half of the core work (now 20%)
Gets in describes Exa today: our agent reached search and page-reading with no account at all. It never had to sign up, verify or hold a key, so no checkpoint stopped it on that path. Through the documented keyless hosted MCP server, our agent ran web search and page fetches directly. It also paid per call on Exa's own API, settling x402 charges for search and for fetching page contents, without a dashboard or stored billing details. Reaching an account hit a Cloudflare Turnstile at sign-up. The dashboard turned our agent back at a Vercel checkpoint, so answering, agent runs, websets and monitors stayed out of reach, and cancel and delete never applied.
Gets furtherDriven 15 Oct 2026 · The drive and its evidenceThe two summaries: written by our agents from each product's drive. How we write.
Where each one stops.
Brave Search APIStopped at key: blocked
ExaIn on its own; 20% of the work done
| Checkpoint | Brave Search API | Exa |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Not needed |
| Verify | In a browser | Not needed |
| Key | Blocked | Not needed |
| First call | Not reached | Headless |
| First action | Not reached | Not needed |
| Pay | Tried, not settled | Headless |
| Cancel | Not reached | Not needed |
| Delete | In a browser | Not needed |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Brave Search API | Exa | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 3 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 2 | 0 |
| Not tested (checkpoints) | 3 | 0 |
| Work done | Not measured | 20% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Brave Search API | Exa | |
|---|---|---|
| Bot check | Brave's own proof-of-work captcha ('Verifying you're a human being...') let it through at sign up | A challenge on the form stopped 2 ways in (Email and code, Sign-in for apps); it got in another way |
| Wall type | No bot-check wall | A challenge on the form |
| First wall | Card required before any API key | None |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Brave Search API | Exa | |
|---|---|---|
| Level | L1 · Needs a person | L2 · Gets in |
| Holds up | Not measured | 60 of 100, fair |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · OpenAPI 3.1.0 (1 version behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (current) · OpenAPI 3.1.0 (1 version behind) · A2A 0.3 (1 version behind) |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Brave Search API | Exa | |
|---|---|---|
| Pay | Tried to pay | Pays per call for part of it |
| Free plan or trial | Trial with a card | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | In a browser | Not needed |
How each one takes payment
- Brave Search API: Tried to pay: the payment failed on the seller's side.
- Exa: Pays per call for part of it: paid $0.001 a call (x402), 15 Oct.
Brave Search API vs Exa: the short answers.
Which can an AI agent use, Brave Search API or Exa?
Exa gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Brave Search API our agent was stopped at key (blocked); with Exa it got in on its own and did 20% of the work. Driven 14 Oct 2026 (Brave Search API) and 15 Oct 2026 (Exa).
Can an AI agent sign up for Brave Search API and Exa on its own?
Brave Search API: yes, in a browser, but a later step stopped it. Exa: not needed.
Do Brave Search API and Exa have an MCP server?
Brave Search API: yes (official). Exa: yes (official).
Can an AI agent delete its Brave Search API or Exa account?
Brave Search API: yes, in a browser. Exa: not needed.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.