Head to head · Agent tracing · October 2026 research run

HoneyHive vs Respan API + MCP

Respan API + MCP scores 73.9 (BB) on agent readiness against HoneyHive's 53 (D), and leads in 6 of 7 scored categories. HoneyHive leads on transparency & trust. Both do agent tracing.

Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons

Which one, for what

HoneyHive D

Best for Teams that want OpenTelemetry tracing and evals with tight key scoping, drive the platform from a CLI and can talk to sales for volume.

Ahead on

  • Transparency & trust, 67 against 59

Watch for

Status page showed its single component in Downtime with 0.000 per cent uptime on 4 November 2026, with no incident history

Respan API + MCP BB

Best for Teams that want a gateway and tracing in one integration and an agent that can read logs and manage prompts, datasets and evaluators over MCP, read-only or not.

Ahead on

  • Reliability, 83 against 39
  • Agent ergonomics, 90 against 63
  • Security & auth, 74 against 61
  • Payments & pricing, 45 against 30
  • Maintenance & community, 85 against 77

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Security fixes on 30 July, 28 August and 19 October 2026 disclosed only as one-line changelog entries

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.

Reliability Respan API + MCP +44

HoneyHive 39

Better Stack page at status.honeyhive.ai with a single component, Backend Platform, and nothing separate for the data plane, control plane or ingestion (12 of 20). On 4 November 2026 the page showed "Some services are down", Backend Platform in Downtime and uptime figures of 0.000, 14.836 and 43.447 per cent, with no incident write-ups readable (its /history path redirects to the page itself). We can't tell whether the monitor watches a retired host, but the vendor's own page shows the figures, so 0. The pricing page publishes 1,000 requests a minute on Free and custom limits on Enterprise, and the changelog gives a 7 MiB ingestion body limit (12). The OpenAPI specs declare no 429 and we found no Retry-After or backoff guidance. The Python SDK has a configurable retry budget (5). Enterprise lists an uptime SLA with service credits, but no SLA document is published, so 0 under this run's reading. API, SDKs and CLI are GA (10).

Respan API + MCP 83

Better Stack page at status.respan.ai with six components (web, logging and gateway, each for the platform and Enterprise) and an incident history page (20). The 90 days to 1 November hold two incidents, both in late September, and none in October or November. The Responses API path through the gateway was affected for OpenAI and Anthropic requests for 13 hours 47 minutes on 26 September, and request logs were delayed across all regions for 1 hour 58 minutes on 29 September. The first affected about 0.5 per cent of OpenAI and Anthropic requests on that path. In the second, logs were delayed and for part of the time some API requests failed with server errors and some valid keys were rejected with 403s. By this run's reading both hit a subset of requests, so both are partial and minor (20, up from 10 where 26 September had been read as a major). Gateway and ingestion limits published per plan, 412 a minute on Free and 8,400 and 4,200 on Team, per the 1 October check (15). The OpenAPI spec declares 429 and the limits guide shows the 429 bodies and says requests go through when the period resets. We found no Retry-After or backoff guidance (10). The pricing page listed a 99.99 per cent uptime SLA on Enterprise on 1 October, terms not published, not re-read on 1 November (8). Gateway, logging and MCP are GA (10). 20 + 20 + 15 + 10 + 8 + 10 = 83.

Agent ergonomics Respan API + MCP +27

HoneyHive 63

No MCP server for platform data. The docs MCP only searches documentation. Event search defaults to 1,000 rows with no field projection, so an agent has to set limit itself (10). Filters, date ranges, limit and page on search (18). Since 24 September a bad key, a revoked key and a missing permission all return the same 404 as a missing resource, which leaves an agent guessing (10). POST /session/start is idempotent on session_id. We found no other idempotency keys (10). Python SDK, TypeScript SDKs and a CLI generated one to one from the specs with agent skills. Few required parameters (15).

Respan API + MCP 90

Since 21 October the hosted MCP server's tools/list shows ten everyday tools (logs, traces, metrics, errors, behaviours, prompts) plus tool_search and tool_run, with listed descriptions cut to 300 characters and full contracts on request (15 for 12 tools). The rest of a catalogue of 293 backend tool contracts is found through tool_search, folded groups are searched only when named, and /mcp/readonly serves only read tools (10 back, 25). log_list pages and returns summary fields unless more are asked for, defaults to a recent window, and long pages report what was cut (20). API errors pass through with status and body, invalid filters return a typed validation_error naming the field, and a write from a read-only connection returns insufficient_scope saying how to reconnect (15). Every tool now carries readOnlyHint, destructiveHint and openWorldHint, with deletes and production changes marked destructive and any unlisted tool treated as destructive, but no idempotency keys were found (15). Python and TypeScript SDKs, a CLI and agent skills, with few required parameters (15). 25 + 20 + 15 + 15 + 15 = 90.

