Exa vs Tavily for AI agents
As of 16 Oct 2026, Tavily gets an AI agent further: L3 · Does the work against L2 · Gets in.
- 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.
Driven 15 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: Can't sign up for one.
- Use: 50% of the work.
- Pay: Tried to pay: The payment failed on the seller's side.
- Leave: Leaves on its own: Nothing to cancel, made nothing to delete.
In on its own; 50% of the work done. Next: let an agent sign up for an account on its own (without one it does 50% of the core work)
Tavily is easy for an agent to start with: keyless Search and Extract work on REST, a modern 28 Jul 2026 MCP server and the CLI with no account, and covered 4 of 8 core tasks. Getting further fails: email sign-up shows a Cloudflare Turnstile checkbox and GitHub/OAuth sign-in is refused by Auth0 as a 'Suspicious User Agent', so Crawl, Map and Research (free with a key) were out of reach. The first-party x402 rail sells only search, and our signed payments came back settlement_failed.
Gets furtherDriven 16 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.
ExaIn on its own; 20% of the work done
TavilyIn on its own; 50% of the work done
| Checkpoint | Exa | Tavily |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Not needed |
| Verify | Not needed | Not needed |
| Key | Not needed | Not needed |
| First call | Headless | Headless |
| First action | Not needed | Headless |
| Pay | Headless | Tried, not settled |
| Cancel | Not needed | Not needed |
| Delete | Not needed | 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
| Exa | Tavily | |
|---|---|---|
| Headless (checkpoints) | 3 | 3 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 0 | 0 |
| Work done | 20% of the core | 50% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | – | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Exa | Tavily | |
|---|---|---|
| Bot check | A challenge on the form stopped 2 ways in (Email and code, Sign-in for apps); it got in another way | A challenge on the form stopped one way in (Email and password); it got in another way |
| Wall type | A challenge on the form | A challenge on the form |
| First wall | None | 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.
| Exa | Tavily | |
|---|---|---|
| Level | L2 · Gets in | L3 · Does the work |
| Holds up | 60 of 100, fair | 90 of 100, good |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | 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) | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (current) · OpenAPI 3.0.3 (2 versions behind) · A2A 1.0 (current) |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Exa | Tavily | |
|---|---|---|
| Pay | Pays per call for part of it | Tried to pay |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | Not needed | Not needed |
How each one takes payment
- Exa: Pays per call for part of it: paid $0.001 a call (x402), 15 Oct.
- Tavily: Tried to pay: the payment failed on the seller's side.
Exa vs Tavily: the short answers.
Which can an AI agent use, Exa or Tavily?
Tavily gets an AI agent further: L3 · Does the work against L2 · Gets in. With Exa our agent got in on its own and did 20% of the work; with Tavily it got in on its own and did 50% of the work. Driven 15 Oct 2026 (Exa) and 16 Oct 2026 (Tavily).
Can an AI agent sign up for Exa and Tavily on its own?
Exa: not needed. Tavily: not needed.
Do Exa and Tavily have an MCP server?
Exa: yes (official). Tavily: yes (official).
Can an AI agent delete its Exa or Tavily account?
Exa: not needed. Tavily: 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.