{
  "data": {
    "a": {
      "slug": "deepseek-search-api",
      "name": "DeepSeek Search and Fetch API",
      "vendor": "DeepSeek",
      "vendorUrl": "https://www.deepseek.com",
      "company": "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": 56.7,
        "grade": "C",
        "agentReady": false,
        "rank": 916,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 22,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 81,
          "maintenance": 42,
          "payments": 30,
          "reliability": 72,
          "schema": 55,
          "security": 43,
          "transparency": 60
        },
        "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": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 56.7
          }
        ],
        "editorialScores": {
          "ergonomics": 81,
          "maintenance": 42,
          "payments": 30,
          "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-13",
          "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-ocr-2",
        "deepseek-harness",
        "deepseek-superagent",
        "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-18T22:43:20.142067771Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 416,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 282,
          "p95ms24h": 416,
          "samples24h": 241,
          "samples30d": 7837,
          "days": [
            {
              "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": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 228,
              "ok": 228
            }
          ],
          "since": "2026-10-17T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.deepseek.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T18:52:23.753805413Z"
        },
        "securityTxt": {
          "url": "https://deepseek.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:30:35.913140422Z"
        },
        "domain": {
          "domain": "deepseek.com",
          "registered": "2000-08-13",
          "source": "https://rdap.verisign.com/com/v1/domain/deepseek.com",
          "checkedAt": "2026-11-15T15:32:45.312454032Z"
        },
        "updatedAt": "2026-11-18T22:43:20.142067771Z"
      },
      "streak": {
        "days": 32,
        "from": "2026-10-17",
        "sinceWatching": true,
        "best": 32
      }
    },
    "answer": "Hyperresearch scores 68.1 (B) on agent readiness against DeepSeek Search and Fetch API's 56.7 (C), and leads in 6 of 7 scored categories. DeepSeek Search and Fetch API leads on reliability.",
    "b": {
      "slug": "hyperresearch",
      "name": "Hyperresearch",
      "vendor": "Hyperresearch",
      "vendorUrl": "https://hyperresearch.ai",
      "company": "hyperresearch.ai",
      "kind": "http-api",
      "category": "search",
      "summary": "Hyperresearch is a deep research API from Thalient Labs Inc. that turns a question into a cited, checked report, with a source vault, citation verification and per-call Answers search, through REST and two remote MCP servers.",
      "url": "https://www.anchorterminal.com/tools/hyperresearch",
      "markdownUrl": "https://www.anchorterminal.com/tools/hyperresearch.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hyperresearch.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hyperresearch.json",
      "dns": "hyperresearch.grade.anchorterminal.com",
      "repo": "https://github.com/jordan-gibbs/hyperresearch",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://answers.hyperresearch.ai/mcp",
      "packages": [
        {
          "registry": "pypi",
          "name": "hyperresearch"
        },
        {
          "registry": "pypi",
          "name": "langchain-hyperresearch"
        },
        {
          "registry": "npm",
          "name": "@hyperresearch/ai-sdk"
        },
        {
          "registry": "npm",
          "name": "@hyperresearch/langchain"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve scoped bearer keys (`hr_live_` billed, `hr_test_` free fixture mode) created in the console after a browser signup, with rotation, revocation and IP allowlists. MCP servers use OAuth with PKCE and a scope consent screen. A client that asks for no scopes gets read-only access.",
      "pricing": "usage",
      "pricingNotes": "Answers per call from a prepaid wallet: ask 2 cents (fast), 10 cents (standard, 20 when it digs deeper), 50 cents (max). Search 5 or 15 cents. Research runs flat: Light $9, Deep $49. $5 of Answers credit and one Light report free, no card. Top-ups from $10.",
      "priceSummary": "$0.02 / call",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in llms.txt, the pricing page, the Answers page or the docs (checked 2026-11-18). Payment is a Stripe wallet or monthly invoice.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://hyperresearch.ai/docs",
      "llmsTxt": "https://hyperresearch.ai/llms.txt",
      "openapi": "https://api.hyperresearch.ai/v1/openapi.json",
      "registryName": "ai.hyperresearch/answers",
      "capabilities": [
        "search.research",
        "search.answer",
        "web.search",
        "web.fetch"
      ],
      "tags": [
        "hosted",
        "remote-mcp",
        "mcp",
        "mcp-registry",
        "oauth",
        "api-key",
        "llms-txt",
        "openapi",
        "usage-priced",
        "prepaid",
        "no-card",
        "free-tier",
        "async-jobs",
        "webhooks",
        "python",
        "typescript",
        "beta",
        "no-status-page"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 68.1,
        "grade": "B",
        "agentReady": false,
        "rank": 407,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 13,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 88,
          "payments": 60,
          "reliability": 35,
          "schema": 76,
          "security": 79,
          "transparency": 71
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.",
        "bestFor": "Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.",
        "strengths": [
          "Answers MCP prices are public per call: ask 2 cents (fast), 10 cents (standard), 50 cents (max), search 5 or 15 cents, with not-found calls charged less",
          "$5 of Answers credit and one free Light report on every account, no card needed. `hr_test_` keys run free fixture-mode runs",
          "Keys carry scopes (runs, vault, verify, mcp, admin), rotate with a 24-hour overlap and revoke at once. MCP uses OAuth with PKCE and a scope consent screen",
          "One error envelope with a stable `code`, `retryable` and `retry_after`, per-key rate limits by bucket, and `Idempotency-Key` on writes",
          "Fetched pages reach models inside `\u003cuntrusted-source\u003e` fences, with tool allowlists per role and private network ranges refused"
        ],
        "weaknesses": [
          "No status page, and the terms say there is no SLA and no uptime figure",
          "The terms call the service 'a beta from a young company'",
          "No SOC 2 report, no DPA on the shelf, no formal disclosure policy or bug bounty. Vulnerabilities go to the support address",
          "The research MCP server's tool schemas aren't published on a page we could read, and the OpenAPI host refused our reader",
          "Signup and MCP authorisation need a person in a browser. There is no machine payment protocol"
        ],
        "agentNotes": [
          "Use Answers (`data_and_web_answer` with mode `auto`) for one fact, and start a Light or Deep run only when the user wants a written report",
          "Send an `Idempotency-Key` on every write and reuse it only with an unchanged body, so a retried run or answer is charged once",
          "Poll a run with `GET /v1/runs/{id}` about once a minute, or stream its events. A Light run takes about 30 to 40 minutes",
          "If a response has `retryable: false`, change the request rather than retrying. Branch on `error.code`, never on the message",
          "Use a key that starts `hr_test_` to build and test an integration without spending"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 68.1
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 88,
          "payments": 60,
          "reliability": 35,
          "schema": 76,
          "security": 79,
          "transparency": 84
        },
        "provenanceScore": 58,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST https://api.hyperresearch.ai/v1/answers -H \"Authorization: Bearer $HYPERRESEARCH_KEY\" -H \"Idempotency-Key: $(uuidgen)\" -H 'Content-Type: application/json' -d '{\"question\":\"How old must a US senator be?\",\"mode\":\"fast\"}'",
        "claudeCode": "claude mcp add hyperresearch-answers --transport http https://answers.hyperresearch.ai/mcp",
        "config": {
          "mcpServers": {
            "hyperresearch": {
              "url": "https://mcp.hyperresearch.ai/mcp"
            },
            "hyperresearch-answers": {
              "url": "https://answers.hyperresearch.ai/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/search.research",
        "tool": "https://letme.dev/hyperresearch"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Answers ask, fast",
          "unit": "call",
          "usd": 0.02,
          "note": "1 to 2 cents if not found"
        },
        {
          "item": "Answers ask, standard",
          "unit": "call",
          "usd": 0.1,
          "note": "20 cents when it digs deeper"
        },
        {
          "item": "Answers ask, max",
          "unit": "call",
          "usd": 0.5,
          "note": "10 to 50 cents if not found"
        },
        {
          "item": "Answers search, standard",
          "unit": "call",
          "usd": 0.05
        },
        {
          "item": "Answers search, max",
          "unit": "call",
          "usd": 0.15
        },
        {
          "item": "Light research run",
          "unit": "tx",
          "usd": 9,
          "note": "one report"
        },
        {
          "item": "Deep research run",
          "unit": "tx",
          "usd": 49,
          "note": "one report"
        }
      ],
      "provenance": {
        "legalEntity": "Thalient Labs Inc.",
        "domain": "hyperresearch.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://hyperresearch.ai/legal/terms",
        "privacy": "https://hyperresearch.ai/legal/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The about page names Thalient Labs Inc., a Delaware corporation incorporated on 16 March 2026, at 1001 S. Main St., Suite 500, Kalispell, MT 59901, and says the terms, privacy policy and Stripe receipts carry the same details. The terms choose Delaware law and have no arbitration clause.",
          "Terms version 1.7, effective 23 September 2026, last updated 4 October 2026. Privacy policy version 1.7, effective 17 September 2026, per the about page.",
          "hyperresearch.ai/robots.txt allows ClaudeBot, anthropic-ai and Claude-Web and disallows /api/, with Content-Signal search=yes, ai-input=yes, ai-train=yes. mcp. and answers.hyperresearch.ai publish comment-only robots files with no rules. api.hyperresearch.ai's robots.txt asked for a sign-in, so that host wasn't read.",
          "/.well-known/security.txt answers 404. No status page found.",
          "The about page asks directories to copy its product descriptions verbatim. We wrote our own."
        ],
        "score": 58
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/hyperresearch.json",
      "live": {
        "slug": "hyperresearch",
        "probe": {
          "target": "https://answers.hyperresearch.ai/mcp",
          "method": "get",
          "lastAt": "2026-11-18T22:43:33.50023008Z",
          "lastOk": true,
          "lastStatus": 406,
          "lastMs": 233,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 328,
          "p95ms24h": 813,
          "samples24h": 11,
          "samples30d": 11,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 11,
              "ok": 11
            }
          ],
          "since": "2026-11-18T21:38:05.612316973Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "ai.hyperresearch/answers",
            "version": "1.0.1",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.hyperresearch.ai/mcp",
          "checkedAt": "2026-10-01T21:59:49.591132636Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-01T21:59:49.591132636Z"
        },
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 46,
        "category": "maintenance",
        "leads": "hyperresearch",
        "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": "The pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30). Four tagged CLI releases in the 90 days to this check: v0.13.0 (27 October), v0.13.1 (9 November), v0.13.2 (12 November), v0.13.3 (16 November) (20). The CLI changelog credits fixes to issues and pull requests from outside contributors (#71, #201 to #206). We didn't read the issue threads (15 of 25). `ai.hyperresearch/hyperresearch` and `ai.hyperresearch/answers` are in the official MCP registry under the vendor's domain namespace (15). The repository has CI and publish workflows, and AI SDK and LangChain packages are published (8 of 10). 30+20+15+15+8 = 88."
        },
        "scores": {
          "a": 42,
          "b": 88
        }
      },
      {
        "by": 37,
        "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": "Graded on the hosted API and the two remote MCP servers. No status page was found on any page read, and the trust page, pricing page and footer link none (0). No readable incident history (5). Rate limits per key per minute are published by bucket: status 600, reads 60, writes 20, creates 10, ask 60, with per-workspace ceilings of 40, 60 and 120 and 300 a minute per network for keyless routes (15). 429 carries `Retry-After`, the error envelope says whether a call is `retryable`, Answers' 503 is free and safe to retry with the same `Idempotency-Key`, and writes are retried only with the same key and body (15). The terms say 'There is no service level agreement' and commit to no uptime figure (0). The terms call the service 'a beta from a young company' (0). 0+5+15+15+0+0 = 35."
        },
        "scores": {
          "a": 72,
          "b": 35
        }
      },
      {
        "by": 36,
        "category": "security",
        "leads": "hyperresearch",
        "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": "Bearer keys of 32 random bytes stored as salted hashes, shown once, scoped to `runs:read`, `runs:write`, `vault:read`, `vault:write`, `verify`, `mcp` and `admin`, with a last-used time, rotation with a 24-hour overlap and instant revocation, plus an IP allowlist. MCP uses OAuth with PKCE and a consent screen that lists each scope. The docs say never to put keys in URLs (30). A client that requests no scopes gets read-only access, billed scopes are marked on the consent screen, and every workspace has a spend cap. No confirmation step for deletes was found (16 of 20). The trust page documents `\u003cuntrusted-source\u003e` fences on every fetched body, forged fence tags neutralised, per-role tool allowlists, schema-validated arguments and private address ranges refused (15). A workspace audit log exportable as NDJSON, a 365-day default window, and a list of agent connections that can be revoked (15). No security.txt (404), no formal disclosure policy and no bug bounty, and the trust page says there is no SOC 2 report. Vulnerabilities go to support@hyperresearch.ai (3 of 20). 30+16+15+15+3 = 79."
        },
        "scores": {
          "a": 43,
          "b": 79
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "hyperresearch",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "Per the 17 October check, not re-read on 4 November (terms pause). No machine payment protocol in the guide, the API reference or the pricing page (0). $0.75 per 1,000 successful requests for each endpoint, published without a login on the guide and the pricing page (20). No free tier for direct calls. The stated free period for server-side calls made through DeepSeek Harness, Claude Code or Codex ended at 16:00 UTC on 31 October 2026, and it never covered direct calls (0). Browser sign-up and a prepaid top-up (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.",
          "b": "No x402, MPP or L402 (0). Per-call prices for Answers and flat per-run prices (Light $9, Deep $49) are published without login, with rerun discounts and refund rules (30). $5 of Answers credit and the first Light report free on every account, no card needed, and `hr_test_` keys are never billed (30). A person signs up through Clerk in a browser and creates keys in the console, and MCP clients authorise in a browser (0). 0+30+30+0 = 60."
        },
        "scores": {
          "a": 30,
          "b": 60
        }
      },
      {
        "by": 21,
        "category": "schema",
        "leads": "hyperresearch",
        "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": "llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generated from it. api.hyperresearch.ai's robots.txt asked for a sign-in, so read.py closed the host and the file wasn't read (20 of 25). llms.txt, and every docs page as Markdown with `.md` (10). The Answers page says when to use fast, standard, max or auto and that fast skips structured sources, and the docs say Answers is for one fact and runs for a report. The research MCP server's tool descriptions couldn't be read (12 of 20). Modes and run tiers are enums, and examples show `max_results`, but the schemas themselves weren't read (10 of 15). Request and result examples, one error envelope with status meanings and a stable `code` (14 of 15). The version is in the path (/v1) with an additive-only promise, but the hosted service has no public changelog. The open-source CLI's CHANGELOG.md is dated (10 of 15). 20+10+12+10+14+10 = 76."
        },
        "scores": {
          "a": 55,
          "b": 76
        }
      },
      {
        "by": 11,
        "category": "transparency",
        "leads": "hyperresearch",
        "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": "The hosted service is closed with terms from Thalient Labs Inc. (version 1.7), and the CLI that runs the same pipeline is MIT (20 of 30). The trust page states retention per record type (content kept until deleted, verification inputs 7 days, billing at least 7 years, audit log 365 days by default), names the known gaps (the run index and questions are kept indefinitely, no automatic expiry), says customer content isn't used for training, and says it matches the privacy policy. No DPA on the shelf (26 of 30). A written deprecation policy: at least six months' notice, `Deprecation` and `Sunset` headers and a list of deprecations, plus 30 days' notice by email before a shutdown (20). Subprocessors are listed with what each receives and their countries, and the trust page says there is no data residency guarantee on Cloudflare's network (18 of 20). 20+26+20+18 = 84."
        },
        "scores": {
          "a": 60,
          "b": 71
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "DeepSeek",
        "b": "Hyperresearch",
        "name": "Vendor"
      },
      {
        "a": "https://api.deepseek.com/v1/tools/search",
        "b": "https://answers.hyperresearch.ai/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "$0.75 per 1,000 requests",
        "b": "$0.05 per call",
        "name": "Price for web search"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "ai.hyperresearch/answers",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-17",
        "b": "2026-11-16",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "2026-11-17",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2026-11-17",
        "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": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "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": "Hyperresearch scores 68.1 (B) on agent readiness against DeepSeek Search and Fetch API's 56.7 (C), and leads in 6 of 7 scored categories. DeepSeek Search and Fetch API leads on reliability.",
        "question": "Which is better for AI agents, DeepSeek Search and Fetch API or Hyperresearch?"
      },
      {
        "answer": "DeepSeek Search and Fetch API needs an API key. Hyperresearch takes an API key or an OAuth sign-in.",
        "question": "Do DeepSeek Search and Fetch API and Hyperresearch need an API key?"
      },
      {
        "answer": "Yes. DeepSeek Search and Fetch API has a hosted endpoint at https://api.deepseek.com/v1/tools/search and Hyperresearch at https://answers.hyperresearch.ai/mcp.",
        "question": "Can an agent call DeepSeek Search and Fetch API and Hyperresearch without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 72 against 35"
        ],
        "also": null,
        "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": [
          "Schema \u0026 documentation, 76 against 55",
          "Security \u0026 auth, 79 against 43",
          "Payments \u0026 pricing, 60 against 30",
          "Maintenance \u0026 community, 88 against 42",
          "Transparency \u0026 trust, 71 against 60"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.",
        "slug": "hyperresearch",
        "watchFor": "No status page, and the terms say there is no SLA and no uptime figure"
      }
    ],
    "history": {
      "deepseek-search-api": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.2,
          "from": 55.5,
          "fromGrade": "C",
          "to": 56.7,
          "toGrade": "C"
        },
        {
          "causes": [
            "correction"
          ],
          "date": "2026-11-04",
          "delta": 2.3,
          "from": 53.2,
          "fromGrade": "D",
          "to": 55.5,
          "toGrade": "C"
        }
      ],
      "hyperresearch": 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-hyperresearch.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch"
      },
      {
        "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/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-hyperresearch.json",
        "title": "Grounding with Bing Search vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch"
      },
      {
        "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-hyperresearch.json",
        "title": "Brave Search API + MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch"
      },
      {
        "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-hyperresearch.json",
        "title": "Cloudflare Web Search API vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch"
      },
      {
        "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-mojeek.json",
        "title": "DeepSeek Search and Fetch API vs Mojeek Web Search API",
        "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek"
      },
      {
        "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-hyperresearch.json",
        "title": "Exa API + MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.json",
        "title": "Firecrawl MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.json",
        "title": "Hyperresearch vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.json",
        "title": "Hyperresearch vs Mojeek Web Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io.json",
        "title": "Hyperresearch vs SearchAPI.io",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi.json",
        "title": "Hyperresearch vs SerpApi",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serper.json",
        "title": "Hyperresearch vs Serper",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serper"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse.json",
        "title": "Hyperresearch vs SERPHouse",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite.json",
        "title": "Hyperresearch vs SerpKite",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch.json",
        "title": "Arcmira vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch.json",
        "title": "Grep AI vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.json",
        "title": "Hyperresearch vs Liner Search MCP",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-linkup.json",
        "title": "Hyperresearch vs Linkup",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-linkup"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher.json",
        "title": "Hyperresearch vs NewsCatcher",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api.json",
        "title": "Hyperresearch vs Parallel Search and Task APIs",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api.json",
        "title": "Hyperresearch vs Perplexity Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-specstream.json",
        "title": "Hyperresearch vs SpecStream",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-specstream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp.json",
        "title": "Hyperresearch vs Tavily API + MCP",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search.json",
        "title": "Hyperresearch vs TinyFish Search",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.json",
        "title": "Hyperresearch vs Valyu",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-valyu"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-api.json",
        "title": "Hyperresearch vs You.com APIs",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.json",
        "title": "Fetch (MCP reference server) vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 37,
        "deepseek-search-api": 72,
        "edge": "deepseek-search-api",
        "hyperresearch": 35,
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 21,
        "deepseek-search-api": 55,
        "edge": "hyperresearch",
        "hyperresearch": 76,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 2,
        "deepseek-search-api": 81,
        "edge": "hyperresearch",
        "hyperresearch": 83,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 36,
        "deepseek-search-api": 43,
        "edge": "hyperresearch",
        "hyperresearch": 79,
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 30,
        "deepseek-search-api": 30,
        "edge": "hyperresearch",
        "hyperresearch": 60,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 46,
        "deepseek-search-api": 42,
        "edge": "hyperresearch",
        "hyperresearch": 88,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 11,
        "deepseek-search-api": 60,
        "edge": "hyperresearch",
        "hyperresearch": 71,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Hyperresearch scores 68.1 (B) on agent readiness against DeepSeek Search and Fetch API's 56.7 (C), and leads in 6 of 7 scored categories. DeepSeek Search and Fetch API leads on reliability. Both do web search.",
    "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.",
      "hyperresearch": "Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch",
    "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.min.md"
  },
  "markdown": "Hyperresearch scores 68.1 (B) on agent readiness against DeepSeek Search and Fetch API's 56.7 (C), and leads in 6 of 7 scored categories. DeepSeek Search and Fetch API leads on reliability. Both do web search.\n\n- DeepSeek Search and Fetch API: grade C, 56.7/100, rank #916 of 1557. Markdown https://www.anchorterminal.com/tools/deepseek-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json\n- Hyperresearch: grade B, 68.1/100, rank #407 of 1557. Markdown https://www.anchorterminal.com/tools/hyperresearch.md · JSON https://www.anchorterminal.com/api/v1/tools/hyperresearch.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 353 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 35\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### Hyperresearch (B)\n\nGood for: Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.\n\nAhead on:\n- Schema \u0026 documentation, 76 against 55\n- Security \u0026 auth, 79 against 43\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 88 against 42\n- Transparency \u0026 trust, 71 against 60\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No status page, and the terms say there is no SLA and no uptime figure\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Hyperresearch +46\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- Hyperresearch (88): The pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30). Four tagged CLI releases in the 90 days to this check: v0.13.0 (27 October), v0.13.1 (9 November), v0.13.2 (12 November), v0.13.3 (16 November) (20). The CLI changelog credits fixes to issues and pull requests from outside contributors (#71, #201 to #206). We didn't read the issue threads (15 of 25). `ai.hyperresearch/hyperresearch` and `ai.hyperresearch/answers` are in the official MCP registry under the vendor's domain namespace (15). The repository has CI and publish workflows, and AI SDK and LangChain packages are published (8 of 10). 30+20+15+15+8 = 88.\n\n### Reliability: DeepSeek Search and Fetch API +37\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- Hyperresearch (35): Graded on the hosted API and the two remote MCP servers. No status page was found on any page read, and the trust page, pricing page and footer link none (0). No readable incident history (5). Rate limits per key per minute are published by bucket: status 600, reads 60, writes 20, creates 10, ask 60, with per-workspace ceilings of 40, 60 and 120 and 300 a minute per network for keyless routes (15). 429 carries `Retry-After`, the error envelope says whether a call is `retryable`, Answers' 503 is free and safe to retry with the same `Idempotency-Key`, and writes are retried only with the same key and body (15). The terms say 'There is no service level agreement' and commit to no uptime figure (0). The terms call the service 'a beta from a young company' (0). 0+5+15+15+0+0 = 35.\n\n### Security \u0026 auth: Hyperresearch +36\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- Hyperresearch (79): Bearer keys of 32 random bytes stored as salted hashes, shown once, scoped to `runs:read`, `runs:write`, `vault:read`, `vault:write`, `verify`, `mcp` and `admin`, with a last-used time, rotation with a 24-hour overlap and instant revocation, plus an IP allowlist. MCP uses OAuth with PKCE and a consent screen that lists each scope. The docs say never to put keys in URLs (30). A client that requests no scopes gets read-only access, billed scopes are marked on the consent screen, and every workspace has a spend cap. No confirmation step for deletes was found (16 of 20). The trust page documents `\u003cuntrusted-source\u003e` fences on every fetched body, forged fence tags neutralised, per-role tool allowlists, schema-validated arguments and private address ranges refused (15). A workspace audit log exportable as NDJSON, a 365-day default window, and a list of agent connections that can be revoked (15). No security.txt (404), no formal disclosure policy and no bug bounty, and the trust page says there is no SOC 2 report. Vulnerabilities go to support@hyperresearch.ai (3 of 20). 30+16+15+15+3 = 79.\n\n### Payments \u0026 pricing: Hyperresearch +30\n\n- DeepSeek Search and Fetch API (30): Per the 17 October check, not re-read on 4 November (terms pause). No machine payment protocol in the guide, the API reference or the pricing page (0). $0.75 per 1,000 successful requests for each endpoint, published without a login on the guide and the pricing page (20). No free tier for direct calls. The stated free period for server-side calls made through DeepSeek Harness, Claude Code or Codex ended at 16:00 UTC on 31 October 2026, and it never covered direct calls (0). Browser sign-up and a prepaid top-up (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.\n- Hyperresearch (60): No x402, MPP or L402 (0). Per-call prices for Answers and flat per-run prices (Light $9, Deep $49) are published without login, with rerun discounts and refund rules (30). $5 of Answers credit and the first Light report free on every account, no card needed, and `hr_test_` keys are never billed (30). A person signs up through Clerk in a browser and creates keys in the console, and MCP clients authorise in a browser (0). 0+30+30+0 = 60.\n\n### Schema \u0026 documentation: Hyperresearch +21\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- Hyperresearch (76): llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generated from it. api.hyperresearch.ai's robots.txt asked for a sign-in, so read.py closed the host and the file wasn't read (20 of 25). llms.txt, and every docs page as Markdown with `.md` (10). The Answers page says when to use fast, standard, max or auto and that fast skips structured sources, and the docs say Answers is for one fact and runs for a report. The research MCP server's tool descriptions couldn't be read (12 of 20). Modes and run tiers are enums, and examples show `max_results`, but the schemas themselves weren't read (10 of 15). Request and result examples, one error envelope with status meanings and a stable `code` (14 of 15). The version is in the path (/v1) with an additive-only promise, but the hosted service has no public changelog. The open-source CLI's CHANGELOG.md is dated (10 of 15). 20+10+12+10+14+10 = 76.\n\n### Transparency \u0026 trust: Hyperresearch +11\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- Hyperresearch (71): The hosted service is closed with terms from Thalient Labs Inc. (version 1.7), and the CLI that runs the same pipeline is MIT (20 of 30). The trust page states retention per record type (content kept until deleted, verification inputs 7 days, billing at least 7 years, audit log 365 days by default), names the known gaps (the run index and questions are kept indefinitely, no automatic expiry), says customer content isn't used for training, and says it matches the privacy policy. No DPA on the shelf (26 of 30). A written deprecation policy: at least six months' notice, `Deprecation` and `Sunset` headers and a list of deprecations, plus 30 days' notice by email before a shutdown (20). Subprocessors are listed with what each receives and their countries, and the trust page says there is no data residency guarantee on Cloudflare's network (18 of 20). 20+26+20+18 = 84.\n\n## Score by category\n\n| Category | Weight | DeepSeek Search and Fetch API | Hyperresearch | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 72 | 35 | DeepSeek Search and Fetch API +37 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 55 | 76 | Hyperresearch +21 |\n| Agent ergonomics | 13% | 81 | 83 | Hyperresearch +2 |\n| Security \u0026 auth | 14% | 43 | 79 | Hyperresearch +36 |\n| Payments \u0026 pricing | 10% | 30 | 60 | Hyperresearch +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 42 | 88 | Hyperresearch +46 |\n| Transparency \u0026 trust | 7% | 60 | 71 | Hyperresearch +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **56.7 · C** | **68.1 · B** | |\n\n## Facts side by side\n\n| Fact | DeepSeek Search and Fetch API | Hyperresearch |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | DeepSeek | Hyperresearch |\n| Hosted endpoint | `https://api.deepseek.com/v1/tools/search` | `https://answers.hyperresearch.ai/mcp` |\n| Transports | HTTP | Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $0.75 per 1,000 requests | $0.05 per call |\n| x402 | no | no |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `ai.hyperresearch/answers` |\n| Last release | 2026-10-17 | 2026-11-16 |\n| Terms last updated | couldn't be read | 2026-11-17 |\n| Privacy policy last updated | couldn't be read | 2026-11-17 |\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 | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\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- +1.2 on 13 November 2026: checklist\n- +2.3 on 4 November 2026 (D to C): correction\n\n### Hyperresearch\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**Hyperresearch.** Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.\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### Hyperresearch\n\n1. Use Answers (`data_and_web_answer` with mode `auto`) for one fact, and start a Light or Deep run only when the user wants a written report\n2. Send an `Idempotency-Key` on every write and reuse it only with an unchanged body, so a retried run or answer is charged once\n3. Poll a run with `GET /v1/runs/{id}` about once a minute, or stream its events. A Light run takes about 30 to 40 minutes\n4. If a response has `retryable: false`, change the request rather than retrying. Branch on `error.code`, never on the message\n5. Use a key that starts `hr_test_` to build and test an integration without spending\n\n## Questions\n\n### Which is better for AI agents, DeepSeek Search and Fetch API or Hyperresearch?\n\nHyperresearch scores 68.1 (B) on agent readiness against DeepSeek Search and Fetch API's 56.7 (C), and leads in 6 of 7 scored categories. DeepSeek Search and Fetch API leads on reliability.\n\n### Do DeepSeek Search and Fetch API and Hyperresearch need an API key?\n\nDeepSeek Search and Fetch API needs an API key. Hyperresearch takes an API key or an OAuth sign-in.\n\n### Can an agent call DeepSeek Search and Fetch API and Hyperresearch without installing anything?\n\nYes. DeepSeek Search and Fetch API has a hosted endpoint at https://api.deepseek.com/v1/tools/search and Hyperresearch at https://answers.hyperresearch.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deepseek-search-api\", \"b\": \"hyperresearch\"}`. From a terminal: `anchor compare deepseek-search-api hyperresearch`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json and https://www.anchorterminal.com/api/v1/tools/hyperresearch.json\n\n## Other comparisons with DeepSeek Search and Fetch API or Hyperresearch\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 Hyperresearch](https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.md)\n- [Arcmira vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/arcmira-vs-deepseek-search-api.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 Hyperresearch](https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.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 Hyperresearch](https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch.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 Hyperresearch](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.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 Mojeek Web Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.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 Hyperresearch](https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.md)\n- [Firecrawl MCP vs Hyperresearch](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.md)\n- [Hyperresearch vs Kagi Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.md)\n- [Hyperresearch vs Mojeek Web Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.md)\n- [Hyperresearch vs SearchAPI.io](https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io.md)\n- [Hyperresearch vs SerpApi](https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi.md)\n- [Hyperresearch vs Serper](https://www.anchorterminal.com/compare/hyperresearch-vs-serper.md)\n- [Hyperresearch vs SERPHouse](https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse.md)\n- [Hyperresearch vs SerpKite](https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite.md)\n- [Arcmira vs Hyperresearch](https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch.md)\n- [Grep AI vs Hyperresearch](https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch.md)\n- [Hyperresearch vs Liner Search MCP](https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.md)\n- [Hyperresearch vs Linkup](https://www.anchorterminal.com/compare/hyperresearch-vs-linkup.md)\n- [Hyperresearch vs NewsCatcher](https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher.md)\n- [Hyperresearch vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api.md)\n- [Hyperresearch vs Perplexity Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api.md)\n- [Hyperresearch vs SpecStream](https://www.anchorterminal.com/compare/hyperresearch-vs-specstream.md)\n- [Hyperresearch vs Tavily API + MCP](https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp.md)\n- [Hyperresearch vs TinyFish Search](https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search.md)\n- [Hyperresearch vs Valyu](https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.md)\n- [Hyperresearch vs You.com APIs](https://www.anchorterminal.com/compare/hyperresearch-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- [Fetch (MCP reference server) vs Hyperresearch](https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.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-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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 Hyperresearch",
        "url": ""
      }
    ],
    "description": "Hyperresearch scores 68.1 (B) to DeepSeek Search and Fetch's 56.7 (C) for web search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "DeepSeek Search and Fetch API C 56.7",
      "Hyperresearch B 68.1",
      "scores"
    ],
    "h1": "DeepSeek Search and Fetch API vs Hyperresearch",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/deepseek-search-api-vs-hyperresearch",
    "published": "2026-10-01",
    "section": "tools",
    "title": "DeepSeek Search and Fetch vs Hyperresearch for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch"
  },
  "tokens": {
    "markdown": 6150,
    "slim": 1180
  },
  "version": 1
}
