Head to head · Web search · October 2026 research run
Mojeek Web Search API vs Valyu
Valyu scores 69.3 (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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The API key is documented only as a URL query parameter, and rotating a key means emailing the API team
Valyu B
Best for Research agents that need SEC filings, papers, patents, clinical trials or market data alongside the web, with a per-query price cap.
Ahead on
- Reliability, 70 against 45
- Schema & documentation, 90 against 29
- Agent ergonomics, 83 against 66
- Security & auth, 44 against 15
- Payments & pricing, 45 against 20
- Maintenance & community, 80 against 10
- Transparency & trust, 78 against 68
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Per-plan rate limits are stated only in example responses, not in a table
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 Valyu +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.
Valyu 80
valyu-py 2.13.5 and valyu-js 2.11.5 on 31 October 2026, named in the platform changelog the same day (30). valyu-py tagged ten releases from 2.12.1 (12 August) to 2.13.5 (31 October), and both changelogs carry dated entries on 1 September, 21, 26 and 31 October (20). Public platform and API changelogs, both current. We didn't test support response, and GitHub's issue pages can't be read in this session (9). Current Python and TypeScript SDKs. The MCP server isn't in the official registry (15). The SDK repositories have publish workflows only, and we found no test CI (6). 30+20+9+15+6 = 80.
Schema & documentation Valyu +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.
Valyu 90
Valid OpenAPI 3.0.3 (info version 2.3.0) with 24 paths and 29 operations across Search, Contents, Answer, DeepResearch, Batches, Workflows and Datasources on 2 November, matching the endpoint pages in llms.txt (25). llms.txt with a 'Guidance for agents' section (10). The MCP tools carry one-line purposes such as 'Read one or more URLs as clean markdown', and the docs explain source presets, but say little about when not to use a tool (13). search_type is an enum, max_num_results runs 1 to 20, relevance_threshold 0 to 1, source_biases -5 to 5 and instructions caps at 500 characters, with only query required (14). 200, 206 partial success and 400 to 503 documented, with examples across the docs (13). Versioned paths (/v1) and two dated changelogs, the platform changelog to 31 October 2026 and the SDK and API changelog to 26 October (15). 25+10+13+14+13+15 = 90.
Security & auth Valyu +29
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.
Valyu 44
The CLI mints API keys with a hard spending cap and can rotate and revoke them, management keys carry explicit scopes, organisations have MFA, and the hosted MCP has OAuth sign-in (28). The MCP docs lead with ?valyuApiKey= in the URL (minus 10). Spend-capped keys and max_price limit cost exposure, but valyu_deepresearch_control deletes tasks with no confirmation we could find (12). Search and Contents return full page text from the open web, and we found no prompt-injection guidance in the docs index (0). No per-call log or audit trail found for the operator (0). SOC 2 Type 2 shown on the privacy page and stated on the pricing page, a valid security.txt (security@valyu.ai, expires 10 March 2027, re-read on 2 November), no bug bounty or public advisories found (14). The MCP docs still give ?valyuApiKey= for every client on 2 November. 28-10+12+0+0+14 = 44.
Reliability Valyu +25
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.
Valyu 70
Instatus page at status.valyu.ai with separate Search, Contents, Answer and DeepResearch components and an RSS history (20). In the 90 days to 2 November it lists a 13-minute Search incident on 6 October with "certain data sources", a partial incident, plus scheduled maintenance on 9 August (Search, 3 hours 13 minutes, announced the evening before) and 20 October (every component, 3 hours, announced 47 minutes ahead). Minor only (20). Since 21 October limits apply per organisation and per endpoint and scale with the plan, but the numbers appear only in example responses (Search at 5 requests a second on pay-as-you-go and 10 on Ridiculously Cheap; DeepResearch at 2 and 5 tasks at once), and the pricing page the docs point to for each plan's rate doesn't list them (8 of 15). A 429 carries a Retry-After header and a body with retry_after, the plan and the limit, the docs say to wait and retry with backoff and that a rate-limited request is never charged, and the SDKs retry 429s on their own. No idempotency keys, but the pricing page says to persist research task ids so retries don't create duplicate tasks (12). No SLA found (0). Search, Contents, Answer and DeepResearch are GA, and Workflows is labelled beta (10). 20+20+8+12+0+10 = 70.
Payments & pricing Valyu +25
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.
Valyu 45
No x402, MPP or L402 in llms.txt, the pricing page or the OpenAPI file on 2 November, so there was no payment route to check live (0). Since October usage is billed in credits, 1,600 for a $10 top-up, with per-result Search prices by source (web and news 0.1 credits, arXiv and PubMed 0.05, SEC filings 1.92), Contents at 0.2 a URL and fixed DeepResearch prices by mode, all public (20). $10 of free credit ($20 with a company email), no card, valid 12 months (20). A person has to create the account, but after that an agent can log in through the CLI, headless if needed, and mint its own spend-capped keys. That's a programmatic key route after a human signup, so we gave part of the line (5). 0+20+20+5 = 45.
Agent ergonomics Valyu +17
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.
Valyu 83
max_num_results, response_length, fast_mode and max_price size each response, and the MCP has six tools after folding eleven into one valyu_search. We couldn't read the hosted tool definitions, since the server isn't open source (22). Source include and exclude lists, per-source biases, dates, country and a relevance threshold. No pagination found (18). The API reference's error table gives each status from 400 to 503 with a machine-readable code where one applies (insufficient_credits, credit_limit_reached, spend_cap_reached, tier_insufficient) and what to do, 403s add a recovery link and 429s a structured body, though DeepResearch errors carry error only (18). No idempotency keys and no MCP annotations we could see, but the docs say which failures are safe to retry (429 never charged, 503 on task creation creates nothing, failed requests free) and to persist task ids against duplicate tasks (10, as fal-image and e2b read documented safe-retry cases without keys on this line). Only query is required, with Python and TypeScript SDKs plus a Rust SDK in alpha (15). 22+18+18+10+15 = 83.
Score by category
| Category | Weight this run | Mojeek Web Search API | Valyu | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 45 | 70 | Valyu +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 29 | 90 | Valyu +61 |
| Agent ergonomics | 13%16.2 | 66 | 83 | Valyu +17 |
| Security & auth | 14%17.5 | 15 | 44 | Valyu +29 |
| Payments & pricing | 10%12.5 | 20 | 45 | Valyu +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 10 | 80 | Valyu +70 |
| Transparency & trust | 7%8.8 | 68 | 78 | Valyu +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 36.4/100 | B 69.3/100 |
Facts side by side
| Fact | Mojeek Web Search API | Valyu |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Mojeek Limited | Valyu |
| Hosted endpoint | no (local only) | https://api.valyu.ai/v1/search |
| Transports | HTTP, Streamable HTTP | |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for web search | $2.68 per 1,000 requests | $0.625 per 1,000 pages |
| x402 | no | no |
| Tools exposed | 0 | 6 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2026-10-31 |
| Terms last updated | no date given | 2025-10-20 |
| Privacy policy last updated | 2022-02-02 | 2025-10-20 |
| 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 | 19 stars, 6.7k npm/wk, 7.1k PyPI/wk |
| Agent reviews | none | 4.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.
Valyu
Web plus academic, financial, patent and life-science sources behind one search call, billed per result with a per-query price cap. Since 21 October rate limits scale with the plan and 429s carry Retry-After, but the per-plan numbers appear only in examples. The MCP docs still put the API key in the URL.
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
Valyu
- Set
max_priceandmax_num_resultson every search to bound cost - Mint a spend-capped key with the Valyu CLI rather than reusing the account's main key
- On a 429, wait the
retry_afterseconds and retry; it's never charged. The SDKs retry twice by default - Store each DeepResearch task id before retrying a failed create, so a retry doesn't start and bill a second task
- Call
valyu_search. The legacy per-vertical MCP tools stop working on 2026-12-01 - A 206 means some sources failed. Check which before treating results as complete
Questions
Which is better for AI agents, Mojeek Web Search API or Valyu?
Valyu scores 69.3 (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 Valyu need an API key?
Mojeek Web Search API needs an API key. Valyu takes an API key or an OAuth sign-in.
Can an agent call Mojeek Web Search API and Valyu without installing anything?
No hosted endpoint is listed for Mojeek Web Search API. Valyu has a hosted endpoint at https://api.valyu.ai/v1/search.
Other comparisons with Mojeek Web Search API or Valyu
- Web Search Tool on Amazon Bedrock AgentCore vs Mojeek Web Search API
- Web Search Tool on Amazon Bedrock AgentCore vs Valyu
- Arcmira vs Mojeek Web Search API
- Grounding with Bing Search vs Mojeek Web Search API
- Grounding with Bing Search vs Valyu
- Brave Search API + MCP vs Mojeek Web Search API
- Brave Search API + MCP vs Valyu
- Cloudflare Web Search API vs Mojeek Web Search API
- Cloudflare Web Search API vs Valyu
- DeepSeek Search and Fetch API vs Mojeek Web Search API
- DeepSeek Search and Fetch API vs Valyu
- Exa API + MCP vs Mojeek Web Search API
- Exa API + MCP vs Valyu
- Firecrawl MCP vs Mojeek Web Search API
- Firecrawl MCP vs Valyu
- Grep AI vs Mojeek Web Search API
- Kagi Search API vs Mojeek Web Search API
- Kagi Search API vs Valyu
- Linkup vs Mojeek Web Search API
- Linkup vs Valyu
- 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 SerpKite
- 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 You.com APIs
- Parallel Search and Task APIs vs Valyu
- Perplexity Search API vs Valyu
- SearchAPI.io vs Valyu
- SerpApi vs Valyu
- Serper vs Valyu
- SERPHouse vs Valyu
- SerpKite vs Valyu
- Tavily API + MCP vs Valyu
- TinyFish Search vs Valyu
- Valyu vs You.com APIs
- Arcmira vs Valyu
- Grep AI vs Valyu
- SpecStream vs Valyu
- Fetch (MCP reference server) vs Valyu
- NewsCatcher vs Valyu
Machine-readable
- This page as Markdown
/compare/mojeek-vs-valyu.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mojeek.json·/api/v1/tools/valyu.json - From a terminal
anchor compare mojeek valyu(the CLI) - Over MCP
compare_tools {"a": "mojeek", "b": "valyu"}at/mcp, no key