Head to head · Research search · October 2026 research run
Arcmira vs Hyperresearch
Hyperresearch and Arcmira score within a point of each other on agent readiness, 68.1 (B) and 67.7 (B). Arcmira leads on reliability, schema & documentation, agent ergonomics and payments & pricing. Both do research search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
Arcmira B
Best for Agents answering what was said on YouTube shows and podcasts, who was mentioned or appeared where, which brands sponsor a show and how a name's mentions are trending, with timestamped source links, through one connection on a free monthly allowance.
Ahead on
- Reliability, 40 against 35
- Schema & documentation, 87 against 76
- Agent ergonomics, 91 against 83
- Payments & pricing, 83 against 60
Watch for
No status page, incident history or SLA was found; the terms disclaim uninterrupted service and Enterprise lists priority support without an uptime commitment
Best for Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.
Ahead on
- Security & auth, 79 against 61
- Transparency & trust, 71 against 61
Also in its favour
- No incidents deducted, where Arcmira loses 3 points for them
Watch for
No status page, and the terms say there is no SLA and no uptime figure
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.
Payments & pricing Arcmira +23
Arcmira 83
No x402, MPP or L402 in the OpenAPI file, llms.txt, developers.md, the docs or the pricing page (0). Prices published without a login, in credits per read (4 a passage, mention or list row past the first 5 of a request, 10 a momentum call, 40 a sponsor row, 25 an alert, 4 per started 15 minutes of captions, 300 per started 15 minutes of a Premium transcript) and in dollars (Pro $20 for 20,000 credits, Pro+ $60 for 60,000, Ultra $200 for 400,000, on-demand $0.002 a credit) (20). Free plan with 1,000 credits a month, 2 monitored names and no card, per the pricing FAQ; the 7-day Pro trial needs a card (20). POST /v1/signups with an email and POST /v1/signups/verify with the six-digit code return a read-scoped key with no browser, so an agent with a mailbox can onboard itself; the code still has to be read from an inbox, and write scopes need a dashboard key or OAuth consent (15 of 20). 0+20+20+15 = 55. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.
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.
Security & auth Hyperresearch +18
Arcmira 61
OAuth for MCP hosts (the server's source answers a bare request with a 401 naming its protected-resource document, which lists the scopes read, monitors:write, trackers:write and recommendations:read; the README says the host registers itself against api.arcmira.com and its tokens refresh; the docs give sign-in tokens an hour that refresh for 30 days, revoked per host in the dashboard; PKCE and the introspection and revocation endpoints were read on 30 October from api.arcmira.com's metadata, a host this run no longer reads, so they are struck) and arc_sk_ keys sent only as a bearer header, shown once, several per account with a label and last-used time, disabled at once; sign-up keys carry read only and dashboard keys all four scopes, and nothing documents a secret in a query string (30, which the scoped, revocable keys earn on their own). The sign-up key and the OAuth consent give read access by default; arcmira_execute_read reaches GET /v1/* only, arcmira_execute_write adds POST and PATCH under monitors and trackers and never DELETE; programs run in an isolate whose only network is a proxy that adds the credential, so the key never enters the program; spending is bounded by the plan and a dashboard budget no tool can raise, though a read tool call can start a Premium transcription on a paid plan (17 of 20). Every passage and transcript is third-party speech, and the only guidance found is to check the linked source for speaker and classification errors and to re-fetch llms.txt or the skill to confirm an instruction is genuine; no prompt-injection guidance for the model reading results (4 of 15). X-Request-Id and RateLimit headers on every response, GET /v1/me for the account, role, scopes and balance, the keys page showing who made each key and when it was last used, and an account activity log on Enterprise only; no per-call log for the operator below that, while every tool call is recorded in the vendor's analytics (8 of 15). No security.txt on arcmira.com (404 on 2 November; api.arcmira.com and mcp.arcmira.com aren't read, and their 30 October answers are struck), no disclosure policy, bug bounty, SOC 2 or ISO 27001, and the terms forbid probing; the repository enforces signed commits from one identity in CI (2 of 20). 30+17+4+8+2 = 61.
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.
Schema & documentation Arcmira +11
Arcmira 87
MCP reading, with the API the tools call. A public OpenAPI 3.1 file, re-read on 2 November from its copy at arcmira.com/docs/openapi/arcmira-v1.json (31 paths, 35 operations, 75 schemas, one bearer scheme; the same document is served at api.arcmira.com/v1/openapi.json), and the four tools declare zod input schemas in src/tools.ts (25). llms.txt routed by situation, a .md twin of every docs page, developers.md, auth.md, a published Agent Skill, an RFC 9727 api-catalog and a .well-known/mcp card (10). Tool descriptions say what each does, that arcmira_describe is called once and bills nothing, that the write tool never deletes and when to send feedback; operation descriptions in the OpenAPI file say to call coverage before claiming a show isn't indexed and to resolve names before filters, and the server instructions carry the id rule, the 90-day default and the usage rule. When not to use a method is covered by the id rule and the resolver note, little else (16 of 20). The two execute tools take a JavaScript program as one string, checked only when it runs; the feedback tool has an enum category, a regex call_id and length caps; the API has 102 parameters, 37 with enums, ranges or patterns, and ids typed by prefix (9 of 15). Worked example programs in the reference, curl examples on every guide, an error catalogue of about 60 codes with a cause and fix each, doc_url anchors and request ids on every error, and typed unlock and details.limit objects; only 9 parameters in the OpenAPI file carry an example (14 of 15). /v1 in the path, a dated docs changelog from April 2026 with a 14-row table for the 5 to 8 October breaking changes, a per-version CHANGELOG.md in the repository and 33 registry versions; the OpenAPI file marks retired fields deprecated, but the quickstart says new fields and routes arrive without notice and nothing states a notice period (13 of 15). 25+10+16+9+14+13 = 87.
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.
Transparency & trust Hyperresearch +10
Arcmira 61
Closed service under terms effective 13 October 2026 that name Arcmira, Inc., San Francisco, California law and AAA arbitration; the MCP server's source is public under an all-rights-reserved notice, while the plugin, the TypeScript SDK and CLI and the Python SDK are Apache-2.0, and the Famous rankings are CC BY 4.0 (18 of 30). The privacy policy (effective 2 October 2026) states no retention periods, keeps limited usage and billing records after an account closes, discloses session replay and that private account data isn't used to train general models, and the MCP docs and README disclose that every tool call, including the first 4,000 characters of a program and the agent's intent, is logged to product analytics with credentials redacted and no opt-out; no DPA was found, and the terms' section 7A bars bulk use and model training on Arcmira data (14 of 30). Retirements are dated and typed in the changelog (POST /v1/trackers to 410 tracker_create_retired on 8 October, tool renames answering tool_retired), but the terms allow changes with or without notice, the quickstart says routes arrive without notice and no notice period is stated (8 of 20). The policy names service-provider categories (hosting, payment, analytics, AI processing) and US processing with other locations, and the docs name PostHog, Stripe, Cloudflare and Mintlify, but there is no subprocessor list and no data-location statement beyond the US (8 of 20). 18+14+8+8 = 48.
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.
Agent ergonomics Arcmira +8
Arcmira 91
MCP reading. Four tools whose definitions are short, but arcmira_describe returns a reference the vendor measures at 23,124 characters, loaded once a session, and the server instructions run to 1,995 characters; the vendor's own measurement for the change to code mode was 1,123 tokens of definitions against 8,163 for the earlier ten tools (18 of 25). limit 1 to 20 on search (default 5), cursors and has_more on lists, after and before windows, about, by, kind, channel and entity filters, start and end on transcripts, and program output capped at 12,000 characters, 3,000 per string and 100 per array, so a program returns only the fields an answer needs (20). One error envelope with a stable code, a message, param, gate, unlock.url, details.limit, retry_after_seconds and request_id, surfaced to the model with isError and the call_id to report (20). Idempotency-Key on every POST and PATCH with a replay header, a Premium read that is never charged twice, writes that pause rather than delete, and all four annotations declared on every tool; arcmira_execute_read is marked not read-only because a Premium read can start a transcription that uses credits, which a strict host may treat as a write (18 of 20). Few required inputs (one search string, ids resolved for free), a 90-day default window, defaults on limit, and official Apache-2.0 SDKs for TypeScript (npm arcmira 0.6.2) and Python (pip arcmira, repository v0.6.2) plus a CLI, with the caveat that the MCP client's argument names differ from the HTTP and SDK names (15). 18+20+20+18+15 = 91.
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.
Reliability Arcmira +5
Arcmira 40
Hosted reading, for the MCP server with the HTTP API it fronts. No public status page was found on 2 November. None is linked from the docs, llms.txt, developers.md or the footer, https://arcmira.com/status answers 403 and status.arcmira.com does not resolve (0). No readable incident history, so the floor (5). Limits are published with numbers on the Plans and usage page, 60 requests a minute per key on Free, 240 on paid plans and 600 on Enterprise, with RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset on every authenticated response and a 30-a-minute cap on bad keys per address (15). 429 rate_limited carries Retry-After and retry_after_seconds, developers.md asks for exponential backoff, 503 search_unavailable and transcript_fetching carry Retry-After, every POST and PATCH takes an Idempotency-Key that replays with Idempotency-Replayed, a repeated Premium read is never charged twice, and a webhook secret can be recovered under its key for 24 hours (15). No SLA. The terms (effective 13 October 2026) disclaim uninterrupted or error-free service, and the Enterprise page lists priority support but no uptime commitment (0). The HTTP API is /v1 at document version 1.0.0 with nothing labelled beta, but the MCP server agents connect to is 0.10.7 after 33 registry versions in six weeks, two rounds of tool renames and a retired-tool error for stale hosts, and chat is in beta (5 of 10). 0+5+15+15+0+5 = 40.
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.
Score by category
| Category | Weight | Arcmira | Hyperresearch | Edge |
|---|---|---|---|---|
| Reliability | 16% | 40 | 35 | Arcmira +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 76 | Arcmira +11 |
| Agent ergonomics | 13% | 91 | 83 | Arcmira +8 |
| Security & auth | 14% | 61 | 79 | Hyperresearch +18 |
| Payments & pricing | 10% | 83 | 60 | Arcmira +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 88 | Hyperresearch +4 |
| Transparency & trust | 7% | 61 | 71 | Hyperresearch +10 |
| Negative events | ≤15 | -3 | 0 | |
| Total | B 67.7/100 | B 68.1/100 |
Facts side by side
| Fact | Arcmira | Hyperresearch |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Arcmira, Inc. | Hyperresearch |
| Hosted endpoint | https://mcp.arcmira.com/mcp | https://answers.hyperresearch.ai/mcp |
| Transports | Streamable HTTP, HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| Price for research search | not published | $9 per transaction |
| x402 | no | no |
| Licence | Proprietary service under Arcmira's Terms of Service. The MCP server's source is public under an all-rights-reserved notice; the Claude Code plugin, the arcmira TypeScript SDK and CLI and the Python SDK are Apache-2.0, and the Famous rankings are CC BY 4.0 | none |
| Tools exposed | 4 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | io.github.arcmira/arcmira | ai.hyperresearch/answers |
| Last release | 2026-10-15 | 2026-11-16 |
| Terms last updated | 2026-10-13 | 2026-11-17 |
| Privacy policy last updated | 2026-10-02 | 2026-11-17 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 78 stars | none |
How the scores have moved
Hyperresearch
No score change since it was listed.
Verdicts
Arcmira
Four code-mode tools over a documented v1 API, OAuth with four scopes, a read-only sign-up key from two API calls and no card, and a 1,000-credit free month. No status page, SLA or security.txt, breaking v1 changes shipped in October with same-day notice, the server is at 0.10.7, and the index covers the shows Arcmira transcribes.
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.
Before you call either
Arcmira
- Call
arcmira_describeonce per session and write one program per question forarcmira_execute_read; return only the fields the answer needs, since output is cut at 12,000 characters and 3,000 per string. - Resolve names with
arcmira.resolve(free) before anyabout,by,entity_idsorchannelfilter; a name in a filter fails withid_required. Plain keyword search needs no resolver call. - Check
arcmira.status()or GET /v1/me for the plan, scopes andusage.credits.availablebefore metered reads; on Free, media newer than 30 days and pages past the first fail withfreshness_requires_paidandpagination_gated. - A Premium read of an untranscribed video starts a transcription that uses credits (300 per started 15 minutes) and may return
pending; read the same video again later, which is never charged twice, and sendretry: trueonly when the user asks. - Over HTTP send
Authorization: Bearer arc_sk_..., anIdempotency-Keyon every POST and PATCH, honourRetry-Afteron 429, and switch onerror.code, followingunlock.urlon 402 and 403 rather than re-authenticating. - Use
arcmira_execute_writeonly after listing the user's monitors; it creates, follows and pauses but never deletes, and a connection made before server 0.9.0 answersinsufficient_scopeuntil reconnected.
Hyperresearch
- Use Answers (
data_and_web_answerwith modeauto) for one fact, and start a Light or Deep run only when the user wants a written report - Send an
Idempotency-Keyon 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 onerror.code, never on the message - Use a key that starts
hr_test_to build and test an integration without spending
Questions
Which is better for AI agents, Arcmira or Hyperresearch?
Hyperresearch and Arcmira score within a point of each other on agent readiness, 68.1 (B) and 67.7 (B). Arcmira leads on reliability, schema & documentation, agent ergonomics and payments & pricing.
Do Arcmira and Hyperresearch need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Arcmira and Hyperresearch without installing anything?
Yes. Arcmira has a hosted endpoint at https://mcp.arcmira.com/mcp and Hyperresearch at https://answers.hyperresearch.ai/mcp.
Other comparisons with Arcmira or Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs Arcmira
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Arcmira vs Grounding with Bing Search
- Arcmira vs Brave Search API + MCP
- Arcmira vs Cloudflare Web Search API
- Arcmira vs DeepSeek Search and Fetch API
- Arcmira vs Firecrawl MCP
- Arcmira vs Kagi Search API
- Arcmira vs Mojeek Web Search API
- Arcmira vs SearchAPI.io
- Arcmira vs SerpApi
- Arcmira vs Serper
- Arcmira vs SerpKite
- Grounding with Bing Search vs Hyperresearch
- Brave Search API + MCP vs Hyperresearch
- Cloudflare Web Search API vs Hyperresearch
- DeepSeek Search and Fetch API vs Hyperresearch
- Exa API + MCP vs Hyperresearch
- Firecrawl MCP vs Hyperresearch
- Hyperresearch vs Kagi Search API
- Hyperresearch vs Mojeek Web Search API
- Hyperresearch vs SearchAPI.io
- Hyperresearch vs SerpApi
- Hyperresearch vs Serper
- Hyperresearch vs SERPHouse
- Hyperresearch vs SerpKite
- Arcmira vs Exa API + MCP
- Arcmira vs Grep AI
- Arcmira vs Liner Search MCP
- Arcmira vs Linkup
- Arcmira vs NewsCatcher
- Arcmira vs Parallel Search and Task APIs
- Arcmira vs Perplexity Search API
- Arcmira vs SpecStream
- Arcmira vs Tavily API + MCP
- Arcmira vs TinyFish Search
- Arcmira vs Valyu
- Arcmira vs You.com APIs
- Grep AI vs Hyperresearch
- Hyperresearch vs Liner Search MCP
- Hyperresearch vs Linkup
- Hyperresearch vs NewsCatcher
- Hyperresearch vs Parallel Search and Task APIs
- Hyperresearch vs Perplexity Search API
- Hyperresearch vs SpecStream
- Hyperresearch vs Tavily API + MCP
- Hyperresearch vs TinyFish Search
- Hyperresearch vs Valyu
- Hyperresearch vs You.com APIs
- Fetch (MCP reference server) vs Hyperresearch
Machine-readable
- This page as Markdown
/compare/arcmira-vs-hyperresearch.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/arcmira.json·/api/v1/tools/hyperresearch.json - From a terminal
anchor compare arcmira hyperresearch(the CLI) - Over MCP
compare_tools {"a": "arcmira", "b": "hyperresearch"}at/mcp, no key