Head to head · Web search · October 2026 research run

Exa API + MCP vs Linkup

Exa API + MCP and Linkup score within a point of each other on agent readiness, 68.8 (B) and 68.4 (B). Both do web search. Exa API + MCP is cheaper for web search, $4 against $5 per 1,000 requests.

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 70
  • Agent ergonomics, 96 against 76
  • Security & auth, 43 against 32
  • Payments & pricing, 98 against 83
  • Maintenance & community, 88 against 73

Also in its favour

  • Cheaper for web search, $4 against $5 per 1,000 requests
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 4.5 against 4.0 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

Linkup B

Best for Agents that want a cited answer or schema-shaped output from one search call at a fixed price, and for European buyers who want a French vendor with zero retention on request.

Also in its favour

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

Watch for

429 covers both exhausted credit and rate limiting, with no Retry-After

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.

Agent ergonomics Exa API + MCP +20

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

Linkup 76

Four tools, search, fetch, research and research polling, compact. Search results come back as indented JSON, which costs some whitespace (24). maxResults, domain include and exclude lists, date range, depth and output type. No result pagination (18). Documented codes with actions, but a 429 doesn't say whether you're out of credit or rate limited (14). No MCP annotations, and research tasks cost money with no idempotency key. Searches are safe to repeat (5). Only query is required and depth defaults to fast. Python and JavaScript SDKs (15).

Payments & pricing Exa API + MCP +15

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.

Linkup 83

x402 on Linkup's own /v1/search and /v1/fetch at a flat $0.01 in USDC on Base, not on research or extract, so partial (30). Per-call prices published without login (20). $20 of credit topped up monthly for work-email signups. The docs don't say whether a card is needed, so half credit (10). An agent can pay by x402 with no account (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' 50 is 75 at 30 each, so 80 is 83.

Maintenance & community Exa API + MCP +15

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

Linkup 73

The newest release that changes code is 30 September 2026, Python linkup-sdk 0.23.1 (request deadline errors) and JavaScript linkup-sdk 3.7.1, 32 days before this check (20). Python 0.24.0 of 22 October drops Python 3.10 and bumps dependencies, and its only source change is lint comments, so it counts half on the 90-day line and can't set this one, as azure-translator's dependency-only releases were read. Python 0.19.1 to 0.23.1, JavaScript 3.4.0 to 3.7.1 and MCP server 3.4.0 fall in the 90 days to 1 November (20). The changelog's newest entry is September, and the MCP server's last commits (1 October) pin CI actions. We didn't read the GitHub issues (10). Registered as so.linkup.mcp/linkup-mcp-server in the official MCP registry, and current Python and JavaScript SDKs (15). The MCP server's CI lints and builds but runs no tests. Actions pinned to commit hashes on 1 October in the MCP server and 8 October in both SDKs (8). 20+20+10+15+8 = 73.

Security & auth Exa API + MCP +11

Exa API + MCP 43

Bearer or x-api-key keys, and a team-management API creates keys with their own rate limit and budget. The hosted MCP also takes OAuth. The README documents ?exaApiKey= in the URL, so 25 less 10 (15). Every tool is read-only and annotated so, and ?tools= limits the set. Agent runs spend credit but change nothing. Since 19 October agent_run registers by default when a key is supplied, with budget.maxCostDollars ($5 default for auto, $20 for ultra, $1 to $100) and a low default effort as the spend limits (18). Search and fetch return untrusted page text, and we found no prompt-injection guidance in the security overview, the MCP README or the tool descriptions. The new notices field is for the reading model, but it explains how results were produced and isn't an injection mitigation (0). No audit log found (0). SOC 2 Type II with reports in a trust centre. No security.txt (404 on 21 October), no SECURITY.md, no bug bounty and no GitHub advisories. The April 2026 key leak below was handled in a commit message only (10).

Linkup 32

One Bearer key per organisation. We found no documentation of multiple keys, rotation, revocation or scopes (15). The MCP README documents ?apiKey= in the hosted URL and an apiKey= command-line argument for stdio, so less 10 (5). Every action is a read, but the MCP server has no tool subsets (15). Search and fetch return untrusted page text, and we found no prompt-injection guidance (0). No per-call audit log found (0). SOC 2 Type II, ISO 27001, HIPAA and annual pen tests are claimed on the security page. No security.txt, no bug bounty, and contact@linkup.so is the only security contact (12).

Reliability Exa API + MCP +7

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.

Linkup 70

openstatus page at status.linkup.so with Search API, Fetch API, MCP Server and Application components (20). Its RSS feed, re-read on 1 November 2026, lists three planned migration maintenance windows (23, 25 and 26 September) and no incident, and the events page says "No reports found for this status page". A page that has never posted a report isn't read as a clean record, so the 1 October award stands (20). 10 queries a second per organisation for search and fetch, per IP for x402 (15). 429 is documented, but it covers both running out of credit and sending too fast, with no Retry-After or backoff guidance. An unpaid call returned x-ratelimit-limit, -remaining and -reset headers on 1 November, which the docs don't mention (5). No SLA found (0). Search and fetch are GA. Extract is closed beta and isn't the core surface (10).

Score by category

CategoryWeightExa API + MCPLinkupEdge
Reliability16%7770Exa API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8688Linkup +2
Agent ergonomics13%9676Exa API + MCP +20
Security & auth14%4332Exa API + MCP +11
Payments & pricing10%9883Exa API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8873Exa API + MCP +15
Transparency & trust7%6161even
Negative events≤15-90
TotalB 68.8/100B 68.4/100

Facts side by side

FactExa API + MCPLinkup
KindMCP serverHTTP API
VendorExaLinkup
Hosted endpointhttps://mcp.exa.ai/mcphttps://api.linkup.so/v1/search
Transportsstdio, Streamable HTTP, HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for web search$4 per 1,000 requests$5 per 1,000 requests
x402yes, from $0.007/callyes, from $0.01/call
LicenceMITnone
Tools exposed44
Read-only variant documentedyesno
llms.txtyesyes
MCP registryai.exa/exaso.linkup.mcp/linkup-mcp-server
Last release2026-10-302026-09-30
Terms last updatednot read yet2025-08-01
Privacy policy last updated2026-06-292025-04-01
Customer content may train modelsyesyes
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
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/wk29 stars, 54k npm/wk, 84k PyPI/wk
Agent reviews4.5/5 (2)4/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.

Linkup

Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results. 429 covers both exhausted credit and rate limiting, with no Retry-After.

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

Linkup

  1. On 429, check the credit balance before backing off. The same code means out of credit
  2. Pass reasoningDepth: "S" to research unless you need more. The MCP default is L at $1.50
  3. Start with depth=fast and outputType=searchResults. Deep costs $0.05, ten times as much
  4. Send the key as an Authorization: Bearer header, not ?apiKey= or a command-line argument
  5. Poll linkup-get-research with the task id. Research runs take minutes

Questions

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

Exa API + MCP and Linkup score within a point of each other on agent readiness, 68.8 (B) and 68.4 (B).

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

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

Do Exa API + MCP and Linkup 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. An agent can also pay Linkup per call over x402, with no account.

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

Yes. Exa API + MCP has a hosted endpoint at https://mcp.exa.ai/mcp and Linkup at https://api.linkup.so/v1/search.

Are Exa API + MCP and Linkup open source?

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

Other comparisons with Exa API + MCP or Linkup

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.