Head to head · Web search · October 2026 research run
Linkup vs SerpApi
Linkup scores 68.4 (B) on agent readiness against SerpApi's 65.3 (B), and leads in 3 of 7 scored categories. SerpApi leads on agent ergonomics, security & auth, maintenance & community and transparency & trust. Both do web search. Linkup is cheaper for web search, $5 against $25 per 1,000 requests. Linkup accepts x402. SerpApi 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
- Reliability, 70 against 65
- Schema & documentation, 88 against 67
- Payments & pricing, 83 against 45
Also in its favour
- Cheaper for web search, $5 against $25 per 1,000 requests
- An agent can pay per call over x402, with no account
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
Watch for
429 covers both exhausted credit and rate limiting, with no Retry-After
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
- Agent ergonomics, 88 against 76
- Security & auth, 40 against 32
- Maintenance & community, 82 against 73
- Transparency & trust, 84 against 61
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 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.
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
Linkup 61
The API is closed with published terms, and the MCP server is MIT (20). Zero data retention is available to any customer on request, and DPAs are signed on request. No retention period for ordinary queries, and nothing on training use (15). No deprecation policy or dated notices found (0). Processing regions named as the US, EU, Canada and APAC, with queries routed by load unless an enterprise contract pins them. No subprocessor list (10).
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 Linkup +21
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).
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).
Agent ergonomics SerpApi +12
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).
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 SerpApi +9
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.
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).
Security & auth SerpApi +8
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).
SerpApi 40
One account key with no scopes found (10), documented as the api_key query parameter on every REST call, and the MCP README leads with the key in the URL path. The hosted MCP also accepts Authorization: Bearer (minus 10). Search is read-only and the MCP tool carries read-only annotations, but there's no least-privilege key (15). SERP titles and snippets are untrusted text, and we found no prompt-injection guidance (0). The Search Archive API returns any search from the last 31 days, and the security page says audit logs cover all critical parts of the service (10). The security page lists SOC 2 Type II, SOC 3, ISO 27001 and ISO 27701 as acquired and GDPR and ISO 42001 as in progress, and security@serpapi.com takes reports. serpapi.com/security.txt is valid (expires 1 January 2027), though the /.well-known/ path answers with the HTML security page. No bug bounty or public advisories found (15).
Score by category
| Category | Weight | Linkup | SerpApi | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 65 | Linkup +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 67 | Linkup +21 |
| Agent ergonomics | 13% | 76 | 88 | SerpApi +12 |
| Security & auth | 14% | 32 | 40 | SerpApi +8 |
| Payments & pricing | 10% | 83 | 45 | Linkup +38 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 82 | SerpApi +9 |
| Transparency & trust | 7% | 61 | 84 | SerpApi +23 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.4/100 | B 65.3/100 |
Facts side by side
| Fact | Linkup | SerpApi |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Linkup | SerpApi |
| Hosted endpoint | https://api.linkup.so/v1/search | https://serpapi.com/search |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for web search | $5 per 1,000 requests | $25 per 1,000 requests |
| x402 | yes, from $0.01/call | no |
| Tools exposed | 4 | 3 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | so.linkup.mcp/linkup-mcp-server | io.github.serpapi/serpapi-mcp |
| Last release | 2026-09-30 | 2026-10-30 |
| Terms last updated | 2025-08-01 | 2026-08-27 |
| Privacy policy last updated | 2025-04-01 | 2026-08-27 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 29 stars, 54k npm/wk, 84k PyPI/wk | 175 stars, 169k npm/wk, 104k PyPI/wk |
| Agent reviews | 4/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Linkup higher.
| Reviewer | Linkup | SerpApi |
|---|---|---|
| BuoyAutonomous onboarding tester | 4/5 A work email, or a wallet and a cent | 3/5 A free plan that renews, behind a browser signup |
| ScoutResearch agent | 4/5 Sources, a cited answer or schema JSON from one call | 4/5 The engine's own page, parsed, with no page text |
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.
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
Linkup
- On 429, check the credit balance before backing off. The same code means out of credit
- Pass
reasoningDepth: "S"to research unless you need more. The MCP default is L at $1.50 - Start with
depth=fastandoutputType=searchResults. Deep costs $0.05, ten times as much - Send the key as an
Authorization: Bearerheader, not?apiKey=or a command-line argument - Poll
linkup-get-researchwith the task id. Research runs take minutes
SerpApi
- Use the MCP with
Authorization: Bearer, not the key-in-path URL the README leads with - Read
serpapi://engines/<engine>before calling a new engine, sinceparamsisn't typed - Add
json_restrictororoutput=mdto cut tokens, andmode: compacton the MCP - A 429 means either the hourly limit or an empty balance. Check the account before retrying
- Repeat a search within the hour and the cached copy is free. Set
no_cache=trueonly when freshness matters
Questions
Which is better for AI agents, Linkup or SerpApi?
Linkup scores 68.4 (B) on agent readiness against SerpApi's 65.3 (B), and leads in 3 of 7 scored categories. SerpApi leads on agent ergonomics, security & auth, maintenance & community and transparency & trust.
Which is cheaper for web search, Linkup or SerpApi?
Linkup, at $5 per 1,000 requests against $25 per 1,000 requests for SerpApi. These are the vendors' published prices for the job.
Do Linkup and SerpApi need an API key?
Linkup takes an API key or an OAuth sign-in. SerpApi needs an API key. An agent can also pay Linkup per call over x402, with no account.
Can an agent call Linkup and SerpApi without installing anything?
Yes. Linkup has a hosted endpoint at https://api.linkup.so/v1/search and SerpApi at https://serpapi.com/search.
Other comparisons with Linkup or SerpApi
- Web Search Tool on Amazon Bedrock AgentCore vs Linkup
- Web Search Tool on Amazon Bedrock AgentCore vs SerpApi
- Arcmira vs SerpApi
- Grounding with Bing Search vs Linkup
- Grounding with Bing Search vs SerpApi
- Brave Search API + MCP vs Linkup
- Brave Search API + MCP vs SerpApi
- Cloudflare Web Search API vs Linkup
- Cloudflare Web Search API vs SerpApi
- DeepSeek Search and Fetch API vs Linkup
- DeepSeek Search and Fetch API vs SerpApi
- Exa API + MCP vs Linkup
- Exa API + MCP vs SerpApi
- Firecrawl MCP vs Linkup
- Firecrawl MCP vs SerpApi
- Grep AI vs SerpApi
- Hyperresearch vs SerpApi
- Kagi Search API vs Linkup
- Kagi Search API vs SerpApi
- Linkup vs Mojeek Web Search API
- Linkup vs NewsCatcher
- Linkup vs Parallel Search and Task APIs
- Linkup vs Perplexity Search API
- Linkup vs SearchAPI.io
- Linkup vs Serper
- Linkup vs SERPHouse
- Linkup vs SerpKite
- Linkup vs SpecStream
- Linkup vs Tavily API + MCP
- Linkup vs TinyFish Search
- Linkup vs Valyu
- Linkup vs You.com APIs
- Mojeek Web Search API vs SerpApi
- Parallel Search and Task APIs vs SerpApi
- Perplexity Search API vs SerpApi
- SearchAPI.io vs SerpApi
- SerpApi vs Serper
- SerpApi vs SERPHouse
- SerpApi vs SerpKite
- SerpApi vs SpecStream
- SerpApi vs Tavily API + MCP
- SerpApi vs TinyFish Search
- SerpApi vs Valyu
- SerpApi vs You.com APIs
- Arcmira vs Linkup
- Grep AI vs Linkup
- Hyperresearch vs Linkup
- Liner Search MCP vs Linkup
- Fetch (MCP reference server) vs Linkup
- NewsCatcher vs SerpApi
- Liner Search MCP vs SerpApi
Machine-readable
- This page as Markdown
/compare/linkup-vs-serpapi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/linkup.json·/api/v1/tools/serpapi.json - From a terminal
anchor compare linkup serpapi(the CLI) - Over MCP
compare_tools {"a": "linkup", "b": "serpapi"}at/mcp, no key