Head to head · Web search · October 2026 research run

Exa API + MCP vs SerpApi

Exa API + MCP scores 68.8 (B) on agent readiness against SerpApi's 65.3 (B), and leads in 6 of 7 scored categories. SerpApi leads on transparency & trust. Both do web search. Exa API + MCP is cheaper for web search, $4 against $25 per 1,000 requests. Exa API + MCP accepts x402. SerpApi doesn't.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Exa API + MCP B

Best for Agents that search in natural language and want short highlights or page text in the same call, and for keyless or wallet-paid use.

Ahead on

  • Reliability, 77 against 65
  • Schema & documentation, 86 against 67
  • Agent ergonomics, 96 against 88
  • Payments & pricing, 98 against 45
  • Maintenance & community, 88 against 82

Also in its favour

  • Cheaper for web search, $4 against $25 per 1,000 requests
  • An agent can pay per call over x402, with no account
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 4.5 against 3.5 out of 5

Watch for

The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits

SerpApi B

Best for An agent that needs what a specific engine shows (Google verticals, Maps, Shopping, Flights, Scholar, YouTube, Amazon) parsed to JSON.

Ahead on

  • Transparency & trust, 84 against 61

Also in its favour

  • No incidents deducted, where Exa API + MCP loses 9 points for them

Watch for

35 incidents on the status page between 4 August and 2 November 2026, including an outage across all APIs on 10 September

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Exa API + MCP +53

Exa API + MCP 98

