Head to head · Web search · October 2026 research run

Hyperresearch vs SearchAPI.io

Hyperresearch scores 68.1 (B) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io leads on reliability. Both do web search.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Hyperresearch B

Best for Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.

Ahead on

  • Schema & documentation, 76 against 59
  • Agent ergonomics, 83 against 52
  • Security & auth, 79 against 28
  • Payments & pricing, 60 against 45
  • Maintenance & community, 88 against 0
  • Transparency & trust, 71 against 62

Watch for

No status page, and the terms say there is no SLA and no uptime figure

SearchAPI.io D

Best for Agents that need parsed results from many engines, especially shopping, ads, travel and social sources, at a low price per search.

Ahead on

  • Reliability, 90 against 35

Watch for

MCP loads one tool per engine with no toolsets

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Hyperresearch +88

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.

SearchAPI.io 0

No changelog (/changelog answered 404 on 4 November 2026) and no dated API change found, so the last release can't be dated (0). No releases to count (0). No public issue tracker or changelog to judge replies by. A Discord server is linked from the footer and wasn't tested (0). The 15 for io.searchapi/mcp in the official MCP registry rested on a reading of the registry's JSON API, which this run doesn't use, and no ordinary registry page shows the entry, so the line falls to 0, as graphiti, linear-mcp and copilot-studio-mcp read it. No official SDKs were found; the footer links a GitHub organisation whose pages answered 403 (0, 15 before). No public packages or CI (0). 0 + 0 + 0 + 0 + 0 = 0.

Reliability SearchAPI.io +55

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.

SearchAPI.io 90

Honeybadger status page at status.searchapi.io with Landing Page and API components and monthly history (20). Re-read on 4 November 2026, it shows no incidents in September, October or November 2026, and its incident feed's newest entry is the 11 February 2026 partial outage, so the window from 6 August is clean (30). The hourly cap is published, 20 per cent of the plan's monthly searches in any hour (15). The OpenAPI file lists a 429 response with an error string, but no Retry-After or backoff guidance was found. The partial 5 is kept pending the founder's rule on in-between values (5). The terms of 11 April 2026 give a 99.9% SLA for all plans with a credit of 100% of the monthly price, and the pricing page lists it on every plan (10). GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.

Security & auth Hyperresearch +51

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 <untrusted-source> 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.

SearchAPI.io 28

API keys with a documented api_key query-string option, and OAuth with expiring, rotating tokens for the MCP. The MCP page, re-read on 4 November 2026, now tells clients to send the token in the X-MCP-Token header and not in a URL. The registry's ?token= reading came from a JSON API this run doesn't use and is struck. The api_key query option stays documented in the API reference. 20 less 10 (10). Every action is a read, and there are no tool subsets (15). Results are third-party snippets and scraped AI answers, with no injection guidance (0). No per-call audit log found. The privacy policy says account logins are logged by IP (0). The trust centre at security.searchapi.io answers robots.txt with an app page, so it was left unread on 4 November 2026. No certifications, bounty or security.txt (404 on 4 November 2026) found. The partial 3 is kept pending the founder's rule on in-between values (3).

Agent ergonomics Hyperresearch +31

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.

SearchAPI.io 52

The MCP exposes over 100 tools, one or more per engine, with no toolsets or filtering documented (5). page, time_period, location, country, language and safe search. Google's num has been fixed at 10 since September 2025 (18). Status codes are documented, but not how to recover from each (12). Searches are reads, and only HTTP 200 responses are billed, so retries are cheap. MCP annotations aren't visible (10). Two required parameters, engine and q. No official SDKs (7).

Schema & documentation Hyperresearch +17

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.

SearchAPI.io 59

OpenAPI 3.0 for the Google engine at /openapi/google.yaml with 25 typed parameters. We found no index of specs for the other engines, so 20 of 25. No llms.txt (404 on 4 November 2026) and no Markdown docs for agents (0). The API reference explains each parameter, and the MCP tool definitions aren't public (10). Enums for device, country, language, safe search and time period (14). Examples and a Postman collection, and the spec documents 400, 401, 403, 429 and 500 (12). /api/v1 in the path and no changelog anywhere we looked (3).

Payments & pricing Hyperresearch +15

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.

SearchAPI.io 45

No x402, MPP or L402 (0). Monthly plans only, priced in public, from $40 for 10,000 searches to $5,000 for 5 million (10). 100 free requests with no card (20). A person has to sign up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Score by category

CategoryWeightHyperresearchSearchAPI.ioEdge
Reliability16%3590SearchAPI.io +55
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7659Hyperresearch +17
Agent ergonomics13%8352Hyperresearch +31
Security & auth14%7928Hyperresearch +51
Payments & pricing10%6045Hyperresearch +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%880Hyperresearch +88
Transparency & trust7%7162Hyperresearch +9
Negative events≤1500
TotalB 68.1/100D 52/100

Facts side by side

FactHyperresearchSearchAPI.io
KindHTTP APIHTTP API
VendorHyperresearchSearchApi
Hosted endpointhttps://answers.hyperresearch.ai/mcphttps://www.searchapi.io/api/v1/search
TransportsStreamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
Price for web search$0.05 per call$4 per 1,000 requests
x402nono
Read-only variant documentednono
llms.txtyesno
MCP registryai.hyperresearch/answersio.searchapi/mcp
Last release2026-11-16none
Terms last updated2026-11-172026-04-11
Privacy policy last updated2026-11-172026-04-11
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviewsnone3/5 (2)

How the scores have moved

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.

SearchAPI.io

A 99.9% SLA in the terms on every plan, no status-page incidents since 11 February 2026, and over 150 engine endpoints behind one URL. The MCP loads one tool per engine with no toolsets, there is no changelog or official SDK, and every account starts with a browser signup.

Before you call either

Hyperresearch

  1. 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
  2. Send an Idempotency-Key on every write and reuse it only with an unchanged body, so a retried run or answer is charged once
  3. 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
  4. If a response has retryable: false, change the request rather than retrying. Branch on error.code, never on the message
  5. Use a key that starts hr_test_ to build and test an integration without spending

SearchAPI.io

  1. Send the key as Authorization: Bearer, not api_key= in the URL
  2. Connect the MCP through OAuth or the X-MCP-Token header. Never put the token in the MCP URL
  3. Call the REST API with engine= when context is tight. The MCP loads one tool definition per engine
  4. Page Google results with page. num is fixed at 10
  5. Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches

Questions

Which is better for AI agents, Hyperresearch or SearchAPI.io?

Hyperresearch scores 68.1 (B) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io leads on reliability.

Do Hyperresearch and SearchAPI.io need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Hyperresearch and SearchAPI.io without installing anything?

Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and SearchAPI.io at https://www.searchapi.io/api/v1/search.

Other comparisons with Hyperresearch or SearchAPI.io

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.