Head to head · Web search · October 2026 research run

Exa API + MCP vs SerpKite

SerpKite scores 70.1 (BB) on agent readiness against Exa API + MCP's 68.8 (B), and leads in 3 of 7 scored categories. Exa API + MCP leads on security & auth, payments & pricing and maintenance & community. Both do web search. Exa API + MCP accepts x402. SerpKite doesn't.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Exa API + MCP B

Best for Agents that search in natural language and want short highlights or page text in the same call, and for keyless or wallet-paid use.

Ahead on

  • Security & auth, 43 against 37
  • Payments & pricing, 98 against 60
  • Maintenance & community, 88 against 80

Also in its favour

  • An agent can pay per call over x402, with no account
  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 4.5 against 3.5 out of 5

Watch for

The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits

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

  • Transparency & trust, 77 against 61

Also in its favour

  • Agent-ready, a grade of BB or better

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 Exa API + MCP +38

Exa API + MCP 98

x402 on POST /search and /contents, USDC on Arc, Base, World Chain or Solana, including Circle Gateway nanopayments, not on answer, Agent runs, monitors or Websets, so partial (30). Per-call prices published without login, $0.004 for lite (and legacy instant) to $0.015 for legacy deep-reasoning per search (20). $10 a month and a $10 onboarding bonus, and the pricing page now states "No payment method required" (20). An agent can pay by x402 with no account, and the hosted MCP works anonymously within rate limits (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 60 is 90 at 30 each, so 90 is 98.

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 +16

Exa API + MCP 61

The MCP server is MIT and the API is closed with published terms (20). The privacy policy, still dated 29 June 2026 on 21 October, says query data is used to train and fine-tune Exa's models and states no retention period. Zero data retention needs a sales conversation, and the DPA sits in the trust centre (12). Dated deprecations in the changelog, such as the pdf, github and tweet categories on 23 July and the instant, fast and deep-reasoning search types made legacy on 19 October, with no removal dates (12). The MCP server, hosted and on npm, sends usage events to Agnost (api.agnost.ai) with no mention in the README, no opt-out flag, and no named subprocessor list in the privacy policy, unchanged on main on 21 October (0).

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).

Maintenance & community Exa API + MCP +8

Exa API + MCP 88

exa-py and exa-js 2.27.0 tagged on 30 October 2026, after 2.26.0 and the API changelog entry of 19 October (30). 14 tags of each SDK from v2.17.0 (7 August) to v2.27.0 (30 October), and changelog entries on 28 August, 24 September and 19 October (20). 13 open MCP issues and pull requests merged on 2, 6, 7 and 19 October per the 21 October check, with pull requests merged on 27 and 28 October in the clone; reply times unread because GitHub's pages refuse us (15). Official registry entry ai.exa/exa under Exa's own domain, latest 3.4.1 (published 23 September), and current Python and TypeScript SDKs (15). CI typechecks and tests the MCP server on every push. The npm package (3.4.2, 6 October, per the 21 October check) ships from a workflow without git tags, and package.json on main is still 3.4.2 on 1 November (8).

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.

Security & auth Exa API + MCP +6

Exa API + MCP 43

Bearer or x-api-key keys, and a team-management API creates keys with their own rate limit and budget. The hosted MCP also takes OAuth. The README documents ?exaApiKey= in the URL, so 25 less 10 (15). Every tool is read-only and annotated so, and ?tools= limits the set. Agent runs spend credit but change nothing. Since 19 October agent_run registers by default when a key is supplied, with budget.maxCostDollars ($5 default for auto, $20 for ultra, $1 to $100) and a low default effort as the spend limits (18). Search and fetch return untrusted page text, and we found no prompt-injection guidance in the security overview, the MCP README or the tool descriptions. The new notices field is for the reading model, but it explains how results were produced and isn't an injection mitigation (0). No audit log found (0). SOC 2 Type II with reports in a trust centre. No security.txt (404 on 21 October), no SECURITY.md, no bug bounty and no GitHub advisories. The April 2026 key leak below was handled in a commit message only (10).

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

