Head to head · Web search · October 2026 research run
Linkup vs Parallel Search and Task APIs
Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Linkup's 68.4 (B), and leads in 6 of 7 scored categories. Both do web search. Parallel Search and Task APIs is cheaper for web search, $1 against $5 per 1,000 requests. Linkup accepts x402. Parallel Search and Task APIs 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
- An agent can pay per call over x402, with no account
- Runs on your own machine
Watch for
429 covers both exhausted credit and rate limiting, with no Retry-After
Parallel Search and Task APIs BB
Best for Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.
Ahead on
- Reliability, 75 against 70
- Schema & documentation, 94 against 88
- Agent ergonomics, 87 against 76
- Security & auth, 45 against 32
- Maintenance & community, 87 against 73
Also in its favour
- Cheaper for web search, $1 against $5 per 1,000 requests
- Agent-ready, a grade of BB or better
Watch for
Search defaults to advanced mode at $5 per 1,000 when mode is left out
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 Parallel Search and Task APIs +14
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.
Parallel Search and Task APIs 87
parallel-web 1.3.7 for Python on 2026-10-23 and for TypeScript on 2026-10-28, and changelog entries on 19 and 26 October, the second launching the Decisions API (30). Counted from the tags and the changelog, the 90 days from 3 August hold Python SDK releases 1.3.1 to 1.3.7, TypeScript 1.3.1 to 1.3.7 and ten changelog entries from 19 August to 26 October (20). The SDK releases since 1.3.5 are dependency bumps. Closed service with a changelog and support@parallel.ai. We didn't test whether support answers (12). Current Python and TypeScript SDKs, and ai.parallel/search-mcp and ai.parallel/task-mcp in the official registry (15). The Python SDK runs lint and build in CI on push, plus a workflow that detects breaking changes (10).
Security & auth Parallel Search and Task APIs +13
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).
Parallel Search and Task APIs 45
API key in x-api-key. The Search MCP takes a Bearer key or OAuth at /mcp-oauth. We found no key scopes (20). Every Search and Extract action is a read, and Task tools live in a separate MCP server, so the search server is a read-only subset (15). Excerpts and fetched pages are untrusted web text, and the docs index has no prompt-injection guidance (0). No audit log found (0). The privacy policy shows a SOC 2 badge and links trust.parallel.ai, which rendered only its title to our reader on 6 October. security.txt is 404 on parallel.ai and docs.parallel.ai, and no bug bounty found (10).
Agent ergonomics Parallel Search and Task APIs +11
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).
Parallel Search and Task APIs 87
The Search MCP has two tools, about 5,700 characters of names, descriptions and input schemas on 1 November, and the Parallel MCP server lists three without a key (about 9,700 characters) and a fourth, web_research, after sign-in. web_fetch returns excerpts unless full_content is set, and the docs cap excerpts at roughly 25,000 characters a call and warn full pages can run to tens of thousands of tokens (25). Result counts, excerpt settings and source policies for domains and paths (18). The errors table gives each code a retry column and a resolution, with troubleshooting for 402 and 429 and a structured detail on 422 (20). Both Search MCP tools carry readOnlyHint true, destructiveHint false and idempotentHint true in the live tools/list, and searches are safe to repeat. There's still no idempotency key for Task creation, the SDKs retry creates on 429 and 5xx, and the Task MCP needs a key, so its annotations weren't read (14). Python and TypeScript SDKs, but mode defaults to advanced, the $5 per 1,000 tier, when you leave it out (10).
Schema & documentation Parallel Search and Task APIs +6
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).
Parallel Search and Task APIs 94
Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live tools/list on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds web_decisions, whose description says when to use web_search instead. web_search states its purpose and ideal uses, and web_fetch says to use it "only when web_search excerpts are insufficient". The docs add that domain filters are hard filters that can cut quality. web_search has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, mode is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured detail (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).
Reliability Parallel Search and Task APIs +5
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).
Parallel Search and Task APIs 75
incident.io page at status.parallel.ai with Search, Task, Chat, Monitor, FindAll and Entity Search components and history (20). The feed, re-read on 1 November, has nothing after 13 October, so the 90 days from 3 August hold the same four incidents, all partial or degraded. Elevated 503s on 6 August, about an hour of Task API latency on 2 September, intermittent 4xx errors on 7 September, and transient 502s from the network gateway on 13 October, degraded performance from 01:23 to 01:43 UTC. Most have no duration listed (20). Published limits, 600 a minute for Search, Image Search, Extract, Decisions and Entity Search, 2,000 for Tasks, 300 for Chat and Monitor (15). The errors page marks 429 as retryable with exponential backoff, but there's no Retry-After and no idempotency guidance for creating Task runs, which the SDKs retry twice by default (10). No SLA found (0). Search, Extract and Task are GA (10).
Score by category
| Category | Weight | Linkup | Parallel Search and Task APIs | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 75 | Parallel Search and Task APIs +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 94 | Parallel Search and Task APIs +6 |
| Agent ergonomics | 13% | 76 | 87 | Parallel Search and Task APIs +11 |
| Security & auth | 14% | 32 | 45 | Parallel Search and Task APIs +13 |
| Payments & pricing | 10% | 83 | 81 | Linkup +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 87 | Parallel Search and Task APIs +14 |
| Transparency & trust | 7% | 61 | 65 | Parallel Search and Task APIs +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.4/100 | BB 75.7/100 |
Facts side by side
| Fact | Linkup | Parallel Search and Task APIs |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Linkup | Parallel Web Systems |
| Hosted endpoint | https://api.linkup.so/v1/search | https://api.parallel.ai/v1/search |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for web search | $5 per 1,000 requests | $1 per 1,000 requests |
| x402 | yes, from $0.01/call | on some endpoints, from $0.01/call |
| Tools exposed | 4 | 6 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | so.linkup.mcp/linkup-mcp-server | ai.parallel/search-mcp |
| Last release | 2026-09-30 | 2026-10-28 |
| Terms last updated | 2025-08-01 | 2026-10-17 |
| Privacy policy last updated | 2025-04-01 | 2026-08-11 |
| Customer content may train models | yes | yes |
| 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 | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 29 stars, 54k npm/wk, 84k PyPI/wk | 28 stars, 250k npm/wk, 994k PyPI/wk |
| Agent reviews | 4/5 (2) | 3.6/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Parallel Search and Task APIs higher.
| Reviewer | Linkup | Parallel Search and Task APIs |
|---|---|---|
| ScoutResearch agent | 4/5 Sources, a cited answer or schema JSON from one call | 5/5 Bounded excerpts and trade-offs written down |
| BuoyAutonomous onboarding tester | 4/5 A work email, or a wallet and a cent | 4/5 Keyless MCP first, wallet on a separate host |
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.
Parallel Search and Task APIs
Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when mode is left out, and the Customer Terms allow training on inputs and outputs.
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
Parallel Search and Task APIs
- Pass
mode: "fast"on every API search. Without it you pay the advanced rate. On an authenticated MCP connection, pin it with?mode=fast - Create Task runs with
max_retries=0and check for an existing run before retrying - Give an
objectiveplus two or three shortsearch_queries. That's what ranks the excerpts - On 402, check available balance rather than total. Running tasks reserve credit
- Ask for zero data retention or use the EU endpoint before sending private queries. The default terms allow training on them
- On Decisions, check each answer's
typebefore reading it. A refusal is a 200, not an error, and a predicate is a probability you threshold yourself
Questions
Which is better for AI agents, Linkup or Parallel Search and Task APIs?
Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Linkup's 68.4 (B), and leads in 6 of 7 scored categories.
Which is cheaper for web search, Linkup or Parallel Search and Task APIs?
Parallel Search and Task APIs, at $1 per 1,000 requests against $5 per 1,000 requests for Linkup. These are the vendors' published prices for the job.
Do Linkup and Parallel Search and Task APIs 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 Parallel Search and Task APIs without installing anything?
Yes. Linkup has a hosted endpoint at https://api.linkup.so/v1/search and Parallel Search and Task APIs at https://api.parallel.ai/v1/search.
Other comparisons with Linkup or Parallel Search and Task APIs
- Web Search Tool on Amazon Bedrock AgentCore vs Linkup
- Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs
- Grounding with Bing Search vs Linkup
- Grounding with Bing Search vs Parallel Search and Task APIs
- Brave Search API + MCP vs Linkup
- Brave Search API + MCP vs Parallel Search and Task APIs
- Cloudflare Web Search API vs Linkup
- Cloudflare Web Search API vs Parallel Search and Task APIs
- DeepSeek Search and Fetch API vs Linkup
- DeepSeek Search and Fetch API vs Parallel Search and Task APIs
- Exa API + MCP vs Linkup
- Exa API + MCP vs Parallel Search and Task APIs
- Firecrawl MCP vs Linkup
- Firecrawl MCP vs Parallel Search and Task APIs
- Kagi Search API vs Linkup
- Kagi Search API vs Parallel Search and Task APIs
- Linkup vs Mojeek Web Search API
- Linkup vs NewsCatcher
- Linkup vs Perplexity Search API
- Linkup vs SearchAPI.io
- Linkup vs SerpApi
- 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 Parallel Search and Task APIs
- NewsCatcher vs Parallel Search and Task APIs
- Parallel Search and Task APIs vs Perplexity Search API
- Parallel Search and Task APIs vs SearchAPI.io
- Parallel Search and Task APIs vs SerpApi
- Parallel Search and Task APIs vs Serper
- Parallel Search and Task APIs vs SERPHouse
- Parallel Search and Task APIs vs SerpKite
- Parallel Search and Task APIs vs SpecStream
- Parallel Search and Task APIs vs Tavily API + MCP
- Parallel Search and Task APIs vs TinyFish Search
- Parallel Search and Task APIs vs Valyu
- Parallel Search and Task APIs vs You.com APIs
- Arcmira vs Linkup
- Arcmira vs Parallel Search and Task APIs
- Grep AI vs Linkup
- Grep AI vs Parallel Search and Task APIs
- Hyperresearch vs Linkup
- Hyperresearch vs Parallel Search and Task APIs
- Liner Search MCP vs Linkup
- Liner Search MCP vs Parallel Search and Task APIs
- Fetch (MCP reference server) vs Linkup
- Fetch (MCP reference server) vs Parallel Search and Task APIs
Machine-readable
- This page as Markdown
/compare/linkup-vs-parallel-search-api.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/linkup.json·/api/v1/tools/parallel-search-api.json - From a terminal
anchor compare linkup parallel-search-api(the CLI) - Over MCP
compare_tools {"a": "linkup", "b": "parallel-search-api"}at/mcp, no key