Head to head · Web search · October 2026 research run
SerpApi vs SerpKite
SerpKite scores 70.1 (BB) on agent readiness against SerpApi's 65.3 (B), and leads in 4 of 7 scored categories. SerpApi leads on transparency & trust. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
SerpApi B
Best for An agent that needs what a specific engine shows (Google verticals, Maps, Shopping, Flights, Scholar, YouTube, Amazon) parsed to JSON.
Ahead on
- Transparency & trust, 84 against 77
Also in its favour
- Runs on your own machine
- No incidents deducted, where SerpKite loses 3 points for them
Watch for
35 incidents on the status page between 4 August and 2 November 2026, including an outage across all APIs on 10 September
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
- Reliability, 75 against 65
- Schema & documentation, 90 against 67
- Agent ergonomics, 97 against 88
- Payments & pricing, 60 against 45
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
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.
Schema & documentation SerpKite +23
SerpApi 67
No OpenAPI or similar spec for the REST API. The MCP server publishes per-engine parameter lists as resources (serpapi://engines/<engine>), which we count as a partial contract (10). llms.txt, pricing.md and Markdown twins of the docs pages, such as search-api.md (10). Each engine page describes every parameter, and the MCP tool says when to use it but not when not to (14). Parameters list allowed values on the engine pages, but the MCP search tool takes one free-form params object (7). Examples on every engine page, and a status-and-errors page documents 400, 401, 403, 404, 410, 429 and 5xx with a JSON error field (14). Dated release notes with several entries a week, though the API itself isn't versioned (12).
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).
Payments & pricing SerpKite +15
SerpApi 45
No x402, MPP or L402 on the pricing page or llms.txt (0). Monthly plans are public with search counts, but there's no pay-per-search option (10). Free plan of 250 searches a month, no card (20). An account needs a browser signup (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.
Reliability SerpKite +10
SerpApi 65
Atlassian Statuspage at status.serpapi.com, with per-API components and incident history on its history pages and Atom feed (20). Between 4 August and 2 November the history lists 35 incidents active in the window. Two were wide failures that also list the general API component, each over an hour. From 7 to 9 August an outage across 37 Google and Google Light APIs, including Search, left 'a large number of requests' failing or timing out. On 10 September the vendor posted a 'service outage across all of our APIs', with degradation until 17 September. From 6 October a degradation of 15 Google and Google Light APIs, including Search, which the vendor called a 'partial service outage affecting multiple APIs', was still open on 2 November. Like the single-engine incidents, it hit part of the product and counts as minor. Two majors (5). Hourly throughput published per plan, 50 an hour free to 640,000 on Cloud 54M (15). 429 is documented as either the hourly limit or an empty search balance, with no Retry-After or backoff guidance found (5). The terms (updated 27 August 2026) promise a 99.95% SLA on all plans with credits up to 100% (10). GA (10). 20 + 5 + 15 + 5 + 10 + 10 = 65.
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.
Agent ergonomics SerpKite +9
SerpApi 88
json_restrictor selects fields, output=md returns Markdown (the MCP README claims 50 per cent fewer tokens on average) and the MCP compact mode drops metadata. One core MCP tool plus two opt-in UI tools (22). start, num, location, language and engine-specific filters, plus async with the Search Archive API (20). Documented status codes and search_metadata.status values, though one 429 covers both the hourly limit and an empty balance (14). Searches are read-only, failed and cached searches aren't billed, and the MCP tool sets readOnlyHint true and destructiveHint false (18). Only q is required for most engines. llms.txt lists libraries in 11 languages, though the JavaScript one hasn't had a release since July 2025 (14).
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.
Transparency & trust SerpApi +7
SerpApi 84
The API is closed under one terms-and-privacy page, and the MCP server is MIT (18). The legal page and the security page agree that search data is deleted after 31 days, ZeroTrace mode (an enterprise parameter) stores nothing, and a DPA is available on request (26). Deprecations show up as dated release notes, such as eBay's Sold and Completed filters on 28 September 2026, but there's no notice policy, and the terms allow termination without notice (8). Named subprocessors (AWS, Cloudflare, Wasabi, Stripe, Intercom and others) and US hosting with Standard Contractual Clauses (18).
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 | SerpApi | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 75 | SerpKite +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 67 | 90 | SerpKite +23 |
| Agent ergonomics | 13% | 88 | 97 | SerpKite +9 |
| Security & auth | 14% | 40 | 37 | SerpApi +3 |
| Payments & pricing | 10% | 45 | 60 | SerpKite +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 80 | SerpApi +2 |
| Transparency & trust | 7% | 84 | 77 | SerpApi +7 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 65.3/100 | BB 70.1/100 |
Facts side by side
| Fact | SerpApi | SerpKite |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SerpApi | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | https://serpapi.com/search | https://api.serpkite.com/v1/search |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| Price for web search | $25 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 | 3 | 23 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | io.github.serpapi/serpapi-mcp | io.github.SerpKite/serpkite |
| Last release | 2026-10-30 | 2026-11-01 |
| Terms last updated | 2026-08-27 | 2026-10-03 |
| Privacy policy last updated | 2026-08-27 | 2026-10-03 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | 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 | 175 stars, 169k npm/wk, 104k PyPI/wk | 809 npm/wk, 376 PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
How the scores have moved
Verdicts
SerpApi
Over 100 engines behind one GET URL, with json_restrictor field selection and output=md. The status page posted an outage across all APIs on 10 September and a degradation of the main Google APIs from 6 October that was still open on 2 November.
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
SerpApi
- Use the MCP with
Authorization: Bearer, not the key-in-path URL the README leads with - Read
serpapi://engines/<engine>before calling a new engine, sinceparamsisn't typed - Add
json_restrictororoutput=mdto cut tokens, andmode: compacton the MCP - A 429 means either the hourly limit or an empty balance. Check the account before retrying
- Repeat a search within the hour and the cached copy is free. Set
no_cache=trueonly when freshness matters
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, SerpApi or SerpKite?
SerpKite scores 70.1 (BB) on agent readiness against SerpApi's 65.3 (B), and leads in 4 of 7 scored categories. SerpApi leads on transparency & trust.
Do SerpApi and SerpKite need an API key?
Both need an API key.
Can an agent call SerpApi and SerpKite without installing anything?
Yes. SerpApi has a hosted endpoint at https://serpapi.com/search and SerpKite at https://api.serpkite.com/v1/search.
Other comparisons with SerpApi or SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs SerpApi
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Arcmira vs SerpApi
- Arcmira vs SerpKite
- Grounding with Bing Search vs SerpApi
- Grounding with Bing Search vs SerpKite
- Brave Search API + MCP vs SerpApi
- Brave Search API + MCP vs SerpKite
- Cloudflare Web Search API vs SerpApi
- Cloudflare Web Search API vs SerpKite
- DeepSeek Search and Fetch API vs SerpApi
- DeepSeek Search and Fetch API vs SerpKite
- Exa API + MCP vs SerpApi
- Exa API + MCP vs SerpKite
- Firecrawl MCP vs SerpApi
- Firecrawl MCP vs SerpKite
- Grep AI vs SerpApi
- Grep AI vs SerpKite
- Hyperresearch vs SerpApi
- Hyperresearch vs SerpKite
- Kagi Search API vs SerpApi
- Kagi Search API vs SerpKite
- Linkup vs SerpApi
- Linkup vs SerpKite
- Mojeek Web Search API vs SerpApi
- Mojeek Web Search API vs SerpKite
- Parallel Search and Task APIs vs SerpApi
- Parallel Search and Task APIs vs SerpKite
- Perplexity Search API vs SerpApi
- Perplexity Search API vs SerpKite
- SearchAPI.io vs SerpApi
- SearchAPI.io vs SerpKite
- SerpApi vs Serper
- SerpApi vs SERPHouse
- SerpApi vs SpecStream
- SerpApi vs Tavily API + MCP
- SerpApi vs TinyFish Search
- SerpApi vs Valyu
- SerpApi vs You.com APIs
- 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 SerpApi
- NewsCatcher vs SerpKite
- Liner Search MCP vs SerpApi
- Liner Search MCP vs SerpKite
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/serpapi-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/serpapi.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare serpapi serpkite(the CLI) - Over MCP
compare_tools {"a": "serpapi", "b": "serpkite"}at/mcp, no key