Payments & pricing Respan API + MCP +15

HoneyHive 30

No x402 or other machine payment (0). The only paid plan is Enterprise at a custom price, so there's no public per-unit or plan price (0). The free Developer plan needs no card (20). A person signs up in a browser to get a key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Respan API + MCP 45

No x402 or other machine payment (0). Overage prices published without login, $8 per 100,000 logs and $1 per 1,000 scores on Team (20). The Free plan has 100,000 logs and unlimited seats. The pricing page doesn't say whether a card is needed, so half (10). Keys can be minted by API, but only with an existing Admin key, so a person still signs up in a browser first (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Security & auth Respan API + MCP +13

HoneyHive 61

Five key types. Project keys (hh_), read-only project keys (hh_ro_) since 11 June, fine-grained control plane keys (hh_fgcp_) with chosen permissions and a required expiry of at most 365 days, and ingestion-only keys (hh_ingst_) bound to one project since 17 September, and fine-grained data plane keys (hh_fgdp_) since 5 October. Revocation takes effect within two minutes (30). Read-only and ingestion-only keys give least privilege, and deleting a workspace with active children fails with 409 unless --dangerously-delete-child-scopes is passed (18). Traces hold whatever the application logged, and we found no prompt-injection guidance for agents reading them (3). No audit log found (0). The pricing page claims SOC 2 Type II, GDPR and HIPAA. The Drata trust centre at trust.honeyhive.ai rendered nothing readable to us, there's no security.txt, and the CLI changelog lists "Security fixes" in 1.6.0 without detail (10).

Respan API + MCP 74

API keys carry Read, Write, Gateway and Admin scopes since 25 September, can have an expiry and spend caps, are bound to one project and stop working at once when revoked. The MCP server also takes OAuth, now with mcp:read and mcp:write scopes (30). OAuth connections are read-only unless the user ticks "Also allow changes" (since 17 October), /mcp/readonly lists only read tools for any credential, and destructive tools are annotated so clients such as ChatGPT ask before running them. No confirmation step inside Respan itself (18, as exa-mcp). Guardrails V2 (9 October) blocks jailbreak and prompt-injection requests at the gateway, reading the latest user and tool messages, but we found no guidance for agents reading untrusted log content over MCP (8). Every gateway call is logged against its key. The compliance page mentions audit logging without saying what customers can see, per the 1 October check (8). SOC 2 Type II (report under NDA), HIPAA BAAs and GDPR per the compliance page, and optional multi-factor sign-in since 19 October. No security.txt or SECURITY.md, and security fixes appear in the changelog as one-liners (10). 30 + 18 + 8 + 8 + 10 = 74.

Maintenance & community Respan API + MCP +8

HoneyHive 77

Python SDK 1.8.1 on 2026-10-30 (30). Python SDK 1.6.0, 1.6.1, 1.7.0, 1.8.0 and 1.8.1 and CLI 1.6.0, 1.7.0, 1.8.0 and 1.9.0 since 6 August, and 11 dated product changelog entries from 11 August to 27 October (20). Both SDK and CLI changelogs spell out compatibility changes and deprecations. We didn't load issue reply times (12). The Python SDK is current. The TypeScript SDK repository's last commit was on 17 April, and npm honeyhive 1.0.45 dates from 9 July per the 1 October check (10). The Python SDK repository runs only docs, publish and PR-title workflows, with no test workflow (5).

Respan API + MCP 85

