Head to head · Web search · October 2026 research run
Brave Search API + MCP vs SerpKite
SerpKite scores 70.1 (BB) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 4 of 7 scored categories. Brave Search API + MCP leads on reliability and security & auth. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
Best for Agents that want an independent, non-Google index at a flat price, or that want page text in one call through LLM Context.
Ahead on
- Reliability, 80 against 75
- Security & auth, 58 against 37
Also in its favour
- Runs on your own machine
- Open source
Watch for
The x402 pay-per-call proxy answered 404 on 1 November 2026, and its guide is gone from the docs
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 72
- Agent ergonomics, 97 against 72
- Payments & pricing, 60 against 30
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.
Payments & pricing SerpKite +30
Brave Search API + MCP 30
No machine payment on 1 November. The x402 proxy at search.agent.s.brave.app answers 404 on its root, llms.txt, OpenAPI file and the web search and LLM Context paths it sold on 1 October, the agent payments guide answers 404, and neither llms.txt nor brave.com/search/api mentions x402 (0). $5 per 1,000 searches and $4 per 1,000 Answers requests plus tokens, published without login (20). The $5 monthly credit needs a card on file, which brave.com says is to prevent abuse (0). A person signs up and adds a card before getting a key, so no autonomous route remains (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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.
Agent ergonomics SerpKite +25
Brave Search API + MCP 72
Eight tools, under ten, with --enabled-tools and --disabled-tools to trim the list. Country and language enums make the web search schema long (22). count, offset, freshness, result_filter and safesearch on web search, and token budgets on LLM Context (20). 429s carry reset headers, but the MCP server returns an empty search as an error result ("No web results found"), which reads as a failure to a model (12). Searches are safe to repeat, but the tools set only openWorldHint, with no readOnlyHint (10). Only query is required. No official SDK in any language (8). 22+20+12+10+8 = 72.
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.
Security & auth Brave Search API + MCP +21
Brave Search API + MCP 58
Plain API keys in the X-Subscription-Token header. Several keys per account, revocable from the dashboard, with rotation advice, but no scopes (20). Read-only by nature, with tool allow and deny lists in the MCP server. The HTTP transport binds to 127.0.0.1 and checks Origin (18). Results are untrusted web text and LLM Context returns page content, and we found no prompt-injection guidance in the API docs or the MCP README (0). No per-call audit log found. Rate-limit headers show quota use only (0). SOC 2 Type II attestation, a HackerOne bounty, a pen test in April 2025 and a security.txt at brave.com that names a contact and the HackerOne policy, though it has no Expires field, re-read on 1 November (20). 20+18+0+0+20 = 58.
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).
Schema & documentation SerpKite +18
Brave Search API + MCP 72
No public OpenAPI for the keyed API. The x402 proxy's OpenAPI 3.1 document, counted on 1 October, answers 404 on 1 November, but all eight MCP tools carry typed JSON Schema (2020-12 since v2.1.1), so 20 of 25 stands on the tool schemas. llms.txt at api-dashboard.search.brave.com, linking a Markdown copy of every page (10). Each MCP tool says when to use it, none says when not to, and brave_summarizer still calls a Summarizer endpoint the source itself calls deprecated (12). Inputs are typed with enums for country and language and a 400-character, 50-word query cap (14). Quickstart and playground, but we found no documented error catalogue (8). Dated Api-Version header versions, but no API changelog. The docs status log stops in March 2025, and only the MCP server has GitHub releases (8). 20+10+12+14+8+8 = 72.
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 Brave Search API + MCP +5
Brave Search API + MCP 80
status.brave.app (Better Stack) lists a Brave Search API component monitoring api.search.brave.com, showing 100% uptime with every two-day mark from 6 May to 1 November 2026 operational, and a Search API Dashboard monitor at 99.996%. The 1 October note read the page as unmonitored, but its marks go back to May (20). No incident in the 90 days from 3 August on the page or its feed, and the docs' own status log still ends on 27 March 2025, so a clean record on a readable page (20). Rate limits published per plan, 50 QPS Search, 2 QPS Answers, 100 QPS Spellcheck and Autosuggest, in a 1-second sliding window, per the 1 October check (15). 429 on overrun, X-RateLimit-Reset in seconds and exponential backoff guidance. Searches are reads, so no idempotency keys are needed (15). No SLA on any self-serve plan (0). GA (10). 20+20+15+15+0+10 = 80.
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.
Score by category
| Category | Weight | Brave Search API + MCP | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 75 | Brave Search API + MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 72 | 90 | SerpKite +18 |
| Agent ergonomics | 13% | 72 | 97 | SerpKite +25 |
| Security & auth | 14% | 58 | 37 | Brave Search API + MCP +21 |
| Payments & pricing | 10% | 30 | 60 | SerpKite +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 80 | SerpKite +3 |
| Transparency & trust | 7% | 81 | 77 | Brave Search API + MCP +4 |
| Negative events | ≤15 | -3 | -3 | |
| Total | B 64.1/100 | BB 70.1/100 |
Facts side by side
| Fact | Brave Search API + MCP | SerpKite |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Brave | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | https://api.search.brave.com/res/v1/web/search | https://api.serpkite.com/v1/search |
| Transports | stdio, Streamable HTTP, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Price for web search | $5 per 1,000 requests | not published |
| x402 | no | no |
| Licence | MIT | 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 | 8 | 23 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.brave/brave-search-mcp-server | io.github.SerpKite/serpkite |
| Last release | 2026-09-17 | 2026-11-01 |
| Terms last updated | 2026-09-01 | 2026-10-03 |
| Privacy policy last updated | 2026-08-25 | 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 | 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 | 1.4k stars, 22k npm/wk | 809 npm/wk, 376 PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
How the scores have moved
Verdicts
Brave Search API + MCP
The MCP server's eight tools say when to use each, the status page monitors the Search API with no incident in 90 days, and the self-serve plan costs $5 per 1,000 searches at 50 QPS. Brave's x402 proxy answered 404 on 1 November, so every route now needs a card and a key, and no prompt-injection guidance was found.
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
Brave Search API + MCP
- Call /res/v1/llm/context when you need page text rather than links. It saves a separate fetch
- Treat "No web results found" from the MCP server as an empty result, not an outage
- On 429, wait for
X-RateLimit-Resetseconds. There's noRetry-Afterheader - Skip
brave_summarizer. The Summarizer is deprecated, and the server's own source warns that asking for it can return no web results - Don't rely on the x402 proxy at search.agent.s.brave.app. It answered 404 on 1 November 2026, so use a keyed plan
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, Brave Search API + MCP or SerpKite?
SerpKite scores 70.1 (BB) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 4 of 7 scored categories. Brave Search API + MCP leads on reliability and security & auth.
Do Brave Search API + MCP and SerpKite need an API key?
Brave Search API + MCP takes an API key or an OAuth sign-in. SerpKite needs an API key.
Can an agent call Brave Search API + MCP and SerpKite without installing anything?
Yes. Brave Search API + MCP has a hosted endpoint at https://api.search.brave.com/res/v1/web/search and SerpKite at https://api.serpkite.com/v1/search.
Are Brave Search API + MCP and SerpKite open source?
Brave Search API + MCP is open source (MIT). No open-source release is listed for SerpKite.
Other comparisons with Brave Search API + MCP or SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs Brave Search API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Arcmira vs Brave Search API + MCP
- Arcmira vs SerpKite
- Grounding with Bing Search vs Brave Search API + MCP
- Grounding with Bing Search vs SerpKite
- Brave Search API + MCP vs Cloudflare Web Search API
- Brave Search API + MCP vs DeepSeek Search and Fetch API
- Brave Search API + MCP vs Exa API + MCP
- Brave Search API + MCP vs Firecrawl MCP
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs Kagi Search API
- Brave Search API + MCP vs Linkup
- Brave Search API + MCP vs Mojeek Web Search API
- Brave Search API + MCP vs NewsCatcher
- Brave Search API + MCP vs Parallel Search and Task APIs
- Brave Search API + MCP vs Perplexity Search API
- Brave Search API + MCP vs SearchAPI.io
- Brave Search API + MCP vs SerpApi
- Brave Search API + MCP vs Serper
- Brave Search API + MCP vs SERPHouse
- Brave Search API + MCP vs SpecStream
- Brave Search API + MCP vs Tavily API + MCP
- Brave Search API + MCP vs TinyFish Search
- Brave Search API + MCP vs Valyu
- Brave Search API + MCP vs You.com APIs
- Cloudflare Web Search API vs SerpKite
- DeepSeek Search and Fetch API vs SerpKite
- Exa API + MCP vs SerpKite
- Firecrawl MCP vs SerpKite
- Grep AI vs SerpKite
- Hyperresearch vs SerpKite
- Kagi Search API vs SerpKite
- Linkup vs SerpKite
- Mojeek Web Search API vs SerpKite
- Parallel Search and Task APIs vs SerpKite
- Perplexity Search API vs SerpKite
- SearchAPI.io vs SerpKite
- 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 SerpKite
- Liner Search MCP vs SerpKite
- SERPHouse vs SerpKite
- Brave Search API + MCP vs Grep AI
Machine-readable
- This page as Markdown
/compare/brave-search-mcp-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/brave-search-mcp.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare brave-search-mcp serpkite(the CLI) - Over MCP
compare_tools {"a": "brave-search-mcp", "b": "serpkite"}at/mcp, no key