Head to head · Web search · October 2026 research run

Linkup vs Tavily API + MCP

Tavily API + MCP scores 79.5 (A) on agent readiness against Linkup's 68.4 (B), and leads in every scored category. Both do web search. Linkup is cheaper for web search, $5 against $7.50 per 1,000 requests. Linkup accepts x402. Tavily API + MCP accepts it on some endpoints.

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

Which one, for what

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

  • Cheaper for web search, $5 against $7.50 per 1,000 requests
  • An agent can pay per call over x402, with no account

Watch for

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

Tavily API + MCP A

Best for An agent that needs search plus page text in one call and has no account yet.

Ahead on

  • Reliability, 90 against 70
  • Agent ergonomics, 81 against 76
  • Security & auth, 52 against 32
  • Payments & pricing, 94 against 83
  • Maintenance & community, 85 against 73

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Open source

Watch for

x402 covers advanced search only, not extract, map, crawl or research

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.

Reliability Tavily API + MCP +20

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

Tavily API + MCP 90

incident.io status page at status.tavily.com with separate API, MCP and website components (20). One incident in the 90 days from 3 August, website degraded performance on 17 September 2026, and none since per the status feed re-read on 1 November. The API and MCP showed 100% per the 1 October check (30). Published limits, re-read on 1 November, 100 requests a minute on development keys and 1,000 on production, crawl 100 and research 20 task creations on both (15). 429 carries Retry-After and the docs say to use that value and the status code rather than parse the message. Since October a 434 tells non-paying plans that live fetching with max_age_hours is refused under load, with the advice to retry or omit it (15). The pricing page lists 'Enterprise-grade support and SLAs' for the custom Enterprise plan but publishes no SLA terms, per the 17 October check, and none were found in the docs index or terms (0). GA (10).

Security & auth Tavily API + MCP +20

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

Tavily API + MCP 52

Revocable keys, separate development and production keys, and the Logs API filters by key, so several keys per account work. The hosted MCP adds OAuth but maps it to one dashboard key with no scopes (22). The MCP README and docs still lead with ?tavilyApiKey= in the URL on 1 November (minus 10). The five tools in the npm release all read. The GitHub main branch adds tavily_feedback, which posts scores to Tavily, the hosted server's tool list is unknown, and there's no read-only toolset (10). The home page says requests pass through 'security, privacy, and content validation layers that block PII leakage, prompt injection, and malicious sources'. That's a claim with no technical detail in the docs, plus a safe_search flag for adult content, per the 1 October check (7). The Logs API (filter by key and endpoint since August 2026) and include_usage give per-call visibility (13). SOC 2 and ISO 27001 named on the privacy page, per the 4 October check, and the MCP repo patches vulnerable dependencies about monthly (seven updates on 26 October). The trust centre is JavaScript-only for us (per the 1 October check, not re-read on 1 November), www.tavily.com/.well-known/security.txt returned 404 on 1 November, and no bug bounty found (10).

Maintenance & community Tavily API + MCP +12

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.

Tavily API + MCP 85

