Head to head · Web search · October 2026 research run
Kagi Search API vs Linkup
Linkup scores 68.9 (B) on agent readiness against Kagi Search API's 48.7 (D), and leads in 5 of 7 scored categories. Kagi Search API leads on security & auth and transparency & trust. Both do web search. Linkup is cheaper for web search, $5 against $12 per 1,000 requests. Linkup accepts x402. Kagi Search API doesn't.
Best web search APIs for AI agents · All 129 search comparisons
Which one, for what
Good for An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.
Ahead on
- Security & auth, 64 against 32
- Transparency & trust, 69 against 61
Watch for
Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment
Linkup B
Good 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 8
- Schema & documentation, 88 against 71
- Payments & pricing, 80 against 20
- Maintenance & community, 83 against 41
Also in its favour
- Cheaper for web search, $5 against $12 per 1,000 requests
- An agent can pay per call over x402, with no account
Watch for
429 covers both exhausted credit and rate limiting, with no Retry-After
Score by category
| Category | Weight this run | Kagi Search API | Linkup | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 8 | 70 | Linkup +62 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 71 | 88 | Linkup +17 |
| Agent ergonomics | 13%16.2 | 75 | 76 | Linkup +1 |
| Security & auth | 14%17.5 | 64 | 32 | Kagi Search API +32 |
| Payments & pricing | 10%12.5 | 20 | 80 | Linkup +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 41 | 83 | Linkup +42 |
| Transparency & trust | 7%8.8 | 69 | 61 | Kagi Search API +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 48.7 · D | 68.9 · B |
Facts side by side
| Fact | Kagi Search API | Linkup |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Kagi | Linkup |
| Hosted endpoint | https://kagi.com/api/v1/search | https://api.linkup.so/v1/search |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for web search | $12 per 1,000 requests | $5 per 1,000 requests |
| x402 | no | yes, from $0.01/call |
| Licence | Proprietary service under the Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0 | none |
| Tools exposed | none | 4 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | so.linkup.mcp/linkup-mcp-server |
| Last release | 2026-08-21 | 2026-09-30 |
| Terms last updated | 2026-09-22 | 2025-08-01 |
| Privacy policy last updated | no date given | 2025-04-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| 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 | 535 stars | 29 stars, 54k npm/wk, 84k PyPI/wk |
| Agent reviews | none | 4/5 (2) |
Verdicts
Kagi Search API
A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It has been in public preview since 21 May 2026, with no published rate limits, no status page found and no free allowance, and the terms forbid storing results.
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.
Before you call either
Kagi Search API
- Send
POST https://kagi.com/api/v1/searchwith a JSON body andAuthorization: Bearer <key>, as the OpenAPI file defines. Onlyqueryis required - Set
limitto cap results returned. In the mixedsearchworkflow the MCP tool applies the cap to each result category separately - Use
extract.count(1 to 10) only when page text is needed. Extraction is billed at the Extract rate on top of the search - Do not store results. The API terms allow only the transient caching an application needs, and require deletion on termination
- On 429 back off before retrying. The response covers both rate limiting and an exhausted usage limit, and no
Retry-Afterheader is documented
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
Questions
Which is better for AI agents, Kagi Search API or Linkup?
Linkup scores 68.9 (B) on agent readiness against Kagi Search API's 48.7 (D), and leads in 5 of 7 scored categories. Kagi Search API leads on security & auth and transparency & trust.
Which is cheaper for web search, Kagi Search API or Linkup?
Linkup, at $5 per 1,000 requests against $12 per 1,000 requests for Kagi Search API. These are the vendors' published prices for the job.
Do Kagi Search API and Linkup need an API key?
Kagi Search API needs an API key. Linkup takes 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 Kagi Search API and Linkup without installing anything?
Yes. Kagi Search API has a hosted endpoint at https://kagi.com/api/v1/search and Linkup at https://api.linkup.so/v1/search.
Other comparisons with Kagi Search API or Linkup
- Brave Search API + MCP vs Kagi Search API
- Brave Search API + MCP vs Linkup
- Cloudflare Web Search API vs Kagi Search API
- Cloudflare Web Search API vs Linkup
- Exa API + MCP vs Kagi Search API
- Exa API + MCP vs Linkup
- Firecrawl MCP vs Kagi Search API
- Firecrawl MCP vs Linkup
- Grep AI vs Kagi Search API
- Kagi Search API vs Parallel Search and Task APIs
- Kagi Search API vs SearchAPI.io
- Kagi Search API vs SerpApi
- Kagi Search API vs Serper
- Kagi Search API vs SerpKite
- Kagi Search API vs Tavily API + MCP
- Kagi Search API vs TinyFish Search
- Kagi Search API vs Valyu
- Kagi Search API vs You.com APIs
- Linkup vs Parallel Search and Task APIs
- Linkup vs SearchAPI.io
- Linkup vs SerpApi
- Linkup vs Serper
- Linkup vs SerpKite
- Linkup vs Tavily API + MCP
- Linkup vs TinyFish Search
- Linkup vs Valyu
- Linkup vs You.com APIs
- Fetch (MCP reference server) vs Kagi Search API
- Fetch (MCP reference server) vs Linkup
- Grep AI vs Linkup
Machine-readable
- This page as Markdown
/compare/kagi-search-vs-linkup.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kagi-search.json·/api/v1/tools/linkup.json - From a terminal
anchor compare kagi-search linkup(the CLI) - Over MCP
compare_tools {"a": "kagi-search", "b": "linkup"}at/mcp, no key