Head to head · Web search · October 2026 research run

Linkup vs Serper

Linkup scores 68.4 (B) on agent readiness against Serper's 11.7 (F), and leads in every scored category. Both do web search. Linkup accepts x402. Serper 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 30
  • Schema & documentation, 88 against 6
  • Agent ergonomics, 76 against 35
  • Security & auth, 32 against 20
  • Payments & pricing, 83 against 60
  • Maintenance & community, 73 against 3
  • Transparency & trust, 61 against 32

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 2.5 out of 5
  • No incidents deducted, where Serper loses 15 points for them

Watch for

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

Serper F

Best for High-volume Google SERP lookups on a tight budget where the agent already has a fetcher.

Also in its favour

  • Free to start without a card

Watch for

No status page, SLA or incident history

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.

Schema & documentation Linkup +82

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

Serper 6

No OpenAPI or other spec (0). serper.dev/llms.txt returned 404 on 11 November and there are no Markdown docs (0). The documentation is the playground, a JavaScript page that showed us no text on 11 November. Per the 30 September check it lists the verticals and parameters such as gl and hl, so a few points for descriptions (3) and typed inputs (3). No examples or error responses we could read (0). No changelog or API versioning (0).

Maintenance & community Linkup +70

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.

Serper 3

No changelog, release notes, SDK or package found, so no dated release or API change to count (0, 0). No public changelog. Support is by email per the privacy policy (3). No official SDKs (0). No packages or CI to assess (0).

Agent ergonomics Linkup +41

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

Serper 35

Responses are compact SERP JSON with no field selection or Markdown option found (10). Country and language parameters (the home page FAQ confirms both) and ten separate verticals. We couldn't confirm pagination or result-count parameters from the docs (8). No documented error responses (0). Searches are read-only, and the home page FAQ says credits are deducted only for successful responses (10). One required field (q) and no official SDK (7).

Reliability Linkup +40

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

Serper 30

No status page we could read. The site footer now has a "Status page" button drawn by script with no link, and status.serper.dev, whose robots.txt (Atlassian Statuspage) allows all but /api/ and /embed/, still redirects its home page and /history.atom to Atlassian's Statuspage marketing site on 11 November, as on 30 September (0). No readable incident history (5). Rate limits by pack, 50 queries a second on Starter, 100 on Standard, 200 on Scale and 300 on Ultimate, raised on request, now read from the served home page (15). No 429 or retry guidance found (0). No SLA in the terms (0). GA (10).

Transparency & trust Linkup +29

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

Serper 32

Closed service. The terms exist (updated 29 May 2024, UK law) but name no legal entity, only 'Serper' (8). The privacy policy (last reviewed 5 November 2025) says the service 'should normally not lead to the processing of personal data' and keeps most personal data for the life of the account, but states no retention period for queries or results (10). No deprecation policy or dated notices (0). Data processors are described by category without names, with transfers outside the EEA under an adequacy decision or standard contractual clauses (5).

Payments & pricing Linkup +23

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.

Serper 60

No x402, MPP or L402. The FAQ lists major credit cards and PayPal only (0). Per-1,000 prices published without a login, from $1.00 on the $50 pack to $0.30 on the $3,750 pack, excluding sales tax (20). 2,500 free queries on sign-up, "No credit card required" on the home page (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightLinkupSerperEdge
Reliability16%7030Linkup +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%886Linkup +82
Agent ergonomics13%7635Linkup +41
Security & auth14%3220Linkup +12
Payments & pricing10%8360Linkup +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%733Linkup +70
Transparency & trust7%6132Linkup +29
Negative events≤150-15
TotalB 68.4/100F 11.7/100

Facts side by side

FactLinkupSerper
KindHTTP APIHTTP API
VendorLinkupSerper
Hosted endpointhttps://api.linkup.so/v1/searchhttps://google.serper.dev/search
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for web search$5 per 1,000 requestsnot published
x402yes, from $0.01/callno
Tools exposed4none
Read-only variant documentednono
llms.txtyesno
MCP registryso.linkup.mcp/linkup-mcp-servernot listed
Last release2026-09-30none
Terms last updated2025-08-012024-05-29
Privacy policy last updated2025-04-012025-11-05
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
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)2.5/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.

Serper

$0.30 to $1.00 per 1,000 queries on prepaid packs, with no subscription. No status page, SLA or incident history.

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

Serper

  1. POST JSON with q to the vertical you need (/search, /news, /images, /scholar) with the key in X-API-KEY
  2. Set gl and hl, since Google results vary by country and language
  3. Pair it with a fetcher. Serper returns links and snippets, not page text
  4. Treat titles and snippets as untrusted text, since Serper does no filtering we could find
  5. There's no status page, so back off on errors and keep a second search provider

Questions

Which is better for AI agents, Linkup or Serper?

Linkup scores 68.4 (B) on agent readiness against Serper's 11.7 (F), and leads in every scored category.

Do Linkup and Serper need an API key?

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

Can an agent call Linkup and Serper without installing anything?

Yes. Linkup has a hosted endpoint at https://api.linkup.so/v1/search and Serper at https://google.serper.dev/search.

Other comparisons with Linkup or Serper

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.