Head to head · Web search · October 2026 research run

Linkup vs SearchAPI.io

Linkup scores 68.4 (B) on agent readiness against SearchAPI.io's 52 (D), and leads in 5 of 7 scored categories. SearchAPI.io leads on reliability. Both do web search. SearchAPI.io is cheaper for web search, $4 against $5 per 1,000 requests. Linkup accepts x402. SearchAPI.io doesn't.

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.

Ahead on

  • Schema & documentation, 88 against 59
  • Agent ergonomics, 76 against 52
  • Payments & pricing, 83 against 45
  • Maintenance & community, 73 against 0

Also in its favour

  • An agent can pay per call over x402, with no account
  • Runs on your own machine
  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

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

SearchAPI.io D

Best for Agents that need parsed results from many engines, especially shopping, ads, travel and social sources, at a low price per search.

Ahead on

  • Reliability, 90 against 70

Also in its favour

  • Cheaper for web search, $4 against $5 per 1,000 requests
  • Free to start without a card

Watch for

MCP loads one tool per engine with no toolsets

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.

Maintenance & community Linkup +73

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.

SearchAPI.io 0

No changelog (/changelog answered 404 on 4 November 2026) and no dated API change found, so the last release can't be dated (0). No releases to count (0). No public issue tracker or changelog to judge replies by. A Discord server is linked from the footer and wasn't tested (0). The 15 for io.searchapi/mcp in the official MCP registry rested on a reading of the registry's JSON API, which this run doesn't use, and no ordinary registry page shows the entry, so the line falls to 0, as graphiti, linear-mcp and copilot-studio-mcp read it. No official SDKs were found; the footer links a GitHub organisation whose pages answered 403 (0, 15 before). No public packages or CI (0). 0 + 0 + 0 + 0 + 0 = 0.

Payments & pricing Linkup +38

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.

SearchAPI.io 45

No x402, MPP or L402 (0). Monthly plans only, priced in public, from $40 for 10,000 searches to $5,000 for 5 million (10). 100 free requests with no card (20). A person has to sign up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Schema & documentation Linkup +29

Linkup 88

OpenAPI at api.linkup.so/v1/openapi.json per the 30 September check, and typed JSON Schema on all four MCP tools (25). llms.txt and Markdown pages (10). The research tool says it's async, how to poll, and to prefer linkup-search for quick answers. The search tool lists what to use it for but not when not to (17). Enums for depth, mode and reasoningDepth, ISO dates, positive integers for maxResults (14). An errors page lists every status with a recommended action, plus SDK error types (14). The changelog is dated by month, with four entries since June (Extract in June, Fetch Pro mode and Fetch structured output in August, Linkup Flash in September) and none since. Versioning is the /v1 path only (8).

SearchAPI.io 59

OpenAPI 3.0 for the Google engine at /openapi/google.yaml with 25 typed parameters. We found no index of specs for the other engines, so 20 of 25. No llms.txt (404 on 4 November 2026) and no Markdown docs for agents (0). The API reference explains each parameter, and the MCP tool definitions aren't public (10). Enums for device, country, language, safe search and time period (14). Examples and a Postman collection, and the spec documents 400, 401, 403, 429 and 500 (12). /api/v1 in the path and no changelog anywhere we looked (3).

Agent ergonomics Linkup +24

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

SearchAPI.io 52

The MCP exposes over 100 tools, one or more per engine, with no toolsets or filtering documented (5). page, time_period, location, country, language and safe search. Google's num has been fixed at 10 since September 2025 (18). Status codes are documented, but not how to recover from each (12). Searches are reads, and only HTTP 200 responses are billed, so retries are cheap. MCP annotations aren't visible (10). Two required parameters, engine and q. No official SDKs (7).

Reliability SearchAPI.io +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).

SearchAPI.io 90

Honeybadger status page at status.searchapi.io with Landing Page and API components and monthly history (20). Re-read on 4 November 2026, it shows no incidents in September, October or November 2026, and its incident feed's newest entry is the 11 February 2026 partial outage, so the window from 6 August is clean (30). The hourly cap is published, 20 per cent of the plan's monthly searches in any hour (15). The OpenAPI file lists a 429 response with an error string, but no Retry-After or backoff guidance was found. The partial 5 is kept pending the founder's rule on in-between values (5). The terms of 11 April 2026 give a 99.9% SLA for all plans with a credit of 100% of the monthly price, and the pricing page lists it on every plan (10). GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.

Score by category

CategoryWeightLinkupSearchAPI.ioEdge
Reliability16%7090SearchAPI.io +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8859Linkup +29
Agent ergonomics13%7652Linkup +24
Security & auth14%3228Linkup +4
Payments & pricing10%8345Linkup +38
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%730Linkup +73
Transparency & trust7%6162SearchAPI.io +1
Negative events≤1500
TotalB 68.4/100D 52/100

Facts side by side

FactLinkupSearchAPI.io
KindHTTP APIHTTP API
VendorLinkupSearchApi
Hosted endpointhttps://api.linkup.so/v1/searchhttps://www.searchapi.io/api/v1/search
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for web search$5 per 1,000 requests$4 per 1,000 requests
x402yes, from $0.01/callno
Tools exposed4none
Read-only variant documentednono
llms.txtyesno
MCP registryso.linkup.mcp/linkup-mcp-serverio.searchapi/mcp
Last release2026-09-30none
Terms last updated2025-08-012026-04-11
Privacy policy last updated2025-04-012026-04-11
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity29 stars, 54k npm/wk, 84k PyPI/wknone
Agent reviews4/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Linkup 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

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.

SearchAPI.io

A 99.9% SLA in the terms on every plan, no status-page incidents since 11 February 2026, and over 150 engine endpoints behind one URL. The MCP loads one tool per engine with no toolsets, there is no changelog or official SDK, and every account starts with a browser signup.

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

SearchAPI.io

  1. Send the key as Authorization: Bearer, not api_key= in the URL
  2. Connect the MCP through OAuth or the X-MCP-Token header. Never put the token in the MCP URL
  3. Call the REST API with engine= when context is tight. The MCP loads one tool definition per engine
  4. Page Google results with page. num is fixed at 10
  5. Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches

Questions

Which is better for AI agents, Linkup or SearchAPI.io?

Linkup scores 68.4 (B) on agent readiness against SearchAPI.io's 52 (D), and leads in 5 of 7 scored categories. SearchAPI.io leads on reliability.

Which is cheaper for web search, Linkup or SearchAPI.io?

SearchAPI.io, at $4 per 1,000 requests against $5 per 1,000 requests for Linkup. These are the vendors' published prices for the job.

Do Linkup and SearchAPI.io 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 SearchAPI.io without installing anything?

Yes. Linkup has a hosted endpoint at https://api.linkup.so/v1/search and SearchAPI.io at https://www.searchapi.io/api/v1/search.

Other comparisons with Linkup or SearchAPI.io

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.