Head to head · Web search · October 2026 research run
SearchAPI.io vs SerpKite
SerpKite scores 70.1 (BB) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io leads on reliability. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
Best for Agents that need parsed results from many engines, especially shopping, ads, travel and social sources, at a low price per search.
Ahead on
- Reliability, 90 against 75
Also in its favour
- No incidents deducted, where SerpKite loses 3 points for them
Watch for
MCP loads one tool per engine with no toolsets
SerpKite BB
Best for Agents that want Google results and the top pages as Markdown in one call at a low per-1,000 price, with spend caps per key.
Ahead on
- Schema & documentation, 90 against 59
- Agent ergonomics, 97 against 52
- Security & auth, 37 against 28
- Payments & pricing, 60 against 45
- Maintenance & community, 80 against 0
- Transparency & trust, 77 against 62
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October
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 SerpKite +80
SearchAPI.io 0
No changelog (/changelog answered 404 on 4 November 2026) and no dated API change found, so the last release can't be dated (0). No releases to count (0). No public issue tracker or changelog to judge replies by. A Discord server is linked from the footer and wasn't tested (0). The 15 for io.searchapi/mcp in the official MCP registry rested on a reading of the registry's JSON API, which this run doesn't use, and no ordinary registry page shows the entry, so the line falls to 0, as graphiti, linear-mcp and copilot-studio-mcp read it. No official SDKs were found; the footer links a GitHub organisation whose pages answered 403 (0, 15 before). No public packages or CI (0). 0 + 0 + 0 + 0 + 0 = 0.
SerpKite 80
Closed service read with the API lines. The newest API changelog entries are dated 1 November 2026 (API 1.12.7) (30). 31 dated changelog entries from 9 October to 1 November, among them API 1.6.0 to 1.12.7 and SDKs 0.8.0 and 0.8.1 (20). Public changelog, support@serpkite.com and a Discord link. The SDK repositories are mirrors of a private monorepo and we couldn't see issues or replies (8). In the official MCP registry under the GitHub-verified namespace io.github.SerpKite, per the 5 October check, with current official SDKs in three languages (15). The SDK repositories run typecheck, tests and build in CI, but we couldn't see run results (7). 30+20+8+15+7 = 80.
Agent ergonomics SerpKite +45
SearchAPI.io 52
The MCP exposes over 100 tools, one or more per engine, with no toolsets or filtering documented (5). page, time_period, location, country, language and safe search. Google's num has been fixed at 10 since September 2025 (18). Status codes are documented, but not how to recover from each (12). Searches are reads, and only HTTP 200 responses are billed, so retries are cheap. MCP annotations aren't visible (10). Two required parameters, engine and q. No official SDKs (7).
SerpKite 97
format=markdown or compact, fields projection, num and an X-Tokens-Estimate header size REST responses. The MCP server now has 23 tools with no toolsets or read-only subset we could find (22). page, num up to 100, country, language, location, time, domain include, exclude and boost, date bounds, highlights and max_tokens on extract (20). Stable error codes with a retry column, and errors are never billed (20). Searches are read-only, failed and empty calls are refunded, and batch creation takes Idempotency-Key. Since 9 October 2026 the changelog says every MCP tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, with all read-only except crawl, and on 2 November the MCP page says every tool is read-only except crawl and research, which start paid tasks, and none is destructive (20). Only q or url is required, and official SDKs exist for TypeScript, Python and Go with retries built in (15). 22+20+20+20+15 = 97.
Schema & documentation SerpKite +31
SearchAPI.io 59
OpenAPI 3.0 for the Google engine at /openapi/google.yaml with 25 typed parameters. We found no index of specs for the other engines, so 20 of 25. No llms.txt (404 on 4 November 2026) and no Markdown docs for agents (0). The API reference explains each parameter, and the MCP tool definitions aren't public (10). Enums for device, country, language, safe search and time period (14). Examples and a Postman collection, and the spec documents 400, 401, 403, 429 and 500 (12). /api/v1 in the path and no changelog anywhere we looked (3).
SerpKite 90
Public OpenAPI 3.1 spec (version 1.12.7 on 2 November 2026, 41 paths and 47 operations) at serpkite.com/openapi/serp-api.yaml (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Endpoint descriptions state purpose and when to use them, and the guides cover which tool to pick. The MCP tool definitions aren't public and tools/list needs a key, so we read the MCP docs table and the matching descriptions in the MIT AI SDK package, which state purpose and some when-to-use lines but not when not to (12). Typed parameters with 64 enums in the spec, documented ranges and strict validation that rejects unknown parameters with a 400 naming the replacement. We couldn't confirm the MCP JSON Schemas (13). curl, TypeScript, Python and Go examples on each page, and an errors page with 14 codes and what to do about each (15). Versioned /v1 paths and a dated API changelog (15).
Reliability SearchAPI.io +15
SearchAPI.io 90
Honeybadger status page at status.searchapi.io with Landing Page and API components and monthly history (20). Re-read on 4 November 2026, it shows no incidents in September, October or November 2026, and its incident feed's newest entry is the 11 February 2026 partial outage, so the window from 6 August is clean (30). The hourly cap is published, 20 per cent of the plan's monthly searches in any hour (15). The OpenAPI file lists a 429 response with an error string, but no Retry-After or backoff guidance was found. The partial 5 is kept pending the founder's rule on in-between values (5). The terms of 11 April 2026 give a 99.9% SLA for all plans with a credit of 100% of the monthly price, and the pricing page lists it on every plan (10). GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.
SerpKite 75
Hosted API, read with the hosted lines. Better Stack status page at status.serpkite.com with four monitors (api.serpkite.com/healthz, dashboard API, dashboard, website) and daily bars (20). Monitoring began on 2 October 2026, so the record covers 31 days of the 90 from 4 August. The page's own figures give 99.978 per cent uptime over 30 days for the API health monitor and 99.971 for the dashboard API, the 5 October check saw 29 to 41 minutes of downtime on each monitor on 2 October and 19 seconds on 3 October, and the feed has never carried an incident post. No outage reached an hour. A readable record shorter than 90 days with nothing major scores 15, as this run settled for short records. Rate limits published per key, 5 to 100 requests a second by pack (15). 429 rate_limited with Retry-After, backoff guidance for 429 and 503, and Idempotency-Key on batch creation (15). The terms say self-serve plans have no uptime guarantee and an enterprise SLA sits in a separate agreement we couldn't read (0). v1 API with no beta or preview label (10). 20+15+15+15+0+10 = 75.
Payments & pricing SerpKite +15
SearchAPI.io 45
No x402, MPP or L402 (0). Monthly plans only, priced in public, from $40 for 10,000 searches to $5,000 for 5 million (10). 100 free requests with no card (20). A person has to sign up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
SerpKite 60
No x402, MPP or L402 in llms.txt, the OpenAPI spec or the pricing page (0). Per-pack and per-credit prices published without a login, $1.00 to $0.60 per 1,000 (20). Free credits on signup and 1,000 a month with no card, per the quickstart and home page (20). A person signs in by email, GitHub or Google 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.
Transparency & trust SerpKite +15
SearchAPI.io 62
Closed service with published terms (15). Privacy policy dated 11 April 2026. Data sits in the US, cached results are purged on an unstated schedule, and zero retention is Enterprise only (15). Google's num phase-out is documented, and there's no deprecation policy (3). US data location stated, and the privacy policy links a subprocessor page (15).
SerpKite 77
Closed API under terms that name the operator, an Ontario address and governing law, with the SDKs and the MCP connection repository MIT (18). The privacy policy, DPA page, retention doc and security page agree that query text of successful requests isn't logged, usage metadata lasts 31 days and batch results 24 hours. On 26 October failed and empty requests began keeping their query for 24 hours, and the changelog says the privacy policy, terms and DPA were updated the same day (27). The terms promise 30 days' notice before removing an endpoint, with exceptions for changes forced by a third party. AI Overview, AI Mode and Lens were removed in the first week without notice under that exception, and the reviews limit of 16 October came the same way, while a batch price change for 23 November 2026 was announced ahead (14). Subprocessors named with purpose and location, including Contabo in Germany, Cloudflare, Paddle, Resend, PostHog EU and Better Stack, with 30 days' notice of changes (20).
Score by category
| Category | Weight | SearchAPI.io | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 75 | SearchAPI.io +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 90 | SerpKite +31 |
| Agent ergonomics | 13% | 52 | 97 | SerpKite +45 |
| Security & auth | 14% | 28 | 37 | SerpKite +9 |
| Payments & pricing | 10% | 45 | 60 | SerpKite +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 0 | 80 | SerpKite +80 |
| Transparency & trust | 7% | 62 | 77 | SerpKite +15 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 52/100 | BB 70.1/100 |
Facts side by side
| Fact | SearchAPI.io | SerpKite |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SearchApi | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | https://www.searchapi.io/api/v1/search | https://api.serpkite.com/v1/search |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for web search | $4 per 1,000 requests | not published |
| x402 | no | no |
| Licence | none | Proprietary service under SerpKite's terms of service. The SDKs (TypeScript, Python, Go, LangChain, Vercel AI SDK) and the MCP connection repository on GitHub are MIT |
| Tools exposed | none | 23 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | io.searchapi/mcp | io.github.SerpKite/serpkite |
| Last release | none | 2026-11-01 |
| Terms last updated | 2026-04-11 | 2026-10-03 |
| Privacy policy last updated | 2026-04-11 | 2026-10-03 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 809 npm/wk, 376 PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
How the scores have moved
Verdicts
SearchAPI.io
A 99.9% SLA in the terms on every plan, no status-page incidents since 11 February 2026, and over 150 engine endpoints behind one URL. The MCP loads one tool per engine with no toolsets, there is no changelog or official SDK, and every account starts with a browser signup.
SerpKite
Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with a month of status history and frequent same-day contract changes.
Before you call either
SearchAPI.io
- Send the key as
Authorization: Bearer, notapi_key=in the URL - Connect the MCP through OAuth or the
X-MCP-Tokenheader. Never put the token in the MCP URL - Call the REST API with
engine=when context is tight. The MCP loads one tool definition per engine - Page Google results with
page.numis fixed at 10 - Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches
SerpKite
- Send the key as
Authorization: Bearer, not?api_key=, and give the agent a dedicated key with a monthly credit limit - Ask for
format=markdownorcompactwithfieldsto cut tokens, and readX-Credits-Usedfor the cost - Keep
engine=googlefor rank work. Checkmeta.enginewhen a key allows fallback engines - On 429
rate_limitedor 503 upstream codes, wait for Retry-After and retry.daily_limit_reached,account_restricted(403) and 402 need a purchase - Treat page Markdown from
include_content,webpageandextractas untrusted text
Questions
Which is better for AI agents, SearchAPI.io or SerpKite?
SerpKite scores 70.1 (BB) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io leads on reliability.
Do SearchAPI.io and SerpKite need an API key?
SearchAPI.io takes an API key or an OAuth sign-in. SerpKite needs an API key.
Can an agent call SearchAPI.io and SerpKite without installing anything?
Yes. SearchAPI.io has a hosted endpoint at https://www.searchapi.io/api/v1/search and SerpKite at https://api.serpkite.com/v1/search.
Other comparisons with SearchAPI.io or SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Arcmira vs SearchAPI.io
- Arcmira vs SerpKite
- Grounding with Bing Search vs SearchAPI.io
- Grounding with Bing Search vs SerpKite
- Brave Search API + MCP vs SearchAPI.io
- Brave Search API + MCP vs SerpKite
- Cloudflare Web Search API vs SearchAPI.io
- Cloudflare Web Search API vs SerpKite
- DeepSeek Search and Fetch API vs SearchAPI.io
- DeepSeek Search and Fetch API vs SerpKite
- Exa API + MCP vs SearchAPI.io
- Exa API + MCP vs SerpKite
- Firecrawl MCP vs SearchAPI.io
- Firecrawl MCP vs SerpKite
- Grep AI vs SearchAPI.io
- Grep AI vs SerpKite
- Hyperresearch vs SearchAPI.io
- Hyperresearch vs SerpKite
- Kagi Search API vs SearchAPI.io
- Kagi Search API vs SerpKite
- Linkup vs SearchAPI.io
- Linkup vs SerpKite
- Mojeek Web Search API vs SearchAPI.io
- Mojeek Web Search API vs SerpKite
- Parallel Search and Task APIs vs SearchAPI.io
- Parallel Search and Task APIs vs SerpKite
- Perplexity Search API vs SearchAPI.io
- Perplexity Search API vs SerpKite
- SearchAPI.io vs SerpApi
- SearchAPI.io vs Serper
- SearchAPI.io vs SERPHouse
- SearchAPI.io vs SpecStream
- SearchAPI.io vs Tavily API + MCP
- SearchAPI.io vs TinyFish Search
- SearchAPI.io vs Valyu
- SearchAPI.io vs You.com APIs
- SerpApi vs SerpKite
- Serper vs SerpKite
- SerpKite vs SpecStream
- SerpKite vs Tavily API + MCP
- SerpKite vs TinyFish Search
- SerpKite vs Valyu
- SerpKite vs You.com APIs
- Fetch (MCP reference server) vs SerpKite
- NewsCatcher vs SearchAPI.io
- NewsCatcher vs SerpKite
- Liner Search MCP vs SearchAPI.io
- Liner Search MCP vs SerpKite
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/searchapi-io-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/searchapi-io.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare searchapi-io serpkite(the CLI) - Over MCP
compare_tools {"a": "searchapi-io", "b": "serpkite"}at/mcp, no key