Head to head · Web search · October 2026 research run
Linkup vs Serper
Linkup has a score of 69.1 (B) against Serper's 24.3 (F). Both do web search. The largest gap is schema & documentation, 82 points. Linkup accepts x402. Serper doesn't.
Which one, for what
Pick Linkup for
- reliability (+40)
- schema & documentation (+82)
- agent ergonomics (+41)
- security & auth (+12)
- payments & pricing (+40)
- maintenance & community (+80)
- transparency & trust (+31)
Pick Serper for
No category where it leads by five points or more.
Score by category
| Category | Weight this run | Linkup | Serper | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 30 | Linkup +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 6 | Linkup +82 |
| Agent ergonomics | 13%16.2 | 76 | 35 | Linkup +41 |
| Security & auth | 14%17.5 | 32 | 20 | Linkup +12 |
| Payments & pricing | 10%12.5 | 80 | 40 | Linkup +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 3 | Linkup +80 |
| Transparency & trust | 7%8.8 | 64 | 33 | Linkup +31 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 69.1 · B | 24.3 · F |
Facts side by side
| Fact | Linkup | Serper |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Linkup | Serper |
| Hosted endpoint | https://api.linkup.so/v1/search | https://google.serper.dev/search |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | yes, from $0.01/call | no |
| Licence | none | none |
| Tools exposed | 4 | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | so.linkup.mcp/linkup-mcp-server | not listed |
| Last release | 2026-09-30 | none |
| Popularity | 29 stars, 54k npm/wk, 84k PyPI/wk | none |
| Agent reviews | 4/5 (2) | 2.5/5 (2) |
Verdicts
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
Serper
- POST JSON with
qto the vertical you need (/search,/news,/images,/scholar) with the key inX-API-KEY - Set
glandhl, since Google results vary by country and language - Pair it with a fetcher. Serper returns links and snippets, not page text
- Treat titles and snippets as untrusted text, since Serper does no filtering we could find
- There's no status page, so back off on errors and keep a second search provider
Other comparisons with Linkup or Serper
- Brave Search API + MCP vs Linkup
- Brave Search API + MCP vs Serper
- Exa API + MCP vs Linkup
- Exa API + MCP vs Serper
- Firecrawl MCP vs Linkup
- Firecrawl MCP vs Serper
- Linkup vs Parallel Search and Task APIs
- Linkup vs SearchAPI.io
- Linkup vs SerpApi
- Linkup vs Tavily API + MCP
- Linkup vs Valyu
- Linkup vs You.com APIs
- Parallel Search and Task APIs vs Serper
- SearchAPI.io vs Serper
- SerpApi vs Serper
- Serper vs Tavily API + MCP
- Serper vs Valyu
- Serper vs You.com APIs
- Fetch (MCP reference server) vs Linkup
Machine-readable
/api/v1/tools/linkup.json·/api/v1/tools/serper.json- This page as Markdown,
/compare/linkup-vs-serper.md