{
  "data": {
    "a": {
      "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
      }
    },
    "answer": "Hyperresearch scores 68.1 (B) on agent readiness against Mojeek Web Search API's 37.6 (F), and leads in 6 of 7 scored categories. Mojeek Web Search API leads on reliability.",
    "b": {
      "slug": "mojeek",
      "name": "Mojeek Web Search API",
      "vendor": "Mojeek Limited",
      "vendorUrl": "https://www.mojeek.com/services/search/web-search-api/",
      "company": "mojeek.com",
      "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": 37.6,
        "grade": "F",
        "agentReady": false,
        "rank": 1412,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 26,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 10,
          "payments": 30,
          "reliability": 45,
          "schema": 29,
          "security": 15,
          "transparency": 68
        },
        "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": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 37.6
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 10,
          "payments": 30,
          "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",
          "lastMoved": "2026-11-13",
          "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-18T18:52:58.317466725Z"
        },
        "securityTxt": {
          "url": "https://mojeek.com/.well-known/security.txt",
          "state": "valid",
          "checkedAt": "2026-11-18T16:30:52.5469083Z"
        },
        "domain": {
          "domain": "mojeek.com",
          "registered": "2004-09-30",
          "source": "https://rdap.verisign.com/com/v1/domain/mojeek.com",
          "checkedAt": "2026-11-15T15:19:32.384329386Z"
        },
        "pages": [
          {
            "url": "https://www.mojeek.com/about/privacy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T22:06:15.684106718Z",
            "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-18T22:06:13.520581888Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "f593843e677e"
          }
        ],
        "updatedAt": "2026-11-18T22:06:15.684106718Z"
      }
    },
    "edges": [
      {
        "by": 78,
        "category": "maintenance",
        "leads": "hyperresearch",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "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": 88,
          "b": 10
        }
      },
      {
        "by": 64,
        "category": "security",
        "leads": "hyperresearch",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "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": 79,
          "b": 15
        }
      },
      {
        "by": 47,
        "category": "schema",
        "leads": "hyperresearch",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "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": 76,
          "b": 29
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "hyperresearch",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "No x402, MPP or L402 (0). Per-request prices published without login, £2 and £3 per 1,000 requests (20). The FAQ says a free credit comes with the Startup plan, but a bank card is required to open an account (0). A person signs up in a browser and adds a card (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30."
        },
        "scores": {
          "a": 60,
          "b": 30
        }
      },
      {
        "by": 17,
        "category": "ergonomics",
        "leads": "hyperresearch",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Answers is three compact tools (`data_and_web_answer`, `data_and_web_search` and the free `get_pending_answer`), and an answer returns only a short answer, its quotes and links. The research server's tools (`start_run`, `run_status`, `run_result`, `search_notes`, `read_note`, `verify_citations`, project tools and more) weren't counted, since `tools/list` needs a token (20 of 25). `max_results` on search, list endpoints for runs, projects, notes and calls, vault search by full text or meaning, and runs polled or streamed (14 of 20). Every 4xx and 5xx uses one envelope with `code`, `message`, `retryable`, `retry_after`, `param` and `request_id` (20). `Idempotency-Key` on writes with documented replay and 409 `idempotency_in_flight`, and a failed call on their side costs nothing. MCP tool annotations weren't readable (14 of 20). Only a query and a tier are required to start a run. Packages for the Vercel AI SDK and LangChain in Python and JavaScript (15). 20+14+20+14+15 = 83.",
          "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": 83,
          "b": 66
        }
      },
      {
        "by": 10,
        "category": "reliability",
        "leads": "mojeek",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "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": 35,
          "b": 45
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Hyperresearch",
        "b": "Mojeek Limited",
        "name": "Vendor"
      },
      {
        "a": "https://answers.hyperresearch.ai/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "$0.05 per call",
        "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": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "ai.hyperresearch/answers",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-16",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2026-11-17",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-17",
        "b": "2022-02-02",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Hyperresearch scores 68.1 (B) on agent readiness against Mojeek Web Search API's 37.6 (F), and leads in 6 of 7 scored categories. Mojeek Web Search API leads on reliability.",
        "question": "Which is better for AI agents, Hyperresearch or Mojeek Web Search API?"
      },
      {
        "answer": "Hyperresearch takes an API key or an OAuth sign-in. Mojeek Web Search API needs an API key.",
        "question": "Do Hyperresearch and Mojeek Web Search API need an API key?"
      },
      {
        "answer": "Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp. No hosted endpoint is listed for Mojeek Web Search API.",
        "question": "Can an agent call Hyperresearch and Mojeek Web Search API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 76 against 29",
          "Agent ergonomics, 83 against 66",
          "Security \u0026 auth, 79 against 15",
          "Payments \u0026 pricing, 60 against 30",
          "Maintenance \u0026 community, 88 against 10"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "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"
      },
      {
        "aheadOn": [
          "Reliability, 45 against 35"
        ],
        "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": {
      "hyperresearch": null,
      "mojeek": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.2,
          "from": 36.4,
          "fromGrade": "F",
          "to": 37.6,
          "toGrade": "F"
        }
      ]
    },
    "job": {
      "capability": "web.search",
      "name": "Web search"
    },
    "others": [
      {
        "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/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-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-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/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-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/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-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/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-hyperresearch.json",
        "title": "DeepSeek Search and Fetch API vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch"
      },
      {
        "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/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/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-hyperresearch.json",
        "title": "Firecrawl MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch"
      },
      {
        "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/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-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/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/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/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": 10,
        "edge": "mojeek",
        "hyperresearch": 35,
        "key": "reliability",
        "mojeek": 45,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 47,
        "edge": "hyperresearch",
        "hyperresearch": 76,
        "key": "schema",
        "mojeek": 29,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 17,
        "edge": "hyperresearch",
        "hyperresearch": 83,
        "key": "ergonomics",
        "mojeek": 66,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 64,
        "edge": "hyperresearch",
        "hyperresearch": 79,
        "key": "security",
        "mojeek": 15,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 30,
        "edge": "hyperresearch",
        "hyperresearch": 60,
        "key": "payments",
        "mojeek": 30,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 78,
        "edge": "hyperresearch",
        "hyperresearch": 88,
        "key": "maintenance",
        "mojeek": 10,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 3,
        "edge": "hyperresearch",
        "hyperresearch": 71,
        "key": "transparency",
        "mojeek": 68,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Hyperresearch scores 68.1 (B) on agent readiness against Mojeek Web Search API's 37.6 (F), and leads in 6 of 7 scored categories. Mojeek Web Search API leads on reliability. Both do web search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "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.",
      "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/hyperresearch-vs-mojeek",
    "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.min.md"
  },
  "markdown": "Hyperresearch scores 68.1 (B) on agent readiness against Mojeek Web Search API's 37.6 (F), and leads in 6 of 7 scored categories. Mojeek Web Search API leads on reliability. Both do web search.\n\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- Mojeek Web Search API: grade F, 37.6/100, rank #1412 of 1557. 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 353 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\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 29\n- Agent ergonomics, 83 against 66\n- Security \u0026 auth, 79 against 15\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 88 against 10\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\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### 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- Reliability, 45 against 35\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: Hyperresearch +78\n\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- 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: Hyperresearch +64\n\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- 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### Schema \u0026 documentation: Hyperresearch +47\n\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- 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### Payments \u0026 pricing: Hyperresearch +30\n\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- Mojeek Web Search API (30): No x402, MPP or L402 (0). Per-request prices published without login, £2 and £3 per 1,000 requests (20). The FAQ says a free credit comes with the Startup plan, but a bank card is required to open an account (0). A person signs up in a browser and adds a card (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.\n\n### Agent ergonomics: Hyperresearch +17\n\n- Hyperresearch (83): Answers is three compact tools (`data_and_web_answer`, `data_and_web_search` and the free `get_pending_answer`), and an answer returns only a short answer, its quotes and links. The research server's tools (`start_run`, `run_status`, `run_result`, `search_notes`, `read_note`, `verify_citations`, project tools and more) weren't counted, since `tools/list` needs a token (20 of 25). `max_results` on search, list endpoints for runs, projects, notes and calls, vault search by full text or meaning, and runs polled or streamed (14 of 20). Every 4xx and 5xx uses one envelope with `code`, `message`, `retryable`, `retry_after`, `param` and `request_id` (20). `Idempotency-Key` on writes with documented replay and 409 `idempotency_in_flight`, and a failed call on their side costs nothing. MCP tool annotations weren't readable (14 of 20). Only a query and a tier are required to start a run. Packages for the Vercel AI SDK and LangChain in Python and JavaScript (15). 20+14+20+14+15 = 83.\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### Reliability: Mojeek Web Search API +10\n\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- 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## Score by category\n\n| Category | Weight | Hyperresearch | Mojeek Web Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 35 | 45 | Mojeek Web Search API +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 76 | 29 | Hyperresearch +47 |\n| Agent ergonomics | 13% | 83 | 66 | Hyperresearch +17 |\n| Security \u0026 auth | 14% | 79 | 15 | Hyperresearch +64 |\n| Payments \u0026 pricing | 10% | 60 | 30 | Hyperresearch +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 88 | 10 | Hyperresearch +78 |\n| Transparency \u0026 trust | 7% | 71 | 68 | Hyperresearch +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.1 · B** | **37.6 · F** | |\n\n## Facts side by side\n\n| Fact | Hyperresearch | Mojeek Web Search API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Hyperresearch | Mojeek Limited |\n| Hosted endpoint | `https://answers.hyperresearch.ai/mcp` | no (local only) |\n| Transports | Streamable HTTP |  |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $0.05 per call | $2.68 per 1,000 requests |\n| x402 | no | no |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | `ai.hyperresearch/answers` | not listed |\n| Last release | 2026-11-16 | none |\n| Terms last updated | 2026-11-17 | no date given |\n| Privacy policy last updated | 2026-11-17 | 2022-02-02 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## How the scores have moved\n\n### Hyperresearch\n\nNo score change since it was listed.\n\n### Mojeek Web Search API\n\n- +1.2 on 13 November 2026: checklist\n\n## Verdicts\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**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### 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### 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, Hyperresearch or Mojeek Web Search API?\n\nHyperresearch scores 68.1 (B) on agent readiness against Mojeek Web Search API's 37.6 (F), and leads in 6 of 7 scored categories. Mojeek Web Search API leads on reliability.\n\n### Do Hyperresearch and Mojeek Web Search API need an API key?\n\nHyperresearch takes an API key or an OAuth sign-in. Mojeek Web Search API needs an API key.\n\n### Can an agent call Hyperresearch and Mojeek Web Search API without installing anything?\n\nHyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp. 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/hyperresearch-vs-mojeek.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hyperresearch\", \"b\": \"mojeek\"}`. From a terminal: `anchor compare hyperresearch mojeek`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hyperresearch.json and https://www.anchorterminal.com/api/v1/tools/mojeek.json\n\n## Other comparisons with Hyperresearch or Mojeek Web Search API\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch](https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.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 Mojeek Web Search API](https://www.anchorterminal.com/compare/arcmira-vs-mojeek.md)\n- [Grounding with Bing Search vs Hyperresearch](https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.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 Hyperresearch](https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch.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 Hyperresearch](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.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 Hyperresearch](https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.md)\n- [DeepSeek Search and Fetch API vs Mojeek Web Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.md)\n- [Exa API + MCP vs Hyperresearch](https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.md)\n- [Exa API + MCP vs Mojeek Web Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-mojeek.md)\n- [Firecrawl MCP vs Hyperresearch](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.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- [Hyperresearch vs Kagi Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.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- [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- [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- [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": "Hyperresearch vs Mojeek Web Search API",
        "url": ""
      }
    ],
    "description": "Hyperresearch scores 68.1 (B) to Mojeek Web Search's 37.6 (F) for web search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Hyperresearch B 68.1",
      "Mojeek Web Search API F 37.6",
      "scores"
    ],
    "h1": "Hyperresearch vs Mojeek Web Search API",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/hyperresearch-vs-mojeek",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Hyperresearch vs Mojeek Web Search for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek"
  },
  "tokens": {
    "markdown": 5650,
    "slim": 1080
  },
  "version": 1
}
