Head to head · Web search · October 2026 research run

Exa API + MCP vs Parallel Search and Task APIs

Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Exa API + MCP's 68.8 (B), and leads in 3 of 7 scored categories. Exa API + MCP leads on agent ergonomics and payments & pricing. Both do web search. Parallel Search and Task APIs is cheaper for web search, $1 against $4 per 1,000 requests. Exa API + MCP accepts x402. Parallel Search and Task APIs accepts it on some endpoints.

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

  • Agent ergonomics, 96 against 87
  • Payments & pricing, 98 against 81

Also in its favour

  • An agent can pay per call over x402, with no account
  • Runs on your own machine
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 4.5 against 3.6 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

Parallel Search and Task APIs BB

Best for Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.

Ahead on

  • Schema & documentation, 94 against 86

Also in its favour

  • Cheaper for web search, $1 against $4 per 1,000 requests
  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Exa API + MCP loses 9 points for them

Watch for

Search defaults to advanced mode at $5 per 1,000 when mode is left out

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 +17

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.

Parallel Search and Task APIs 81

Parallel runs a separate gateway at parallelmpp.dev that takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. Our unpaid POST to /api/search on 6 October returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 and a Tempo MPP challenge. Nothing on api.parallel.ai, and the gateway sells one price per endpoint with no mode choice, so partial (25). Per-unit prices published without login (20). Up to 5,000 free requests a month, $5 monthly credit and up to $80 at signup on the pricing page, which still doesn't say whether a card is needed (10). The hosted Search MCP works with no key, and the gateway needs only a wallet (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 25 of 40 is 6.25 of 10, and the other lines' 50 is 75 at 30 each, so 75 is 81.

Agent ergonomics Exa API + MCP +9

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).

Parallel Search and Task APIs 87

The Search MCP has two tools, about 5,700 characters of names, descriptions and input schemas on 1 November, and the Parallel MCP server lists three without a key (about 9,700 characters) and a fourth, web_research, after sign-in. web_fetch returns excerpts unless full_content is set, and the docs cap excerpts at roughly 25,000 characters a call and warn full pages can run to tens of thousands of tokens (25). Result counts, excerpt settings and source policies for domains and paths (18). The errors table gives each code a retry column and a resolution, with troubleshooting for 402 and 429 and a structured detail on 422 (20). Both Search MCP tools carry readOnlyHint true, destructiveHint false and idempotentHint true in the live tools/list, and searches are safe to repeat. There's still no idempotency key for Task creation, the SDKs retry creates on 429 and 5xx, and the Task MCP needs a key, so its annotations weren't read (14). Python and TypeScript SDKs, but mode defaults to advanced, the $5 per 1,000 tier, when you leave it out (10).

Schema & documentation Parallel Search and Task APIs +8

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).

Parallel Search and Task APIs 94

Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live tools/list on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds web_decisions, whose description says when to use web_search instead. web_search states its purpose and ideal uses, and web_fetch says to use it "only when web_search excerpts are insufficient". The docs add that domain filters are hard filters that can cut quality. web_search has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, mode is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured detail (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).

Score by category

CategoryWeightExa API + MCPParallel Search and Task APIsEdge
Reliability16%7775Exa API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8694Parallel Search and Task APIs +8
Agent ergonomics13%9687Exa API + MCP +9
Security & auth14%4345Parallel Search and Task APIs +2
Payments & pricing10%9881Exa API + MCP +17
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8887Exa API + MCP +1
Transparency & trust7%6165Parallel Search and Task APIs +4
Negative events≤15-90
TotalB 68.8/100BB 75.7/100

Facts side by side

FactExa API + MCPParallel Search and Task APIs
KindMCP serverHTTP API
VendorExaParallel Web Systems
Hosted endpointhttps://mcp.exa.ai/mcphttps://api.parallel.ai/v1/search
Transportsstdio, Streamable HTTP, HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for web search$4 per 1,000 requests$1 per 1,000 requests
x402yes, from $0.007/callon some endpoints, from $0.01/call
LicenceMITnone
Tools exposed46
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryai.exa/exaai.parallel/search-mcp
Last release2026-10-302026-10-28
Terms last updatednot read yet2026-10-17
Privacy policy last updated2026-06-292026-08-11
Customer content may train modelsyesyes
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 yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity4.9k stars, 1.1M npm/wk, 1.4M PyPI/wk28 stars, 250k npm/wk, 994k PyPI/wk
Agent reviews4.5/5 (2)3.6/5 (8)

The panel on both

The 2 reviewers who reviewed both split evenly.

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.

Parallel Search and Task APIs

Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when mode is left out, and the Customer Terms allow training on inputs and outputs.

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

Parallel Search and Task APIs

  1. Pass mode: "fast" on every API search. Without it you pay the advanced rate. On an authenticated MCP connection, pin it with ?mode=fast
  2. Create Task runs with max_retries=0 and check for an existing run before retrying
  3. Give an objective plus two or three short search_queries. That's what ranks the excerpts
  4. On 402, check available balance rather than total. Running tasks reserve credit
  5. Ask for zero data retention or use the EU endpoint before sending private queries. The default terms allow training on them
  6. On Decisions, check each answer's type before reading it. A refusal is a 200, not an error, and a predicate is a probability you threshold yourself

Questions

Which is better for AI agents, Exa API + MCP or Parallel Search and Task APIs?

Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Exa API + MCP's 68.8 (B), and leads in 3 of 7 scored categories. Exa API + MCP leads on agent ergonomics and payments & pricing.

Which is cheaper for web search, Exa API + MCP or Parallel Search and Task APIs?

Parallel Search and Task APIs, at $1 per 1,000 requests against $4 per 1,000 requests for Exa API + MCP. These are the vendors' published prices for the job.

Do Exa API + MCP and Parallel Search and Task APIs need an API key?

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

Can an agent call Exa API + MCP and Parallel Search and Task APIs without installing anything?

Yes. Exa API + MCP has a hosted endpoint at https://mcp.exa.ai/mcp and Parallel Search and Task APIs at https://api.parallel.ai/v1/search.

Are Exa API + MCP and Parallel Search and Task APIs open source?

Exa API + MCP is open source (MIT). No open-source release is listed for Parallel Search and Task APIs.

Other comparisons with Exa API + MCP or Parallel Search and Task APIs

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.