Exa vs Parallel for AI agents
As of 15 Oct 2026, Parallel gets an AI agent further: L5 · Autonomous 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, pay per call, sign-up in a browser.
- Use: 80% of the work.
- Pay: Pays on its own: Paid $0.01 a call (x402), 15 Oct.
- Leave: Nothing to cancel: Can't delete its account.
Got in; first wall at delete (blocked). Does it all on its own, payment included
Parallel is an API/tool suite for web search, research, and data-monitoring that AI agents can call. An agent got free search and extraction through a no-account tool, and could pay small per-call fees to search, extract, summarize, and run research tasks without ever creating an account. Signing up for a full account worked without any human checks, but every paid feature on that new account needed a saved credit card, which the test could not provide.
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.
ExaIn on its own; 20% of the work done
ParallelGot in; first wall at delete (blocked)
| Checkpoint | Exa | Parallel |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | In a browser |
| Verify | Not needed | In a browser |
| Key | Not needed | Headless |
| First call | Headless | Headless |
| First action | Not needed | Headless |
| Pay | Headless | Headless |
| Cancel | Not needed | Not needed |
| Delete | Not needed | Blocked |
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 | Parallel | |
|---|---|---|
| Headless (checkpoints) | 3 | 5 |
| In a browser (checkpoints) | 0 | 2 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 0 | 0 |
| Work done | 20% of the core | 80% 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 | Parallel | |
|---|---|---|
| Bot check | A challenge on the form stopped 2 ways in (Email and code, Sign-in for apps); it got in another way | None met |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | None | Got in; first wall at delete (blocked) |
| 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 | Parallel | |
|---|---|---|
| Level | L2 · Gets in | L5 · Autonomous |
| Holds up | 60 of 100, fair | 80 of 100, fair |
| 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 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) |
| Security | No review in this drive | Reported privately to the owner |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Exa | Parallel | |
|---|---|---|
| Pay | Pays per call for part of it | Pays on its own |
| Free plan or trial | Free plan | Trial with a card |
| Cancel | Not needed | Not needed |
| Delete the account | Not needed | Blocked |
How each one takes payment
- Exa: Pays per call for part of it: paid $0.001 a call (x402), 15 Oct.
- Parallel: Pays on its own: paid $0.01 a call (x402), 15 Oct.
Exa vs Parallel: the short answers.
Which can an AI agent use, Exa or Parallel?
Parallel gets an AI agent further: L5 · Autonomous against L2 · Gets in. With Exa our agent got in on its own and did 20% of the work; with Parallel it got in and met its first wall at delete (blocked). Both driven 15 Oct 2026.
Can an AI agent sign up for Exa and Parallel on its own?
Exa: not needed. Parallel: yes, in a browser.
Do Exa and Parallel have an MCP server?
Exa: yes (official). Parallel: yes (official).
Can an AI agent delete its Exa or Parallel account?
Exa: not needed. Parallel: blocked.
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.