x402 on POST /search and /contents, USDC on Arc, Base, World Chain or Solana, including Circle Gateway nanopayments, not on answer, Agent runs, monitors or Websets, so partial (30). Per-call prices published without login, $0.004 for lite (and legacy instant) to $0.015 for legacy deep-reasoning per search (20). $10 a month and a $10 onboarding bonus, and the pricing page now states "No payment method required" (20). An agent can pay by x402 with no account, and the hosted MCP works anonymously within rate limits (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 60 is 90 at 30 each, so 90 is 98.

SerpApi 45

No x402, MPP or L402 on the pricing page or llms.txt (0). Monthly plans are public with search counts, but there's no pay-per-search option (10). Free plan of 250 searches a month, no card (20). An account needs a browser signup (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust SerpApi +23

Exa API + MCP 61

The MCP server is MIT and the API is closed with published terms (20). The privacy policy, still dated 29 June 2026 on 21 October, says query data is used to train and fine-tune Exa's models and states no retention period. Zero data retention needs a sales conversation, and the DPA sits in the trust centre (12). Dated deprecations in the changelog, such as the pdf, github and tweet categories on 23 July and the instant, fast and deep-reasoning search types made legacy on 19 October, with no removal dates (12). The MCP server, hosted and on npm, sends usage events to Agnost (api.agnost.ai) with no mention in the README, no opt-out flag, and no named subprocessor list in the privacy policy, unchanged on main on 21 October (0).

SerpApi 84

The API is closed under one terms-and-privacy page, and the MCP server is MIT (18). The legal page and the security page agree that search data is deleted after 31 days, ZeroTrace mode (an enterprise parameter) stores nothing, and a DPA is available on request (26). Deprecations show up as dated release notes, such as eBay's Sold and Completed filters on 28 September 2026, but there's no notice policy, and the terms allow termination without notice (8). Named subprocessors (AWS, Cloudflare, Wasabi, Stripe, Intercom and others) and US hosting with Standard Contractual Clauses (18).

Schema & documentation Exa API + MCP +19

Exa API + MCP 86

OpenAPI at exa.ai/docs/exa-spec.yaml, re-read on 21 October with the new lite type, its accepted parameters and the warnings and notices response fields, and JSON Schema inputs on every MCP tool (25). llms.txt and Markdown docs (10). web_search_exa tells the model how to phrase a query and when to follow up with web_fetch_exa, and deprecated tools name their replacement. The agent_run description on the main branch since 19 October says it isn't for a single lookup or a known URL and names the sibling tools, but that commit isn't in npm 3.4.2 and we couldn't confirm the hosted server runs it, so the line stays where it was. Nothing else says when not to use a tool (15). Inputs coerce loosely. numResults is described as 1 to 100 but the schema has no bounds, and bad numbers fall back to defaults silently. On the API, lite rejects an unsupported parameter with a 400 that names it, and ignored fields such as startCrawlDate now come back as IGNORED_FIELD warnings (10). An error-codes page and examples on every endpoint page (13). Dated changelog with deprecations, the latest entry 19 October. The MCP repository has no tags, so versions show only in package.json and the registry (13).

SerpApi 67

No OpenAPI or similar spec for the REST API. The MCP server publishes per-engine parameter lists as resources (serpapi://engines/<engine>), which we count as a partial contract (10). llms.txt, pricing.md and Markdown twins of the docs pages, such as search-api.md (10). Each engine page describes every parameter, and the MCP tool says when to use it but not when not to (14). Parameters list allowed values on the engine pages, but the MCP search tool takes one free-form params object (7). Examples on every engine page, and a status-and-errors page documents 400, 401, 403, 404, 410, 429 and 5xx with a JSON error field (14). Dated release notes with several entries a week, though the API itself isn't versioned (12).

Reliability Exa API + MCP +12

Exa API + MCP 77

Instatus page at status.exa.ai with Search API, Exa MCP, Agents API and Websets components and dated history (20). In the 90 days to 1 November, history/1 shows the Search API's 1-minute blip (16 September), a 1 hour 24 minute latency incident (18 September) and 2 hours 21 minutes of elevated latency with some failed requests (21 September), and the Agents API's 25 minutes of runs failing to start (18 September, labelled major) and 4 hours 56 minutes in which 'some agent runs may fail to start or complete' (21 to 22 September). August is per the 21 October check, not re-read on 1 November (history/2 answers 404 again), with a 10-minute Search API major outage on 14 August and a 53-minute latency incident. No notices in October or November. By this run's reading each hit one product or a subset of requests and none was an hour of a core API down, so all are minor (20, up from 10, where the 21 to 22 September Agents API incident had been counted as a major). Rate limits published per endpoint, 10 QPS search and answer, 5 QPS deep, 100 QPS contents, 5 QPS and 50 active Agent runs (15). 429 with Retry-After when available and exponential backoff advice. We found no idempotency guidance for creating Agent runs, which cost money (12). No SLA found. The pricing page lists "Enterprise SLAs" on the contract plan, with no terms published (0). Search, contents and the MCP are GA, and Dynamic Highlights is still a research preview behind a beta header and isn't the core surface (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

SerpApi 65

Atlassian Statuspage at status.serpapi.com, with per-API components and incident history on its history pages and Atom feed (20). Between 4 August and 2 November the history lists 35 incidents active in the window. Two were wide failures that also list the general API component, each over an hour. From 7 to 9 August an outage across 37 Google and Google Light APIs, including Search, left 'a large number of requests' failing or timing out. On 10 September the vendor posted a 'service outage across all of our APIs', with degradation until 17 September. From 6 October a degradation of 15 Google and Google Light APIs, including Search, which the vendor called a 'partial service outage affecting multiple APIs', was still open on 2 November. Like the single-engine incidents, it hit part of the product and counts as minor. Two majors (5). Hourly throughput published per plan, 50 an hour free to 640,000 on Cloud 54M (15). 429 is documented as either the hourly limit or an empty search balance, with no Retry-After or backoff guidance found (5). The terms (updated 27 August 2026) promise a 99.95% SLA on all plans with credits up to 100% (10). GA (10). 20 + 5 + 15 + 5 + 10 + 10 = 65.

Agent ergonomics Exa API + MCP +8

Exa API + MCP 96

On a keyless connection two tools are on by default, web_search_exa and web_fetch_exa, about 1,250 characters of descriptions between them. Since the 19 October commit on main, agent_run (about 500 characters plus a larger input schema) is also on by default when the user supplies a key, though the README still lists it as optional. ?tools= turns on web_search_advanced_exa and picks the set (25). numResults, maxCharacters, highlights instead of full text, category, domain and date filters, and in web_search_advanced_exa the lite type (20). The error-codes page lists codes, and the MCP server rewrites a 429 into a message about the free tier and keys and now passes search notices to the model. Errors reach the model as text rather than a code (16). Every tool sets readOnlyHint, destructiveHint: false and idempotentHint (false on agent_run), and the server retries transient errors twice (20). Only query is required. Python and TypeScript SDKs (15).

SerpApi 88

json_restrictor selects fields, output=md returns Markdown (the MCP README claims 50 per cent fewer tokens on average) and the MCP compact mode drops metadata. One core MCP tool plus two opt-in UI tools (22). start, num, location, language and engine-specific filters, plus async with the Search Archive API (20). Documented status codes and search_metadata.status values, though one 429 covers both the hourly limit and an empty balance (14). Searches are read-only, failed and cached searches aren't billed, and the MCP tool sets readOnlyHint true and destructiveHint false (18). Only q is required for most engines. llms.txt lists libraries in 11 languages, though the JavaScript one hasn't had a release since July 2025 (14).

Maintenance & community Exa API + MCP +6

Exa API + MCP 88

exa-py and exa-js 2.27.0 tagged on 30 October 2026, after 2.26.0 and the API changelog entry of 19 October (30). 14 tags of each SDK from v2.17.0 (7 August) to v2.27.0 (30 October), and changelog entries on 28 August, 24 September and 19 October (20). 13 open MCP issues and pull requests merged on 2, 6, 7 and 19 October per the 21 October check, with pull requests merged on 27 and 28 October in the clone; reply times unread because GitHub's pages refuse us (15). Official registry entry ai.exa/exa under Exa's own domain, latest 3.4.1 (published 23 September), and current Python and TypeScript SDKs (15). CI typechecks and tests the MCP server on every push. The npm package (3.4.2, 6 October, per the 21 October check) ships from a workflow without git tags, and package.json on main is still 3.4.2 on 1 November (8).

SerpApi 82

Release notes carry dated entries almost daily, the latest on 2 November 2026, and serpapi-python 1.2.0 shipped on 30 October (30). Since 4 August, serpapi-python 1.1.0, 1.1.1, 1.1.2 and 1.2.0, MCP server 1.0.3 and 2.0.0, and serpapi-cli 0.3.0, 0.4.0 and 0.5.0, besides the release notes (20). Release notes run several entries a week and the MCP repo merged a fix on 27 October. Open issues weren't read, since GitHub's pages refuse our reader (12). The MCP server is in the official registry as io.github.serpapi/serpapi-mcp and the Python SDK and CLI are current, but the JavaScript SDK's last release is still 2.2.1 of 26 July 2025 (12). The MCP, Python and CLI repositories run tests in CI; pass state not read (8).

Score by category

CategoryWeightExa API + MCPSerpApiEdge
Reliability16%7765Exa API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8667Exa API + MCP +19
Agent ergonomics13%9688Exa API + MCP +8
Security & auth14%4340Exa API + MCP +3
Payments & pricing10%9845Exa API + MCP +53
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8882Exa API + MCP +6
Transparency & trust7%6184SerpApi +23
Negative events≤15-90
TotalB 68.8/100B 65.3/100

Facts side by side

FactExa API + MCPSerpApi
KindMCP serverHTTP API
VendorExaSerpApi
Hosted endpointhttps://mcp.exa.ai/mcphttps://serpapi.com/search
Transportsstdio, Streamable HTTP, HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for web search$4 per 1,000 requests$25 per 1,000 requests
x402yes, from $0.007/callno
LicenceMITnone
Tools exposed43
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryai.exa/exaio.github.serpapi/serpapi-mcp
Last release2026-10-302026-10-30
Terms last updatednot read yet2026-08-27
Privacy policy last updated2026-06-292026-08-27
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity4.9k stars, 1.1M npm/wk, 1.4M PyPI/wk175 stars, 169k npm/wk, 104k PyPI/wk
Agent reviews4.5/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Exa API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Exa API + MCP

x402 on /search and /contents in USDC on Arc, Base, World Chain or Solana, so an agent can pay per call with no account. The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits, and the server still sends usage events to that service without saying so.

SerpApi

Over 100 engines behind one GET URL, with json_restrictor field selection and output=md. The status page posted an outage across all APIs on 10 September and a degradation of the main Google APIs from 6 October that was still open on 2 November.

Before you call either

Exa API + MCP

  1. Send the key as x-api-key or a Bearer header, never ?exaApiKey= in the MCP URL
  2. Ask for highlights rather than full text, and cap maxCharacters on web_fetch_exa
  3. Request only the results you'll read. More than 10 costs extra, and x402 calls stop at 10
  4. On 429, honour Retry-After. The QPS limit is shared by every key on the team
  5. Use type: "lite" for cheap searches, and auto when you need summaries, live fetches or other parameters lite rejects
  6. Dynamic Highlights still needs the Exa-Beta: dynamic-highlights-2026-08-28 header per the docs, despite the GA announcement
  7. Set budget.maxCostDollars on agent_run, which a keyed MCP connection may now expose by default

SerpApi

  1. Use the MCP with Authorization: Bearer, not the key-in-path URL the README leads with
  2. Read serpapi://engines/<engine> before calling a new engine, since params isn't typed
  3. Add json_restrictor or output=md to cut tokens, and mode: compact on the MCP
  4. A 429 means either the hourly limit or an empty balance. Check the account before retrying
  5. Repeat a search within the hour and the cached copy is free. Set no_cache=true only when freshness matters

Questions

Which is better for AI agents, Exa API + MCP or SerpApi?

Exa API + MCP scores 68.8 (B) on agent readiness against SerpApi's 65.3 (B), and leads in 6 of 7 scored categories. SerpApi leads on transparency & trust.

Which is cheaper for web search, Exa API + MCP or SerpApi?

Exa API + MCP, at $4 per 1,000 requests against $25 per 1,000 requests for SerpApi. These are the vendors' published prices for the job.

Do Exa API + MCP and SerpApi need an API key?

Exa API + MCP takes an API key or an OAuth sign-in. SerpApi needs an API key. An agent can also pay Exa API + MCP per call over x402, with no account.

Can an agent call Exa API + MCP and SerpApi without installing anything?

Yes. Exa API + MCP has a hosted endpoint at https://mcp.exa.ai/mcp and SerpApi at https://serpapi.com/search.

Are Exa API + MCP and SerpApi open source?

Exa API + MCP is open source (MIT). No open-source release is listed for SerpApi.

Other comparisons with Exa API + MCP or SerpApi

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.