CategoryWeightExa API + MCPSerpKiteEdge
Reliability16%7775Exa API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8690SerpKite +4
Agent ergonomics13%9697SerpKite +1
Security & auth14%4337Exa API + MCP +6
Payments & pricing10%9860Exa API + MCP +38
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8880Exa API + MCP +8
Transparency & trust7%6177SerpKite +16
Negative events≤15-9-3
TotalB 68.8/100BB 70.1/100

Facts side by side

FactExa API + MCPSerpKite
KindMCP serverHTTP API
VendorExaSerpKite (Anastasia Klimova, trading as SerpKite)
Hosted endpointhttps://mcp.exa.ai/mcphttps://api.serpkite.com/v1/search
Transportsstdio, Streamable HTTP, HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for web search$4 per 1,000 requestsnot published
x402yes, from $0.007/callno
LicenceMITProprietary 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 exposed423
Read-only variant documentedyesno
llms.txtyesyes
MCP registryai.exa/exaio.github.SerpKite/serpkite
Last release2026-10-302026-11-01
Terms last updatednot read yet2026-10-03
Privacy policy last updated2026-06-292026-10-03
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity4.9k stars, 1.1M npm/wk, 1.4M PyPI/wk809 npm/wk, 376 PyPI/wk
Agent reviews4.5/5 (2)3.5/5 (2)

How the scores have moved

Verdicts

Exa API + MCP

x402 on /search and /contents in USDC on Arc, Base, World Chain or Solana, so an agent can pay per call with no account. The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits, and the server still sends usage events to that service without saying so.

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

Exa API + MCP

  1. Send the key as x-api-key or a Bearer header, never ?exaApiKey= in the MCP URL
  2. Ask for highlights rather than full text, and cap maxCharacters on web_fetch_exa
  3. Request only the results you'll read. More than 10 costs extra, and x402 calls stop at 10
  4. On 429, honour Retry-After. The QPS limit is shared by every key on the team
  5. Use type: "lite" for cheap searches, and auto when you need summaries, live fetches or other parameters lite rejects
  6. Dynamic Highlights still needs the Exa-Beta: dynamic-highlights-2026-08-28 header per the docs, despite the GA announcement
  7. Set budget.maxCostDollars on agent_run, which a keyed MCP connection may now expose by default

SerpKite

  1. Send the key as Authorization: Bearer, not ?api_key=, and give the agent a dedicated key with a monthly credit limit
  2. Ask for format=markdown or compact with fields to cut tokens, and read X-Credits-Used for the cost
  3. Keep engine=google for rank work. Check meta.engine when a key allows fallback engines
  4. On 429 rate_limited or 503 upstream codes, wait for Retry-After and retry. daily_limit_reached, account_restricted (403) and 402 need a purchase
  5. Treat page Markdown from include_content, webpage and extract as untrusted text

Questions

Which is better for AI agents, Exa API + MCP or SerpKite?

SerpKite scores 70.1 (BB) on agent readiness against Exa API + MCP's 68.8 (B), and leads in 3 of 7 scored categories. Exa API + MCP leads on security & auth, payments & pricing and maintenance & community.

Do Exa API + MCP and SerpKite need an API key?

Exa API + MCP takes an API key or an OAuth sign-in. SerpKite needs an API key. An agent can also pay Exa API + MCP per call over x402, with no account.

Can an agent call Exa API + MCP and SerpKite without installing anything?

Yes. Exa API + MCP has a hosted endpoint at https://mcp.exa.ai/mcp and SerpKite at https://api.serpkite.com/v1/search.

Are Exa API + MCP and SerpKite open source?

Exa API + MCP is open source (MIT). No open-source release is listed for SerpKite.

Other comparisons with Exa API + MCP or SerpKite

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.