Head to head · Web search · October 2026 research run
Serper vs SerpKite
SerpKite scores 70.1 (BB) on agent readiness against Serper's 11.7 (F), and leads in 6 of 7 scored categories. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
Serper F
Best for High-volume Google SERP lookups on a tight budget where the agent already has a fetcher.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No status page, SLA or incident history
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 30
- Schema & documentation, 90 against 6
- Agent ergonomics, 97 against 35
- Security & auth, 37 against 20
- Maintenance & community, 80 against 3
- Transparency & trust, 77 against 32
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.5 against 2.5 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.
Schema & documentation SerpKite +84
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).
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).
Maintenance & community SerpKite +77
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).
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 +62
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).
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.
Reliability SerpKite +45
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).
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.
Transparency & trust SerpKite +45
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).
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).
Security & auth SerpKite +17
Serper 20
API key in the X-API-KEY header, never in the URL. No scopes, multiple keys or rotation found (10). Read-only search with no write surface, but no MCP annotations or least-privilege mode (10). Returns third-party titles and snippets with no prompt-injection guidance (0). No per-call log or audit trail found outside the logged-in dashboard, which we couldn't see (0). serper.dev/.well-known/security.txt returned 404 on 11 November, and we found no disclosure policy, bug bounty or certification (0).
SerpKite 37
Many keys per account, each revocable and rotatable with an optional monthly credit limit, stored as SHA-256 hashes, with no scopes. Since 9 October the MCP server also takes OAuth (authorisation code with PKCE, dynamic client registration, rotating refresh tokens, one mcp scope), each connection running as a named, revocable API key, while REST still needs a key (20). The docs allow the key as ?api_key= on GET requests (minus 10). Search is read-only, and per-key limits and an account spend cap bound cost, but there's no read-only key, and the MCP server exposes crawl alongside search with no confirmation step we could see (10). Results include third-party snippets and full page Markdown, and we found no prompt-injection guidance (0). The dashboard request log keeps per-call metadata (endpoint, status, credits, key) for 31 days with CSV export, and each key records who created it (12). security.txt returns 404. The security page has a disclosure policy with acknowledgement in 2 business days, no paid bug bounty and SOC 2 marked as not yet started (5).
Score by category
| Category | Weight | Serper | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16% | 30 | 75 | SerpKite +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 6 | 90 | SerpKite +84 |
| Agent ergonomics | 13% | 35 | 97 | SerpKite +62 |
| Security & auth | 14% | 20 | 37 | SerpKite +17 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 3 | 80 | SerpKite +77 |
| Transparency & trust | 7% | 32 | 77 | SerpKite +45 |
| Negative events | ≤15 | -15 | -3 | |
| Total | F 11.7/100 | BB 70.1/100 |
Facts side by side
| Fact | Serper | SerpKite |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Serper | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | https://google.serper.dev/search | https://api.serpkite.com/v1/search |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| 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 | not listed | io.github.SerpKite/serpkite |
| Last release | none | 2026-11-01 |
| Terms last updated | 2024-05-29 | 2026-10-03 |
| Privacy policy last updated | 2025-11-05 | 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 | none | 809 npm/wk, 376 PyPI/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
How the scores have moved
Verdicts
Serper
$0.30 to $1.00 per 1,000 queries on prepaid packs, with no subscription. No status page, SLA or incident history.
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
Serper
- POST JSON with
qto the vertical you need (/search,/news,/images,/scholar) with the key inX-API-KEY - Set
glandhl, since Google results vary by country and language - Pair it with a fetcher. Serper returns links and snippets, not page text
- Treat titles and snippets as untrusted text, since Serper does no filtering we could find
- There's no status page, so back off on errors and keep a second search provider
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, Serper or SerpKite?
SerpKite scores 70.1 (BB) on agent readiness against Serper's 11.7 (F), and leads in 6 of 7 scored categories.
Do Serper and SerpKite need an API key?
Both need an API key.
Can an agent call Serper and SerpKite without installing anything?
Yes. Serper has a hosted endpoint at https://google.serper.dev/search and SerpKite at https://api.serpkite.com/v1/search.
Other comparisons with Serper or SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs Serper
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Arcmira vs Serper
- Arcmira vs SerpKite
- Grounding with Bing Search vs Serper
- Grounding with Bing Search vs SerpKite
- Brave Search API + MCP vs Serper
- Brave Search API + MCP vs SerpKite
- Cloudflare Web Search API vs Serper
- Cloudflare Web Search API vs SerpKite
- DeepSeek Search and Fetch API vs Serper
- DeepSeek Search and Fetch API vs SerpKite
- Exa API + MCP vs Serper
- Exa API + MCP vs SerpKite
- Firecrawl MCP vs Serper
- Firecrawl MCP vs SerpKite
- Grep AI vs Serper
- Grep AI vs SerpKite
- Hyperresearch vs Serper
- Hyperresearch vs SerpKite
- Kagi Search API vs Serper
- Kagi Search API vs SerpKite
- Linkup vs Serper
- Linkup vs SerpKite
- Mojeek Web Search API vs Serper
- Mojeek Web Search API vs SerpKite
- Parallel Search and Task APIs vs Serper
- Parallel Search and Task APIs vs SerpKite
- Perplexity Search API vs Serper
- Perplexity Search API vs SerpKite
- SearchAPI.io vs Serper
- SearchAPI.io vs SerpKite
- SerpApi vs Serper
- SerpApi vs SerpKite
- Serper vs SERPHouse
- Serper vs SpecStream
- Serper vs Tavily API + MCP
- Serper vs TinyFish Search
- Serper vs Valyu
- Serper vs You.com APIs
- 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 Serper
- NewsCatcher vs SerpKite
- Liner Search MCP vs Serper
- Liner Search MCP vs SerpKite
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/serper-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/serper.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare serper serpkite(the CLI) - Over MCP
compare_tools {"a": "serper", "b": "serpkite"}at/mcp, no key