{ "data": { "a": { "slug": "deepseek-search-api", "name": "DeepSeek Search and Fetch API", "vendor": "DeepSeek", "vendorUrl": "https://www.deepseek.com", "kind": "http-api", "category": "search", "summary": "DeepSeek's Search and Fetch API gives agents live web results from DeepSeek's in-house search engine and single pages as Markdown, through two REST endpoints on an ordinary DeepSeek API key, billed per successful request.", "url": "https://www.anchorterminal.com/tools/deepseek-search-api", "markdownUrl": "https://www.anchorterminal.com/tools/deepseek-search-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/deepseek-search-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json", "dns": "deepseek-search-api.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.deepseek.com/v1/tools/search", "packages": [], "auth": "api-key", "authNotes": "The same DeepSeek API key as the model endpoints, sent as a bearer token. Keys carry no scopes, so a search key can also spend the balance on models. Rate limits are per account, whichever key is used.", "pricing": "usage", "pricingNotes": "$0.75 per 1,000 successful requests for Search and the same for Fetch, from a prepaid balance. Only an HTTP 200 with a result is billed, and `count` doesn't change the price. Server-side search through DeepSeek Harness, Claude Code or Codex was free until 31 October 2026 at 16:00 UTC (https://api-docs.deepseek.com/guides/search, checked 2026-10-17; DeepSeek's pages weren't re-read on 2026-11-04 because its Terms of Use bar automated copying).", "priceSummary": "$0.75 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Search and Fetch guide, the API reference or the pricing page (checked 2026-10-17).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-17" }, "docsUrl": "https://api-docs.deepseek.com/guides/search", "capabilities": [ "web.search", "web.fetch" ], "tags": [ "hosted", "prepaid", "usage-priced", "status-page" ], "lastRelease": "2026-10-17", "graded": true, "anchor": { "graded": true, "score": 55.5, "grade": "C", "agentReady": false, "rank": 866, "ranked": true, "rankOf": 1510, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 81, "maintenance": 42, "payments": 20, "reliability": 72, "schema": 55, "security": 43, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": 0, "verdict": "Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training.", "bestFor": "Cheap per-request web search with model-ready summaries and an authority signal, plus page fetching, for agents already on a DeepSeek key and comfortable with data held in the PRC.", "strengths": [ "$0.75 per 1,000 successful requests for each endpoint, and failed calls, empty results and timeouts aren't billed", "Each result has a 100 to 200 character snippet, a 600 to 800 character summary for models, and full text on request", "Site, language, date and phrase operators in the query string, and up to 50 results a call", "Error table with ten status codes and when to retry, and both endpoints documented as read-only" ], "weaknesses": [ "Opened on 17 October 2026, with no service record of its own and no component for it on the status page", "5 requests a second per account for each endpoint, plus an unpublished per-domain limit on Fetch", "No OpenAPI file, no llms.txt, no official SDKs and no free tier for direct calls", "One unscoped key for search and models, no security.txt, and no prompt-injection guidance for returned page text", "Data stored in the PRC, used for training unless the customer opts out by email, and no retention period stated" ], "agentNotes": [ "Keep `query` to 128 characters and put filters in it as operators, such as `site:github.com lang:en after:2026-01-01`", "Leave `need_content` false and read `summary` first, then call Fetch on the URLs you keep", "Stay under 5 requests a second per account across all keys. On 408, 429 or 5xx wait and retry, since no Retry-After is documented", "Don't retry a Fetch 403 or 404 unchanged. The page is blocked by policy, unreachable or has no Markdown", "Don't send private queries or an end user's IP in `localization`. Data is stored in the PRC" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.5 } ], "editorialScores": { "ergonomics": 81, "maintenance": 42, "payments": 20, "reliability": 72, "schema": 55, "security": 43, "transparency": 35 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.deepseek.com/v1/tools/search \\\n -H \"Authorization: Bearer $DEEPSEEK_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"query\":\"DeepSeek V4 release\",\"count\":5,\"need_content\":true}'" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/deepseek-search-api" }, "sameCompany": [ "deepseek-api", "deepseek-v4-1-flash", "deepseek-v3-2", "deepseek-v4-flash-0731" ], "area": "web-data", "unitPrices": [ { "item": "Search", "unit": "1k-requests", "usd": 0.75, "note": "Successful non-empty results only. 1 to 50 results at the same price" }, { "item": "Fetch", "unit": "1k-pages", "usd": 0.75, "note": "One URL per request, billed only when page content comes back" } ], "provenance": { "legalEntity": "Hangzhou DeepSeek Artificial Intelligence Co., Ltd.", "domain": "deepseek.com", "domainRegistered": "2000-08-13", "endpointOnVendorDomain": true, "terms": "https://cdn.deepseek.com/policies/en-US/deepseek-open-platform-terms-of-service.html", "privacy": "https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html", "statusPage": "https://status.deepseek.com", "changelog": "https://api-docs.deepseek.com/updates", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "deepseek.com was registered in 2000, long before the company, so domain age flatters it (per the deepseek-api listing).", "The Open Platform terms (released 22 April, effective 29 April 2026) are a Specific Agreement under the DeepSeek Terms of Use (last update 27 March 2026), both re-read on 4 November 2026. They are governed by PRC law and assign Outputs to the customer. The Terms of Use §3.5(3) bar \"capturing, copying any content of the Services, including but not limited to using any robots, spiders, or other automatic setups, setting mirrors\". The privacy policy (10 February 2026) names Hangzhou DeepSeek Artificial Intelligence Co., Ltd.", "www.deepseek.com/.well-known/security.txt and deepseek.com/.well-known/security.txt returned 404 on 17 October 2026 (not re-read).", "cdn.deepseek.com answers robots.txt with a plain 404 (4 November 2026). Because of the Terms of Use clause, nothing else on DeepSeek's hosts (api-docs, status, www, platform) was requested on 4 November.", "The status page has a Search Service component, grouped under Chat Service, and no component named for the Search or Fetch API (17 October 2026)." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/deepseek-search-api.json", "live": { "slug": "deepseek-search-api", "probe": { "target": "https://api.deepseek.com/v1/tools/search", "method": "get", "lastAt": "2026-11-07T19:22:03.395445263Z", "lastOk": true, "lastStatus": 401, "lastMs": 275, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 286, "p95ms24h": 366, "samples24h": 238, "samples30d": 5155, "days": [ { "date": "2026-10-17", "probes": 21, "ok": 21 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.deepseek.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:37.96985213Z" }, "securityTxt": { "url": "https://deepseek.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:54.973930725Z" }, "domain": { "domain": "deepseek.com", "registered": "2000-08-13", "source": "https://rdap.verisign.com/com/v1/domain/deepseek.com", "checkedAt": "2026-11-01T14:07:48.239871757Z" }, "updatedAt": "2026-11-07T19:22:03.395445263Z" } }, "answer": "DeepSeek Search and Fetch API scores 55.5 (C) on agent readiness against Mojeek Web Search API's 36.4 (F), and leads in 5 of 7 scored categories. Mojeek Web Search API leads on transparency \u0026 trust.", "b": { "slug": "mojeek", "name": "Mojeek Web Search API", "vendor": "Mojeek Limited", "vendorUrl": "https://www.mojeek.com/services/search/web-search-api/", "kind": "http-api", "category": "search", "summary": "Mojeek's Web Search API returns results from Mojeek's own independent web index as JSON or XML, with country and language boosting, date and domain filters. Mojeek Limited runs it from the UK on pay-as-you-go plans.", "url": "https://www.anchorterminal.com/tools/mojeek", "markdownUrl": "https://www.anchorterminal.com/tools/mojeek.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mojeek.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mojeek.json", "dns": "mojeek.grade.anchorterminal.com", "transports": [], "packages": [], "auth": "api-key", "authNotes": "One API key per account, sent as the `api_key` query parameter, the only method the docs show. A key is issued after a browser signup with a bank card. Rotating or revoking a key is done by emailing api@mojeek.com, per a staff reply on the community forum on 22 October 2026.", "pricing": "usage", "pricingNotes": "£2 per 1,000 requests on Startup (5 a second, 100,000 a day, up to 10 results a request) and £3 on Business (10 a second, 400,000 a day, up to 40 results, storage rights). Enterprise by contract. A free credit on signup, but a card is required. No automatic payments; prices exclude VAT.", "priceSummary": "$2.68 / 1k req", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Search API page, the API docs or the API terms (checked 2026-11-06). Payments go through Stripe after a browser signup.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://www.mojeek.com/support/api/search/", "capabilities": [ "web.search" ], "tags": [ "hosted", "usage", "uk", "eu", "status-page" ], "graded": true, "anchor": { "graded": true, "score": 36.4, "grade": "F", "agentReady": false, "rank": 1387, "ranked": true, "rankOf": 1510, "categoryRank": 25, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 10, "payments": 20, "reliability": 45, "schema": 29, "security": 15, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Agents and products that want a second, independent index beside Google-derived results, or European data handling with no sub-processors.", "strengths": [ "Results come from Mojeek's own crawler and index, not from Google or Bing", "Published prices of £2 and £3 per 1,000 requests, with no minimum commitment and no automatic payments", "Region and language boosts, date windows, up to 25 included or excluded domains, and adjustable title and snippet lengths", "The API page states 90-day retention, zero retention on request and no sub-processors, with infrastructure run in Europe", "Business and Enterprise plans allow results to be stored indefinitely and combined with other engines" ], "weaknesses": [ "The API key is documented only as a URL query parameter, and rotating a key means emailing the API team", "A bank card is required to open an account, even for the free credit", "No OpenAPI, llms.txt, changelog, version or error code list; errors arrive as a free-text status string", "No HTTP 429 or retry guidance and no SLA; the terms allow interruption without notice", "Startup results may be cached for one hour only, and the terms forbid using results in a search index" ], "agentNotes": [ "Send `fmt=json`, since the default response is XML", "Read `response.status` on every call; a daily limit shows as 'ERROR: Daily Limit Reached' rather than an HTTP error", "Set `lb`, `lbb`, `rb` and `rbb` as 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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 36.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 10, "payments": 20, "reliability": 45, "schema": 29, "security": 15, "transparency": 50 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.mojeek.com/search?q=mojeek\u0026api_key=YOUR_API_KEY\u0026lb=EN\u0026lbb=100\u0026rb=GB\u0026rbb=10\u0026fmt=json\"" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/mojeek" }, "area": "web-data", "unitPrices": [ { "item": "Search request, Startup", "unit": "1k-requests", "usd": 2.68, "note": "£2, converted at the ECB rates of 6 November 2026 (USD 1.1165, GBP 0.83415 per euro). Excludes VAT" }, { "item": "Search request, Business", "unit": "1k-requests", "usd": 4.02, "note": "£3, with storage rights" } ], "provenance": { "legalEntity": "Mojeek Limited", "domain": "mojeek.com", "domainRegistered": "2004-09-30", "endpointOnVendorDomain": true, "terms": "https://www.mojeek.com/about/legal/api-terms.html", "privacy": "https://www.mojeek.com/about/privacy/", "statusPage": "https://status.mojeek.com/", "changelog": "", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "Mojeek Limited, registered in England number 06918197, registered address in Croydon, office at the Sussex Innovation Centre in Brighton, per the site footer.", "The API terms name Mojeek Limited, choose English law and forbid using the services 'by any automated means unless you are an authorised Services user'. Recorded as a fact; only public pages were read.", "www.mojeek.com/robots.txt disallows /search, /url, /focus/dashboard, /eval and /image? for all agents; none of the pages read is under those paths.", "The privacy policy is dated 2 February 2022 and covers the search website. It says logs are kept indefinitely with IP addresses replaced by a country code.", "/.well-known/security.txt names security@mojeek.com and the contact page, with no Expires field. /security.txt answers 404.", "status.mojeek.com is a Site24x7 StatusIQ page drawn by script. Its RSS feed lists Search, Website, Blog and Community components, all operational on 6 November 2026.", "RDAP gives mojeek.com a registration date of 30 September 2004." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mojeek.json", "live": { "slug": "mojeek", "vendorStatus": { "page": "https://status.mojeek.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:12.320117499Z" }, "securityTxt": { "url": "https://mojeek.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:01:02.996132936Z" }, "pages": [ { "url": "https://www.mojeek.com/about/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:31:48.341040926Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cd749befb394" }, { "url": "https://www.mojeek.com/about/legal/api-terms.html", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:46.299086085Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f593843e677e" } ], "updatedAt": "2026-11-07T16:01:02.996132936Z" } }, "edges": [ { "by": 32, "category": "maintenance", "leads": "deepseek-search-api", "name": "Maintenance \u0026 community", "reasons": { "a": "Closed service, per the 17 October check, not re-read on 4 November (terms pause). Opened on 17 October 2026, 18 days before this check (30). The change log's 17 October entry is the only dated one about Search or Fetch in the 90 days from 6 August (0 of 20). Dated change log, api-service@deepseek.com and a Discord server, not tested for replies (12 of 15). No official SDK (0 of 15). No SDK or package to assess (0 of 10). 30 + 0 + 12 + 0 + 0 = 42.", "b": "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." }, "scores": { "a": 42, "b": 10 } }, { "by": 28, "category": "security", "leads": "deepseek-search-api", "name": "Security \u0026 auth", "reasons": { "a": "Per the 17 October check, not re-read on 4 November (terms pause). The ordinary DeepSeek bearer key, revocable, with no scopes, so a key used for search can also spend on models. No secret in a URL (20 of 30). Both endpoints only read, so there's nothing destructive to approve, but no search-only key (15 of 20). Results and fetched pages are untrusted web text. The change log says the engine filters 'SEO spam, GEO manipulation, and low-quality AIGC', with no technical detail and no prompt-injection guidance (3 of 15). No per-call log or audit log found in the docs. The platform console wasn't readable (0 of 15). Security programme 5 of 20 (was 0). The www.deepseek.com footer carries a Report Security Issue address, security@deepseek.com, per the 21 October reading used for DeepSeek's open-weight listings; no security.txt (404 on 17 October), disclosure policy, bug bounty or certification found. 20 + 15 + 3 + 0 + 5 = 43.", "b": "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." }, "scores": { "a": 43, "b": 15 } }, { "by": 27, "category": "reliability", "leads": "deepseek-search-api", "name": "Reliability", "reasons": { "a": "Hosted reading. DeepSeek's Terms of Use bar capturing or copying content of the Services with robots, spiders or other automatic setups, so no DeepSeek page beyond the terms was requested on 4 November and every line is per the 17 October check, not re-read on 4 November. status.deepseek.com, run on Flashduty, has component history, but the endpoints have no component of their own; the nearest is Search Service, grouped under Chat Service. This run gives 15 for a vendor status page with no component for the product (was 10). The recorded history holds Search service errors of 6 minutes on 14 August and 39 on 18 August inside the 90 days from 6 August (the 29 July one has left the window), minor only; the window after 17 October is unread, so the line keeps its recorded 20. Per-account limits of 5 requests a second for each endpoint (15). The guide says to wait and retry on 408, 429 and 5xx, with no Retry-After or backoff schedule, and documents both endpoints as read-only and safe to retry, which this run reads as safe-retry guidance without idempotency keys, 12 (was 10). No SLA found (0). Opened to everyone with no beta label (10). 15 + 20 + 15 + 12 + 0 + 10 = 72.", "b": "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." }, "scores": { "a": 72, "b": 45 } }, { "by": 26, "category": "schema", "leads": "deepseek-search-api", "name": "Schema \u0026 documentation", "reasons": { "a": "Per the 17 October check, not re-read on 4 November (terms pause). No OpenAPI file found. The API reference is rendered from a schema, but no spec is linked, and /openapi.json and /openapi.yaml on the docs host serve the docs page (0). No llms.txt, since api-docs.deepseek.com answered /llms.txt with HTML (0). The guide says what each endpoint is for and which result field suits a UI or a model, and gives the score thresholds for quality and authority, but not when to use Search content against a Fetch (14 of 20). Types, required fields, defaults and limits on every field, such as `query` 1 to 128 characters and `count` 1 to 50. Filters live inside the free-text query (13 of 15). curl and Python examples, an error body and a table of ten status codes with retry guidance. The reference shows only the 200 response (13 of 15). Dated change log and a /v1 path (15). 0 + 0 + 14 + 13 + 13 + 15 = 55.", "b": "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." }, "scores": { "a": 55, "b": 29 } }, { "by": 15, "category": "ergonomics", "leads": "deepseek-search-api", "name": "Agent ergonomics", "reasons": { "a": "Per the 17 October check, not re-read on 4 November (terms pause). Responses can be sized with `count` and `need_content`, off by default, and each result carries both a short snippet and a 600 to 800 character summary. No field selection, and full content has no length cap stated (20 of 25). Site, language, date and phrase filters, up to 50 results, no pagination (15 of 20). Ten documented codes with what to do, 402 for an empty balance and 404 for an unfetchable page. `param` is always null and `code` repeats the type (17 of 20). Both endpoints are documented as read-only and safe to retry, and failed or empty calls aren't billed (20). Only `query` or `url` is required. No official SDKs, the docs use raw HTTP and Python requests (9 of 15). 20 + 15 + 17 + 20 + 9 = 81.", "b": "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." }, "scores": { "a": 81, "b": 66 } }, { "by": 8, "category": "transparency", "leads": "mojeek", "name": "Transparency \u0026 trust", "reasons": { "a": "Per the 17 October check for the privacy policy, not re-read on 4 November (terms pause). Closed service with published terms under PRC law, which assign Outputs to the customer; the Open Platform terms (released 22 April, effective 29 April 2026) and the Terms of Use (last update 27 March 2026) were re-read on 4 November (15). The privacy policy of 10 February 2026 says personal data trains models unless you opt out by email and gives no retention period. It also says search runs on 'third-party APIs' that receive input keywords, which disagrees with the in-house engine described on 17 October, and nothing covers fetched URLs (5 of 30). No deprecation policy, and the only dated notice is the end of free server-side calls on 31 October (5 of 20). Data location disclosed as the PRC, third parties named only by category (10 of 20). 15 + 5 + 5 + 10 = 35.", "b": "Closed service with API terms naming Mojeek Limited under English law (15 of 30). The API page states 90-day retention, zero retention on request, no sub-processors and that Mojeek is the processor and the customer the controller, while the API terms say both parties are independent controllers under GDPR, and the privacy policy of 2 February 2022 covers only the website (12 of 30). The terms promise 30 days' notice of material changes and of price changes, but there is no deprecation policy or dated notices (5 of 20). The API page says there are no sub-processors and infrastructure is owned and run in Europe, in a UK data centre per the about page (18 of 20). 15 + 12 + 5 + 18 = 50." }, "scores": { "a": 60, "b": 68 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "DeepSeek", "b": "Mojeek Limited", "name": "Vendor" }, { "a": "https://api.deepseek.com/v1/tools/search", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.75 per 1,000 requests", "b": "$2.68 per 1,000 requests", "name": "Price for web search" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-10-17", "b": "none", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2022-02-02", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "DeepSeek Search and Fetch API scores 55.5 (C) on agent readiness against Mojeek Web Search API's 36.4 (F), and leads in 5 of 7 scored categories. Mojeek Web Search API leads on transparency \u0026 trust.", "question": "Which is better for AI agents, DeepSeek Search and Fetch API or Mojeek Web Search API?" }, { "answer": "DeepSeek Search and Fetch API, at $0.75 per 1,000 requests against $2.68 per 1,000 requests for Mojeek Web Search API. These are the vendors' published prices for the job.", "question": "Which is cheaper for web search, DeepSeek Search and Fetch API or Mojeek Web Search API?" }, { "answer": "Both need an API key.", "question": "Do DeepSeek Search and Fetch API and Mojeek Web Search API need an API key?" }, { "answer": "DeepSeek Search and Fetch API has a hosted endpoint at https://api.deepseek.com/v1/tools/search. No hosted endpoint is listed for Mojeek Web Search API.", "question": "Can an agent call DeepSeek Search and Fetch API and Mojeek Web Search API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 72 against 45", "Schema \u0026 documentation, 55 against 29", "Agent ergonomics, 81 against 66", "Security \u0026 auth, 43 against 15", "Maintenance \u0026 community, 42 against 10" ], "also": [ "Cheaper for web search, $0.75 against $2.68 per 1,000 requests", "A hosted endpoint, with nothing to install" ], "goodFor": "Cheap per-request web search with model-ready summaries and an authority signal, plus page fetching, for agents already on a DeepSeek key and comfortable with data held in the PRC.", "slug": "deepseek-search-api", "watchFor": "Opened on 17 October 2026, with no service record of its own and no component for it on the status page" }, { "aheadOn": [ "Transparency \u0026 trust, 68 against 60" ], "also": null, "goodFor": "Agents and products that want a second, independent index beside Google-derived results, or European data handling with no sub-processors.", "slug": "mojeek", "watchFor": "The API key is documented only as a URL query parameter, and rotating a key means emailing the API team" } ], "history": { "deepseek-search-api": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": 2.3, "from": 53.2, "fromGrade": "D", "to": 55.5, "toGrade": "C" } ], "mojeek": null }, "job": { "capability": "web.search", "name": "Web search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-mojeek.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-deepseek-search-api.json", "title": "Arcmira vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/arcmira-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-mojeek.json", "title": "Arcmira vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/arcmira-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.json", "title": "Grounding with Bing Search vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.json", "title": "Grounding with Bing Search vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-deepseek-search-api.json", "title": "Brave Search API + MCP vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-mojeek.json", "title": "Brave Search API + MCP vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-deepseek-search-api.json", "title": "Cloudflare Web Search API vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-mojeek.json", "title": "Cloudflare Web Search API vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-exa-mcp.json", "title": "DeepSeek Search and Fetch API vs Exa API + MCP", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-exa-mcp" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-firecrawl-mcp.json", "title": "DeepSeek Search and Fetch API vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai.json", "title": "DeepSeek Search and Fetch API vs Grep AI", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search.json", "title": "DeepSeek Search and Fetch API vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup.json", "title": "DeepSeek Search and Fetch API vs Linkup", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher.json", "title": "DeepSeek Search and Fetch API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api.json", "title": "DeepSeek Search and Fetch API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.json", "title": "DeepSeek Search and Fetch API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-searchapi-io.json", "title": "DeepSeek Search and Fetch API vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpapi.json", "title": "DeepSeek Search and Fetch API vs SerpApi", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serper.json", "title": "DeepSeek Search and Fetch API vs Serper", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serphouse.json", "title": "DeepSeek Search and Fetch API vs SERPHouse", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite.json", "title": "DeepSeek Search and Fetch API vs SerpKite", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream.json", "title": "DeepSeek Search and Fetch API vs SpecStream", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tavily-mcp.json", "title": "DeepSeek Search and Fetch API vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tinyfish-search.json", "title": "DeepSeek Search and Fetch API vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-valyu.json", "title": "DeepSeek Search and Fetch API vs Valyu", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-you-com-api.json", "title": "DeepSeek Search and Fetch API vs You.com APIs", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-mojeek.json", "title": "Exa API + MCP vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-mojeek.json", "title": "Firecrawl MCP vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-mojeek.json", "title": "Grep AI vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-mojeek.json", "title": "Kagi Search API vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-mojeek.json", "title": "Linkup vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/linkup-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-newscatcher.json", "title": "Mojeek Web Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/mojeek-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-parallel-search-api.json", "title": "Mojeek Web Search API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/mojeek-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.json", "title": "Mojeek Web Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-searchapi-io.json", "title": "Mojeek Web Search API vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/mojeek-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-serpapi.json", "title": "Mojeek Web Search API vs SerpApi", "url": "https://www.anchorterminal.com/compare/mojeek-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-serper.json", "title": "Mojeek Web Search API vs Serper", "url": "https://www.anchorterminal.com/compare/mojeek-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-serphouse.json", "title": "Mojeek Web Search API vs SERPHouse", "url": "https://www.anchorterminal.com/compare/mojeek-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-serpkite.json", "title": "Mojeek Web Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/mojeek-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-specstream.json", "title": "Mojeek Web Search API vs SpecStream", "url": "https://www.anchorterminal.com/compare/mojeek-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-tavily-mcp.json", "title": "Mojeek Web Search API vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/mojeek-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-tinyfish-search.json", "title": "Mojeek Web Search API vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/mojeek-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-valyu.json", "title": "Mojeek Web Search API vs Valyu", "url": "https://www.anchorterminal.com/compare/mojeek-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-you-com-api.json", "title": "Mojeek Web Search API vs You.com APIs", "url": "https://www.anchorterminal.com/compare/mojeek-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-fetch-reference-server.json", "title": "DeepSeek Search and Fetch API vs Fetch (MCP reference server)", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-fetch-reference-server" } ], "panel": null, "scores": [ { "by": 27, "deepseek-search-api": 72, "edge": "deepseek-search-api", "key": "reliability", "mojeek": 45, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 26, "deepseek-search-api": 55, "edge": "deepseek-search-api", "key": "schema", "mojeek": 29, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 15, "deepseek-search-api": 81, "edge": "deepseek-search-api", "key": "ergonomics", "mojeek": 66, "name": "Agent ergonomics", "weight": 13 }, { "by": 28, "deepseek-search-api": 43, "edge": "deepseek-search-api", "key": "security", "mojeek": 15, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "deepseek-search-api": 20, "edge": "", "key": "payments", "mojeek": 20, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 32, "deepseek-search-api": 42, "edge": "deepseek-search-api", "key": "maintenance", "mojeek": 10, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 8, "deepseek-search-api": 60, "edge": "mojeek", "key": "transparency", "mojeek": 68, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "DeepSeek Search and Fetch API scores 55.5 (C) on agent readiness against Mojeek Web Search API's 36.4 (F), and leads in 5 of 7 scored categories. Mojeek Web Search API leads on transparency \u0026 trust. Both do web search. DeepSeek Search and Fetch API is cheaper for web search, $0.75 against $2.68 per 1,000 requests.", "tasks": null, "tutorials": [], "verdicts": { "deepseek-search-api": "Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training.", "mojeek": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek", "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.min.md" }, "markdown": "DeepSeek Search and Fetch API scores 55.5 (C) on agent readiness against Mojeek Web Search API's 36.4 (F), and leads in 5 of 7 scored categories. Mojeek Web Search API leads on transparency \u0026 trust. Both do web search. DeepSeek Search and Fetch API is cheaper for web search, $0.75 against $2.68 per 1,000 requests.\n\n- DeepSeek Search and Fetch API: grade C, 55.5/100, rank #866 of 1510. Markdown https://www.anchorterminal.com/tools/deepseek-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json\n- Mojeek Web Search API: grade F, 36.4/100, rank #1387 of 1510. Markdown https://www.anchorterminal.com/tools/mojeek.md · JSON https://www.anchorterminal.com/api/v1/tools/mojeek.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 326 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### DeepSeek Search and Fetch API (C)\n\nGood for: Cheap per-request web search with model-ready summaries and an authority signal, plus page fetching, for agents already on a DeepSeek key and comfortable with data held in the PRC.\n\nAhead on:\n- Reliability, 72 against 45\n- Schema \u0026 documentation, 55 against 29\n- Agent ergonomics, 81 against 66\n- Security \u0026 auth, 43 against 15\n- Maintenance \u0026 community, 42 against 10\n\nAlso in its favour:\n- Cheaper for web search, $0.75 against $2.68 per 1,000 requests\n- A hosted endpoint, with nothing to install\n\nWatch for: Opened on 17 October 2026, with no service record of its own and no component for it on the status page\n\n### Mojeek Web Search API (F)\n\nGood for: Agents and products that want a second, independent index beside Google-derived results, or European data handling with no sub-processors.\n\nAhead on:\n- Transparency \u0026 trust, 68 against 60\n\nWatch for: The API key is documented only as a URL query parameter, and rotating a key means emailing the API team\n\n\n## Why the edge\n\n### Maintenance \u0026 community: DeepSeek Search and Fetch API +32\n\n- DeepSeek Search and Fetch API (42): Closed service, per the 17 October check, not re-read on 4 November (terms pause). Opened on 17 October 2026, 18 days before this check (30). The change log's 17 October entry is the only dated one about Search or Fetch in the 90 days from 6 August (0 of 20). Dated change log, api-service@deepseek.com and a Discord server, not tested for replies (12 of 15). No official SDK (0 of 15). No SDK or package to assess (0 of 10). 30 + 0 + 12 + 0 + 0 = 42.\n- 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.\n\n### Security \u0026 auth: DeepSeek Search and Fetch API +28\n\n- DeepSeek Search and Fetch API (43): Per the 17 October check, not re-read on 4 November (terms pause). The ordinary DeepSeek bearer key, revocable, with no scopes, so a key used for search can also spend on models. No secret in a URL (20 of 30). Both endpoints only read, so there's nothing destructive to approve, but no search-only key (15 of 20). Results and fetched pages are untrusted web text. The change log says the engine filters 'SEO spam, GEO manipulation, and low-quality AIGC', with no technical detail and no prompt-injection guidance (3 of 15). No per-call log or audit log found in the docs. The platform console wasn't readable (0 of 15). Security programme 5 of 20 (was 0). The www.deepseek.com footer carries a Report Security Issue address, security@deepseek.com, per the 21 October reading used for DeepSeek's open-weight listings; no security.txt (404 on 17 October), disclosure policy, bug bounty or certification found. 20 + 15 + 3 + 0 + 5 = 43.\n- 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.\n\n### Reliability: DeepSeek Search and Fetch API +27\n\n- DeepSeek Search and Fetch API (72): Hosted reading. DeepSeek's Terms of Use bar capturing or copying content of the Services with robots, spiders or other automatic setups, so no DeepSeek page beyond the terms was requested on 4 November and every line is per the 17 October check, not re-read on 4 November. status.deepseek.com, run on Flashduty, has component history, but the endpoints have no component of their own; the nearest is Search Service, grouped under Chat Service. This run gives 15 for a vendor status page with no component for the product (was 10). The recorded history holds Search service errors of 6 minutes on 14 August and 39 on 18 August inside the 90 days from 6 August (the 29 July one has left the window), minor only; the window after 17 October is unread, so the line keeps its recorded 20. Per-account limits of 5 requests a second for each endpoint (15). The guide says to wait and retry on 408, 429 and 5xx, with no Retry-After or backoff schedule, and documents both endpoints as read-only and safe to retry, which this run reads as safe-retry guidance without idempotency keys, 12 (was 10). No SLA found (0). Opened to everyone with no beta label (10). 15 + 20 + 15 + 12 + 0 + 10 = 72.\n- 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.\n\n### Schema \u0026 documentation: DeepSeek Search and Fetch API +26\n\n- DeepSeek Search and Fetch API (55): Per the 17 October check, not re-read on 4 November (terms pause). No OpenAPI file found. The API reference is rendered from a schema, but no spec is linked, and /openapi.json and /openapi.yaml on the docs host serve the docs page (0). No llms.txt, since api-docs.deepseek.com answered /llms.txt with HTML (0). The guide says what each endpoint is for and which result field suits a UI or a model, and gives the score thresholds for quality and authority, but not when to use Search content against a Fetch (14 of 20). Types, required fields, defaults and limits on every field, such as `query` 1 to 128 characters and `count` 1 to 50. Filters live inside the free-text query (13 of 15). curl and Python examples, an error body and a table of ten status codes with retry guidance. The reference shows only the 200 response (13 of 15). Dated change log and a /v1 path (15). 0 + 0 + 14 + 13 + 13 + 15 = 55.\n- 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.\n\n### Agent ergonomics: DeepSeek Search and Fetch API +15\n\n- DeepSeek Search and Fetch API (81): Per the 17 October check, not re-read on 4 November (terms pause). Responses can be sized with `count` and `need_content`, off by default, and each result carries both a short snippet and a 600 to 800 character summary. No field selection, and full content has no length cap stated (20 of 25). Site, language, date and phrase filters, up to 50 results, no pagination (15 of 20). Ten documented codes with what to do, 402 for an empty balance and 404 for an unfetchable page. `param` is always null and `code` repeats the type (17 of 20). Both endpoints are documented as read-only and safe to retry, and failed or empty calls aren't billed (20). Only `query` or `url` is required. No official SDKs, the docs use raw HTTP and Python requests (9 of 15). 20 + 15 + 17 + 20 + 9 = 81.\n- 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.\n\n### Transparency \u0026 trust: Mojeek Web Search API +8\n\n- DeepSeek Search and Fetch API (60): Per the 17 October check for the privacy policy, not re-read on 4 November (terms pause). Closed service with published terms under PRC law, which assign Outputs to the customer; the Open Platform terms (released 22 April, effective 29 April 2026) and the Terms of Use (last update 27 March 2026) were re-read on 4 November (15). The privacy policy of 10 February 2026 says personal data trains models unless you opt out by email and gives no retention period. It also says search runs on 'third-party APIs' that receive input keywords, which disagrees with the in-house engine described on 17 October, and nothing covers fetched URLs (5 of 30). No deprecation policy, and the only dated notice is the end of free server-side calls on 31 October (5 of 20). Data location disclosed as the PRC, third parties named only by category (10 of 20). 15 + 5 + 5 + 10 = 35.\n- Mojeek Web Search API (68): Closed service with API terms naming Mojeek Limited under English law (15 of 30). The API page states 90-day retention, zero retention on request, no sub-processors and that Mojeek is the processor and the customer the controller, while the API terms say both parties are independent controllers under GDPR, and the privacy policy of 2 February 2022 covers only the website (12 of 30). The terms promise 30 days' notice of material changes and of price changes, but there is no deprecation policy or dated notices (5 of 20). The API page says there are no sub-processors and infrastructure is owned and run in Europe, in a UK data centre per the about page (18 of 20). 15 + 12 + 5 + 18 = 50.\n\n## Score by category\n\n| Category | Weight | DeepSeek Search and Fetch API | Mojeek Web Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 45 | DeepSeek Search and Fetch API +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 55 | 29 | DeepSeek Search and Fetch API +26 |\n| Agent ergonomics | 13% (16.2 this run) | 81 | 66 | DeepSeek Search and Fetch API +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 15 | DeepSeek Search and Fetch API +28 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 10 | DeepSeek Search and Fetch API +32 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 68 | Mojeek Web Search API +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55.5 · C** | **36.4 · F** | |\n\n## Facts side by side\n\n| Fact | DeepSeek Search and Fetch API | Mojeek Web Search API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | DeepSeek | Mojeek Limited |\n| Hosted endpoint | `https://api.deepseek.com/v1/tools/search` | no (local only) |\n| Transports | HTTP | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $0.75 per 1,000 requests | $2.68 per 1,000 requests |\n| x402 | no | no |\n| Tools exposed | none | 0 |\n| Read-only variant documented | yes | no |\n| llms.txt | no | no |\n| Last release | 2026-10-17 | none |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | 2022-02-02 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Agent reviews | 3/5 (4) | none |\n\n## How the scores have moved\n\n### DeepSeek Search and Fetch API\n\n- +2.3 on 4 November 2026 (D to C): correction\n\n### Mojeek Web Search API\n\nNo score change since it was listed.\n\n## Verdicts\n\n**DeepSeek Search and Fetch API.** Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training.\n\n**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.\n\n## Before you call either\n\n### DeepSeek Search and Fetch API\n\n1. Keep `query` to 128 characters and put filters in it as operators, such as `site:github.com lang:en after:2026-01-01`\n2. Leave `need_content` false and read `summary` first, then call Fetch on the URLs you keep\n3. Stay under 5 requests a second per account across all keys. On 408, 429 or 5xx wait and retry, since no Retry-After is documented\n4. Don't retry a Fetch 403 or 404 unchanged. The page is blocked by policy, unreachable or has no Markdown\n5. Don't send private queries or an end user's IP in `localization`. Data is stored in the PRC\n\n### Mojeek Web Search API\n\n1. Send `fmt=json`, since the default response is XML\n2. Read `response.status` on every call; a daily limit shows as 'ERROR: Daily Limit Reached' rather than an HTTP error\n3. Set `lb`, `lbb`, `rb` and `rbb` as the quickstart recommends, or results lean to no language or region\n4. Keep the key out of logs and shared URLs, since it travels in the query string\n5. On the Startup plan, don't keep results for more than an hour\n\n## Questions\n\n### Which is better for AI agents, DeepSeek Search and Fetch API or Mojeek Web Search API?\n\nDeepSeek Search and Fetch API scores 55.5 (C) on agent readiness against Mojeek Web Search API's 36.4 (F), and leads in 5 of 7 scored categories. Mojeek Web Search API leads on transparency \u0026 trust.\n\n### Which is cheaper for web search, DeepSeek Search and Fetch API or Mojeek Web Search API?\n\nDeepSeek Search and Fetch API, at $0.75 per 1,000 requests against $2.68 per 1,000 requests for Mojeek Web Search API. These are the vendors' published prices for the job.\n\n### Do DeepSeek Search and Fetch API and Mojeek Web Search API need an API key?\n\nBoth need an API key.\n\n### Can an agent call DeepSeek Search and Fetch API and Mojeek Web Search API without installing anything?\n\nDeepSeek Search and Fetch API has a hosted endpoint at https://api.deepseek.com/v1/tools/search. No hosted endpoint is listed for Mojeek Web Search API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deepseek-search-api\", \"b\": \"mojeek\"}`. From a terminal: `anchor compare deepseek-search-api mojeek`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json and https://www.anchorterminal.com/api/v1/tools/mojeek.json\n\n## Other comparisons with DeepSeek Search and Fetch API or Mojeek Web Search API\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Mojeek Web Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-mojeek.md)\n- [Arcmira vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/arcmira-vs-deepseek-search-api.md)\n- [Arcmira vs Mojeek Web Search API](https://www.anchorterminal.com/compare/arcmira-vs-mojeek.md)\n- [Grounding with Bing Search vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.md)\n- [Grounding with Bing Search vs Mojeek Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.md)\n- [Brave Search API + MCP vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-deepseek-search-api.md)\n- [Brave Search API + MCP vs Mojeek Web Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-mojeek.md)\n- [Cloudflare Web Search API vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-deepseek-search-api.md)\n- [Cloudflare Web Search API vs Mojeek Web Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-mojeek.md)\n- [DeepSeek Search and Fetch API vs Exa API + MCP](https://www.anchorterminal.com/compare/deepseek-search-api-vs-exa-mcp.md)\n- [DeepSeek Search and Fetch API vs Firecrawl MCP](https://www.anchorterminal.com/compare/deepseek-search-api-vs-firecrawl-mcp.md)\n- [DeepSeek Search and Fetch API vs Grep AI](https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai.md)\n- [DeepSeek Search and Fetch API vs Kagi Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search.md)\n- [DeepSeek Search and Fetch API vs Linkup](https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup.md)\n- [DeepSeek Search and Fetch API vs NewsCatcher](https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher.md)\n- [DeepSeek Search and Fetch API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api.md)\n- [DeepSeek Search and Fetch API vs Perplexity Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.md)\n- [DeepSeek Search and Fetch API vs SearchAPI.io](https://www.anchorterminal.com/compare/deepseek-search-api-vs-searchapi-io.md)\n- [DeepSeek Search and Fetch API vs SerpApi](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpapi.md)\n- [DeepSeek Search and Fetch API vs Serper](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serper.md)\n- [DeepSeek Search and Fetch API vs SERPHouse](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serphouse.md)\n- [DeepSeek Search and Fetch API vs SerpKite](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite.md)\n- [DeepSeek Search and Fetch API vs SpecStream](https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream.md)\n- [DeepSeek Search and Fetch API vs Tavily API + MCP](https://www.anchorterminal.com/compare/deepseek-search-api-vs-tavily-mcp.md)\n- [DeepSeek Search and Fetch API vs TinyFish Search](https://www.anchorterminal.com/compare/deepseek-search-api-vs-tinyfish-search.md)\n- [DeepSeek Search and Fetch API vs Valyu](https://www.anchorterminal.com/compare/deepseek-search-api-vs-valyu.md)\n- [DeepSeek Search and Fetch API vs You.com APIs](https://www.anchorterminal.com/compare/deepseek-search-api-vs-you-com-api.md)\n- [Exa API + MCP vs Mojeek Web Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-mojeek.md)\n- [Firecrawl MCP vs Mojeek Web Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-mojeek.md)\n- [Grep AI vs Mojeek Web Search API](https://www.anchorterminal.com/compare/grep-ai-vs-mojeek.md)\n- [Kagi Search API vs Mojeek Web Search API](https://www.anchorterminal.com/compare/kagi-search-vs-mojeek.md)\n- [Linkup vs Mojeek Web Search API](https://www.anchorterminal.com/compare/linkup-vs-mojeek.md)\n- [Mojeek Web Search API vs NewsCatcher](https://www.anchorterminal.com/compare/mojeek-vs-newscatcher.md)\n- [Mojeek Web Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/mojeek-vs-parallel-search-api.md)\n- [Mojeek Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.md)\n- [Mojeek Web Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/mojeek-vs-searchapi-io.md)\n- [Mojeek Web Search API vs SerpApi](https://www.anchorterminal.com/compare/mojeek-vs-serpapi.md)\n- [Mojeek Web Search API vs Serper](https://www.anchorterminal.com/compare/mojeek-vs-serper.md)\n- [Mojeek Web Search API vs SERPHouse](https://www.anchorterminal.com/compare/mojeek-vs-serphouse.md)\n- [Mojeek Web Search API vs SerpKite](https://www.anchorterminal.com/compare/mojeek-vs-serpkite.md)\n- [Mojeek Web Search API vs SpecStream](https://www.anchorterminal.com/compare/mojeek-vs-specstream.md)\n- [Mojeek Web Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/mojeek-vs-tavily-mcp.md)\n- [Mojeek Web Search API vs TinyFish Search](https://www.anchorterminal.com/compare/mojeek-vs-tinyfish-search.md)\n- [Mojeek Web Search API vs Valyu](https://www.anchorterminal.com/compare/mojeek-vs-valyu.md)\n- [Mojeek Web Search API vs You.com APIs](https://www.anchorterminal.com/compare/mojeek-vs-you-com-api.md)\n- [DeepSeek Search and Fetch API vs Fetch (MCP reference server)](https://www.anchorterminal.com/compare/deepseek-search-api-vs-fetch-reference-server.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "DeepSeek Search and Fetch API vs Mojeek Web Search API", "url": "" } ], "description": "DeepSeek Search and Fetch scores 55.5 (C) to Mojeek Web Search's 36.4 (F) for web search. DeepSeek Search and Fetch is cheaper for web search, $0.75 against $2.68 per 1,000 requests. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "DeepSeek Search and Fetch API C 55.5", "Mojeek Web Search API F 36.4", "scores" ], "h1": "DeepSeek Search and Fetch API vs Mojeek Web Search API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/deepseek-search-api-vs-mojeek", "published": "2026-10-01", "section": "tools", "title": "DeepSeek Search and Fetch vs Mojeek Web Search for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek" }, "tokens": { "markdown": 6050, "slim": 3280 }, "version": 1 }