respan-tracing 2.24.0 published from the Apache-2.0 monorepo on 19 October, per its version-sync commit (30). Version-sync commits recording package publishes on 15 days from 7 August to 19 October, and dated changelog entries on 13, 21 and 28 August, 4, 11, 21 and 25 September, and 2, 9 and 19 October (20). The MCP repository took merged pull requests through October, the latest on 29 October. Issue reply times unread (GitHub's pages refuse us). Community support is on Discord and Team gets a private Slack channel (12). Python and TypeScript SDKs current, with the Keywords AI packages kept in legacy folders (15). CI runs types, tests and build on MCP pull requests since 10 October, and the monorepo's workflows run in public (8).

Transparency & trust HoneyHive +8

HoneyHive 67

Closed platform. The Python SDK, CLI and OpenAPI specs are MIT (18). The privacy policy (11 January 2025) covers platform data, defers retention to the pricing page (30 days on Free), names AWS and Stripe and uses standard contractual clauses for EU transfers, per the 1 October check. Self-hosted data-flow docs exist and a DPA is custom on Enterprise (14). 57 operations marked deprecated in the spec, and dated changelog notices for charts (5 October), datasets and datapoints (14 and 21 October) and experiment runs (27 October) that say the old endpoints keep working for now, with no end date. Against that, the v2.0.0 spec of 8 May removed GET /events and nine other operations without deprecation, per its own oasdiff changelog (14). AWS hosting and US transfer stated, no full subprocessor list. The Python SDK sends no usage data of its own, and the TypeScript SDK's PostHog client is commented out (8).

Respan API + MCP 59

Closed platform. The SDK monorepo is Apache-2.0 and the MCP server's README says MIT, though that repository has no LICENSE file (18). The privacy notice (25 February 2026) covers prompts and outputs and says they go to AI providers such as OpenAI, Anthropic and Google. Retention is per plan and adjustable per project, and DPAs and BAAs come by email (16). No deprecation policy found. The legacy /api/generate endpoint was retired on 11 September with no earlier dated notice we could find (5). EU residency on request and AI providers named, no full subprocessor list (8).

Score by category

CategoryWeightHoneyHiveRespan API + MCPEdge
Reliability16%3983Respan API + MCP +44
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8689Respan API + MCP +3
Agent ergonomics13%6390Respan API + MCP +27
Security & auth14%6174Respan API + MCP +13
Payments & pricing10%3045Respan API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7785Respan API + MCP +8
Transparency & trust7%6759HoneyHive +8
Negative events≤15-6-3
TotalD 53/100BB 73.9/100

Facts side by side

FactHoneyHiveRespan API + MCP
KindHTTP APIHTTP API
VendorHoneyHiveRespan (formerly Keywords AI)
Hosted endpointhttps://api.dp1.us.honeyhive.aihttps://api.respan.ai/api
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDK, CLI and OpenAPI specs only, platform closed source)Apache-2.0 (SDKs only, platform closed source)
Tools exposednone12
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-302026-10-19
Terms last updated2025-01-062026-02-25
Privacy policy last updated2025-01-112026-02-25
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity60 npm/wk, 2.1k PyPI/wk270 npm/wk, 13k PyPI/wk
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

HoneyHive

Read-only, ingestion-only and fine-grained API keys, public OpenAPI specs and weekly dated changelogs. The status page showed its single component down on 4 November 2026 with no incident history, and the platform changed error codes and fixed a permission check without advance notice or an advisory.

Respan API + MCP

Project-bound API keys with Read, Write, Gateway and Admin scopes, and since October a hosted MCP server that lists twelve tools, annotates every tool and connects read-only by default. Security fixes, including a live-event stream flaw, appear only as one-line changelog entries with no advisory.

Before you call either

HoneyHive

  1. Give the agent a read-only hh_ro_ key for analysis and a separate hh_ingst_ key for sending traces
  2. Treat a 404 as possibly a bad, revoked or expired key or a missing permission before assuming the record is missing
  3. Call the project-scoped /v1/projects/{project_id}/... routes with a data plane key. The unscoped routes are deprecated
  4. Set limit on POST /v1/events/search. The default is 1,000 rows
  5. Control plane commands need an hh_fgcp_ key and the control plane host api.cp.us.honeyhive.ai

Respan API + MCP

  1. Connect to https://mcp.respan.ai/mcp/readonly for agents that only analyse logs, or use a key with only the Read scope
  2. Call tool_search with resource and action words to find tools that aren't listed, then tool_run with the returned schema
  3. Pass filters to log_list rather than paging through everything. The default window is recent
  4. Call project_list first when results look empty over OAuth. Every tool acts on the active project only
  5. Append .md to any docs URL for clean Markdown

Questions

Which is better for AI agents, HoneyHive or Respan API + MCP?

Respan API + MCP scores 73.9 (BB) on agent readiness against HoneyHive's 53 (D), and leads in 6 of 7 scored categories. HoneyHive leads on transparency & trust.

Do HoneyHive and Respan API + MCP need an API key?

HoneyHive needs an API key. Respan API + MCP takes an API key or an OAuth sign-in.

Can an agent call HoneyHive and Respan API + MCP without installing anything?

Yes. HoneyHive has a hosted endpoint at https://api.dp1.us.honeyhive.ai and Respan API + MCP at https://api.respan.ai/api.

Other comparisons with HoneyHive or Respan API + MCP

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.