Head to head · Web search · October 2026 research run
Mojeek Web Search API vs SerpKite
SerpKite scores 67.6 (B) on agent readiness against Mojeek Web Search API's 36.4 (F), and leads in every scored category. Both do web search.
Best web search APIs for AI agents · All 308 search comparisons
Which one, for what
Best for Agents and products that want a second, independent index beside Google-derived results, or European data handling with no sub-processors.
Also in its favour
- No incidents deducted, where SerpKite loses 3 points for them
Watch for
The API key is documented only as a URL query parameter, and rotating a key means emailing the API team
SerpKite B
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 45
- Schema & documentation, 90 against 29
- Agent ergonomics, 97 against 66
- Security & auth, 37 against 15
- Payments & pricing, 40 against 20
- Maintenance & community, 80 against 10
- Transparency & trust, 77 against 68
Also in its favour
- A hosted endpoint, with nothing to install
- 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.
Maintenance & community SerpKite +70
Mojeek Web Search API 10
Read for a closed service. No API changelog, release notes or dated API change were found, and the blog's posts since 2024 are about search in general, so the last change can't be dated (0). No dated changes in the 90 days from 8 August (0). A staff member answered API questions on the community forum within a day in December 2025 and October 2026, and support is by email; no public changelog (10 of 15). No official SDKs or MCP server (0). No public packages or CI to measure (0). 0 + 0 + 10 + 0 + 0 = 10.
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.
Schema & documentation SerpKite +61
Mojeek Web Search API 29
No OpenAPI or other machine-readable contract (0). No llms.txt (404) and no Markdown pages for agents (0). The parameters page states what each parameter does, with notes on when not to use reg and clufmt, but nothing on when another endpoint fits better (12 of 20). Every parameter has a type, defaults and valid ranges (tlen 0 to 127, dlen 0 to 511, rbb and lbb 1 to 100, up to 25 domains), though reg is called an enum without listing its values (11 of 15). One curl example and annotated JSON and XML response formats; errors appear only as a status string with one example (6 of 15). No API version, changelog or dated release notes, and the quickstart and the parameters page give different hosts (0). 0 + 0 + 12 + 11 + 6 + 0 = 29.
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).
Agent ergonomics SerpKite +31
Mojeek Web Search API 66
Responses can be sized with t (up to 10, 40 or 100 results by plan), tlen, dlen and opt-in date and size fields (22 of 25). s for paging, since and before, site, included and excluded domains, region and language boosting and safe search (20). Errors are a free-text status with no documented codes, which an agent can't branch on reliably (5 of 20). Searches only read, so a retry is safe, but no page says whether failed or empty requests are billed (12 of 20). Only q and api_key are required, with recommended values for the boosts. No official SDK in any language (7 of 15). 22 + 20 + 5 + 12 + 7 = 66.
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 +30
Mojeek Web Search API 45
Read with the hosted lines. status.mojeek.com is a Site24x7 StatusIQ page with Search, Website, Blog and Community components. It is drawn by script, so only its RSS feed could be read, which shows each component's current state (Search operational since 7 September 2026) and no incident entries (15 of 20). No readable incident history (5). Rate limits are published per plan, 5 a second and 100,000 a day on Startup, 10 a second and 400,000 a day on Business (15). Over the daily limit the JSON status reads 'ERROR: Daily Limit Reached'; no HTTP 429, Retry-After or backoff guidance was found (0). No SLA, and the API terms say the service is provided as is and may be interrupted without notice (0). Generally available, with only the lr parameter marked beta (10). 15 + 5 + 15 + 0 + 0 + 10 = 45.
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.
Security & auth SerpKite +22
Mojeek Web Search API 15
One key per account, documented only as the api_key query parameter, and rotation or revocation is by email to the API team (a staff reply of 22 October 2026 on the community forum asks for the key's last 8 digits). One all-powerful key (10) less 10 for the key in the URL (0). Search is read-only and there is nothing to write, but no scoped or restricted key (10 of 20). Results are third-party titles and snippets, with no prompt-injection guidance found (0). No audit log or per-call usage view was found in the docs; the FAQ mentions budget alerts on the account (0 of 15). security.txt names security@mojeek.com, with no Expires field. No bug bounty, disclosure policy, SOC 2 or ISO 27001 found; the API page claims compliance with European rules such as the EU Data Act without a certification (5 of 20). 0 + 10 + 0 + 0 + 5 = 15.
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).
Payments & pricing SerpKite +20
Mojeek Web Search API 20
No x402, MPP or L402 (0). Per-request prices published without login, £2 and £3 per 1,000 requests (20). The FAQ says a free credit comes with the Startup plan, but a bank card is required to open an account (0). A person signs up in a browser and adds a card (0). 0 + 20 + 0 + 0 = 20.
SerpKite 40
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).
Score by category
| Category | Weight this run | Mojeek Web Search API | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 45 | 75 | SerpKite +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 29 | 90 | SerpKite +61 |
| Agent ergonomics | 13%16.2 | 66 | 97 | SerpKite +31 |
| Security & auth | 14%17.5 | 15 | 37 | SerpKite +22 |
| Payments & pricing | 10%12.5 | 20 | 40 | SerpKite +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 10 | 80 | SerpKite +70 |
| Transparency & trust | 7%8.8 | 68 | 77 | SerpKite +9 |
| Negative events | ≤15 | 0 | -3 | |
| Total | F 36.4/100 | B 67.6/100 |
Facts side by side
| Fact | Mojeek Web Search API | SerpKite |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Mojeek Limited | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | no (local only) | https://api.serpkite.com/v1/search |
| Transports | HTTP, Streamable HTTP | |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| Price for web search | $2.68 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 | 0 | 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 | no date given | 2026-10-03 |
| Privacy policy last updated | 2022-02-02 | 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 | none | 3.5/5 (2) |
How the scores have moved
Mojeek Web Search API
No score change since it was listed.
Verdicts
Mojeek Web Search API
Mojeek sells search over its own independent index at published per-request prices, with region, language, date and domain controls and storage rights on the Business plan. The key travels only in the URL, rotation is by email, a card is needed to start, and there is no OpenAPI, changelog, 429 handling or SLA.
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
Mojeek Web Search API
- Send
fmt=json, since the default response is XML - Read
response.statuson every call; a daily limit shows as 'ERROR: Daily Limit Reached' rather than an HTTP error - Set
lb,lbb,rbandrbbas the quickstart recommends, or results lean to no language or region - Keep the key out of logs and shared URLs, since it travels in the query string
- On the Startup plan, don't keep results for more than an hour
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, Mojeek Web Search API or SerpKite?
SerpKite scores 67.6 (B) on agent readiness against Mojeek Web Search API's 36.4 (F), and leads in every scored category.
Do Mojeek Web Search API and SerpKite need an API key?
Both need an API key.
Can an agent call Mojeek Web Search API and SerpKite without installing anything?
No hosted endpoint is listed for Mojeek Web Search API. SerpKite has a hosted endpoint at https://api.serpkite.com/v1/search.
Other comparisons with Mojeek Web Search API or SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs Mojeek Web Search API
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Arcmira vs Mojeek Web Search API
- Arcmira vs SerpKite
- Grounding with Bing Search vs Mojeek Web Search API
- Grounding with Bing Search vs SerpKite
- Brave Search API + MCP vs Mojeek Web Search API
- Brave Search API + MCP vs SerpKite
- Cloudflare Web Search API vs Mojeek Web Search API
- Cloudflare Web Search API vs SerpKite
- DeepSeek Search and Fetch API vs Mojeek Web Search API
- DeepSeek Search and Fetch API vs SerpKite
- Exa API + MCP vs Mojeek Web Search API
- Exa API + MCP vs SerpKite
- Firecrawl MCP vs Mojeek Web Search API
- Firecrawl MCP vs SerpKite
- Grep AI vs Mojeek Web Search API
- Grep AI vs SerpKite
- Kagi Search API vs Mojeek Web Search API
- Kagi Search API vs SerpKite
- Linkup vs Mojeek Web Search API
- Linkup vs SerpKite
- Mojeek Web Search API vs NewsCatcher
- Mojeek Web Search API vs Parallel Search and Task APIs
- Mojeek Web Search API vs Perplexity Search API
- Mojeek Web Search API vs SearchAPI.io
- Mojeek Web Search API vs SerpApi
- Mojeek Web Search API vs Serper
- Mojeek Web Search API vs SERPHouse
- Mojeek Web Search API vs SpecStream
- Mojeek Web Search API vs Tavily API + MCP
- Mojeek Web Search API vs TinyFish Search
- Mojeek Web Search API vs Valyu
- Mojeek Web Search API vs You.com APIs
- 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
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/mojeek-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mojeek.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare mojeek serpkite(the CLI) - Over MCP
compare_tools {"a": "mojeek", "b": "serpkite"}at/mcp, no key