Exa vs SerpApi 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: 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 evidence- Find: Some docs for agents: llms.txt and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person: a person has to sign up and get the key before an agent can search on its own. Our agent stopped first at signup: after the web form, a reCAPTCHA picture puzzle asking to select squares with bicycles appeared, and there is no documented API or CLI sign-up. SerpApi's docs are agent-friendly, with llms.txt and Markdown pages, and the MCP server works keyless for locations lookup and engine schemas. Without a key, /account.json returned "Invalid API key," and robots.txt also blocks the documented search endpoint, so no search ran. Paying, cancelling and deleting the account were never reached: no key, no plan, no account.
Driven 12 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
ExaIn on its own; 20% of the work done
SerpApiStopped at sign up: needs a human
| Checkpoint | Exa | SerpApi |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Needs a human |
| Verify | Not needed | Not reached |
| Key | Not needed | Not reached |
| First call | Headless | Not reached |
| First action | Not needed | Not reached |
| Pay | Headless | Not reached |
| Cancel | Not needed | Not reached |
| Delete | Not needed | Not reached |
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 | SerpApi | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 20% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | – | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Exa | SerpApi | |
|---|---|---|
| Bot check | A challenge on the form stopped 2 ways in (Email and code, Sign-in for apps); it got in another way | Google reCAPTCHA v2 stopped it at sign up, with a visible challenge |
| Wall type | A challenge on the form | A challenge on the form |
| First wall | None | reCAPTCHA picture puzzle on sign-up |
| 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 | SerpApi | |
|---|---|---|
| Level | L2 · Gets in | L1 · Needs a person |
| Holds up | 60 of 100, fair | Not measured |
| Agent-ready setup | 100 of 100, good | 75 of 100, fair |
| 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) |
| 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 | SerpApi | |
|---|---|---|
| Pay | Pays per call for part of it | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | Not needed | Not reached |
How each one takes payment
- Exa: Pays per call for part of it: paid $0.001 a call (x402), 15 Oct.
- SerpApi: Payment not reached.
Exa vs SerpApi: the short answers.
Which can an AI agent use, Exa or SerpApi?
Exa gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Exa our agent got in on its own and did 20% of the work; with SerpApi it was stopped at sign up (needs a human). Driven 15 Oct 2026 (Exa) and 12 Oct 2026 (SerpApi).
Can an AI agent sign up for Exa and SerpApi on its own?
Exa: not needed. SerpApi: no, needs a human.
Do Exa and SerpApi have an MCP server?
Exa: yes (official). SerpApi: yes (official).
Can an AI agent delete its Exa or SerpApi account?
Exa: not needed. SerpApi: not reached.
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.