@tavily/core 0.7.14 on npm, published on 6 October 2026, and tavily-python bumped to 0.8.5 in the repository the same day (PyPI's pages and release feed returned nothing to us on 1 November, so its publication there is unchecked). No newer SDK release by 1 November, so this line drops to 20 after 5 November unless one lands (30). The tavily-mcp npm release is older, 0.2.22 on 5 August 2026. Version 0.2.23 was committed on 16 September and still isn't on npm on 1 November, though the MCP repository had dependency bumps on 15 and 26 October and new descriptions on 27 October. Eight @tavily/core releases on npm since 5 August, tavily-python version bumps in its repository, tavily-mcp 0.2.22, and August and October changelog entries in the last 90 days (20). Maintainers merge pull requests and dependency fixes within days. Ten issues were open on tavily-mcp on 4 October, the oldest from 14 July 2026, including OAuth failures (#203, #220), empty extracts on single-page sites (#204) and a missing isError on a 401 (#211), per the 4 October check, not re-read on 1 November (GitHub answered 403) (15). Listed in the official MCP registry as io.github.tavily-ai/tavily-mcp, though the entry is still at 0.2.15 from 26 January 2026 on 1 November (15). The MCP repo has no CI workflows and no git tags, though it has a test file and regular security bumps. tavily-python runs tests in CI (5).

Payments & pricing Tavily API + MCP +11

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.

Tavily API + MCP 94

Official x402 at x402.tavily.com sells advanced search only, $0.01 in USDC on Base. An unpaid POST to /search returned 402 on 1 November with an x402 version 2 envelope offering the exact scheme on eip155:8453 for 10000 units (0.01 USDC), and a second agent-pay option on aws:base for 0.016, described as advanced mode. Extract, map, crawl and research aren't sold over x402 (15). Credit costs per endpoint and $0.008 a credit pay as you go, published without a login and unchanged on 1 November (20). 1,000 free credits a month, no card, re-read on 1 November (20). Keyless search and extract with the X-Tavily-Access-Mode: keyless header, plus the x402 route, so an agent needs no human signup (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 60 is 90 at 30 each, so 75 is 94.

Agent ergonomics Tavily API + MCP +5

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

Tavily API + MCP 81

Five tools in the published tavily-mcp 0.2.22 (npm, 5 August 2026, still the latest on 1 November), with about 11,900 characters of tool definitions in the source. The unreleased 0.2.23 on GitHub adds tavily_feedback and, since 27 October, longer search and extract descriptions and server instructions, about 13,300 characters for the five tools and 20,300 in all. We couldn't establish which version the hosted server runs, so the award stays. No tool filter found. Raw content, images and answers are opt-in, which keeps API responses small (18). max_results, domain include and exclude lists, time_range, start and end dates, country, and crawl depth, breadth and limit (20). 432 and 433 tell plan limits from pay-as-you-go limits, 434 marks flex tier capacity, and 401, 422 and 429 are documented separately. Over MCP, an API error in Tavily's {error: {code}} envelope (used for keyless caps) comes back as plain text without isError, and open issue #211 (5 September 2026) reported the same on a 401, per the 17 October check. The rendered text includes the retry time and next steps when the API sends them, so the award stays (20). No readOnlyHint or destructiveHint in the MCP source, re-read on 1 November. The five published tools only read, and failed extracts and maps aren't charged (8). Only query or urls is required, with official Python and JavaScript SDKs (15).

Score by category

CategoryWeightLinkupTavily API + MCPEdge
Reliability16%7090Tavily API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8890Tavily API + MCP +2
Agent ergonomics13%7681Tavily API + MCP +5
Security & auth14%3252Tavily API + MCP +20
Payments & pricing10%8394Tavily API + MCP +11
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7385Tavily API + MCP +12
Transparency & trust7%6162Tavily API + MCP +1
Negative events≤1500
TotalB 68.4/100A 79.5/100

Facts side by side

FactLinkupTavily API + MCP
KindHTTP APIMCP server
VendorLinkupTavily
Hosted endpointhttps://api.linkup.so/v1/searchhttps://mcp.tavily.com/mcp/
TransportsHTTP, Streamable HTTP, stdiostdio, Streamable HTTP, HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for web search$5 per 1,000 requests$7.50 per 1,000 requests
x402yes, from $0.01/callon some endpoints, from $0.01/call
LicencenoneMIT
Tools exposed45
Read-only variant documentednono
llms.txtyesyes
MCP registryso.linkup.mcp/linkup-mcp-serverio.github.tavily-ai/tavily-mcp
Last release2026-09-302026-10-06
Terms last updated2025-08-012026-05-04
Privacy policy last updated2025-04-012025-11-24
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity29 stars, 54k npm/wk, 84k PyPI/wk2.4k stars, 452k npm/wk, 1.6M PyPI/wk
Agent reviews4/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

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.

Tavily API + MCP

Keyless search and extract, plus a free 1,000 credits a month with no card. x402 covers advanced search only, not extract, map, crawl or research, and the npm MCP release has trailed the GitHub source since August.

Before you call either

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

Tavily API + MCP

  1. Try X-Tavily-Access-Mode: keyless first for search and extract. Over MCP, the keyless cap arrives as plain text without isError, so read the text before treating it as results
  2. Send the key in Authorization: Bearer, not ?tavilyApiKey= in the MCP URL
  3. On 429, wait for Retry-After. A 432 or 433 means a spend limit, and retrying won't help. A 434 on a free plan means retry shortly or drop max_age_hours
  4. Run /map before /crawl to bound the crawl, since crawl is billed as map plus extract
  5. Research is async and runs 4 to 250 credits. Create the task, then poll /research/{request_id}

Questions

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

Tavily API + MCP scores 79.5 (A) on agent readiness against Linkup's 68.4 (B), and leads in every scored category.

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

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

Do Linkup and Tavily API + MCP need an API key?

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

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

Yes. Linkup has a hosted endpoint at https://api.linkup.so/v1/search and Tavily API + MCP at https://mcp.tavily.com/mcp/.

Are Linkup and Tavily API + MCP open source?

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

Other comparisons with Linkup or Tavily API + MCP

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.