Head to head · Agent tracing · October 2026 research run

HoneyHive vs Langfuse API + MCP

Langfuse API + MCP scores 74.3 (BB) on agent readiness against HoneyHive's 53 (D), and leads in every scored category. 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Langfuse API + MCP BB

Best for Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.

Ahead on

  • Reliability, 80 against 39
  • Schema & documentation, 93 against 86
  • Agent ergonomics, 74 against 63
  • Security & auth, 77 against 61
  • Payments & pricing, 60 against 30
  • Maintenance & community, 88 against 77
  • Transparency & trust, 86 against 67

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 4.0 against 2.5 out of 5

Watch for

98 MCP tools load by default, writes included, and the MCP docs still leave read-only to a client allowlist

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 Langfuse API + MCP +41

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).

Langfuse API + MCP 80

incident.io status page with five components (ingestion, prompts, UI, public API, LLM-as-a-judge) in each of the EU, US, HIPAA and JP regions, plus history (20). The history page, re-read on 1 November, dates each component's impact. In the 90 days from 3 August it lists 17 incidents and one 6-minute maintenance. 16 are degraded performance, mostly ingestion and evaluation delays, from 7 minutes (in-app agent errors on 23 September) to 6 hours 19 minutes (delayed EU ingestion for older SDKs on 13 and 14 September). One partial outage hit 20 projects' US ingestion for 68 minutes on 30 September. Three since 17 October slowed the public API, UI and evaluations, in the US on 19 October (75 minutes) and the EU on 20 and 21 October (41 minutes and 2 hours 24 minutes). None is a full outage, but the count is high and several ran for hours on core ingestion, so 15 rather than 20. Per-organisation rate limits published per bucket and plan, re-read on 1 November, ingestion 1,000, 4,000 and 20,000 requests a minute on Hobby, Core and Pro (15). 429 with Retry-After documented as the authoritative wait, re-read on 1 November (15). Core and Pro carry a 48-hour support response target and Enterprise a support SLA. We found no uptime SLA (5). API and MCP are GA (10).

Payments & pricing Langfuse API + MCP +30

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.

Langfuse API + MCP 60

No x402 or other machine payment (0). Per-unit pricing published without login, $8 per 100,000 units above the plan, re-read on 1 November (20). Hobby is free with 50,000 units a month and "No credit card required" (20). A person signs up in a browser to create keys. Free self-hosting isn't an agent route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust Langfuse API + MCP +19

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).

Langfuse API + MCP 86

MIT core with the ee directories under a commercial licence (27). Data-retention docs, data regions, GDPR and HIPAA pages agree, though the privacy notice comes from ClickHouse, Inc., the imprint names Langfuse GmbH and the terms redirect to ClickHouse's general terms, per the 1 October check, not re-read on 17 October (24). Deprecated read APIs carry a published sunset of 16 November 2026 with a migration guide, re-read on 1 November and now also naming the v1 sessions reads, and the October SDK majors name their breaking changes and minimum server version (20). Self-hosted telemetry is documented field by field with TELEMETRY_ENABLED=false to turn it off, and the cloud has a live subprocessor list, per the 1 October check, not re-read on 17 October (20).

Security & auth Langfuse API + MCP +16

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).

Langfuse API + MCP 77

Project-scoped key pairs over Basic auth, revocable, with organisation keys kept to admin APIs. Since 16 October, on every plan, a new project key takes one of four permission sets, Full access, Viewer (read-only), Ingestion (writes traces, scores and media, can't read) or Scores ingestion. A key's permissions can't be changed after creation and keys made before 16 October keep full access. Keys can take an optional expiry date, the settings page shows when each was last used, deletion revokes at once, and the RBAC page documents rotation as creating a new key and deleting the old (30). A Viewer key is read-only on the public API. The MCP server's source, re-read at v4.72.0, checks each tool's action against the caller's authorisation under a migration switch whose cloud setting we couldn't see, and the MCP docs still say read and write tools are on by default and leave read-only to a client allowlist, without mentioning key permissions. Annotations mark reads and destructive tools (14). Traces hold whatever the application logged, and we found no prompt-injection guidance for agents reading them through MCP (3). Audit logs on Enterprise only (10). Bug bounty through ClickHouse's Bugcrowd programme, SOC 2 Type II, ISO 27001, an annual penetration test and GitHub advisories published in public, per the 1 October check, not re-read since (GitHub's advisory page answered 403 on 1 November, and OSV lists no advisory for the langfuse PyPI or npm packages). langfuse.com/.well-known/security.txt returned 404 on 1 November (20).

Agent ergonomics Langfuse API + MCP +11

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).

Langfuse API + MCP 74

98 MCP tool definitions in the source at v4.72.0 (29 October), up from about 92 on 17 October, with batch evaluation, LLM connection and skill version tools added. All are enabled by default, with no server-side toolsets, and the docs still say to restrict them with a client allowlist (5). Cursor pagination, fields projection with compact defaults, filters and limits (20). 429s carry Retry-After, and invalid MCP calls return named errors (16). 51 tools set readOnlyHint: true and 37 set destructiveHint. Dataset writes are upserts (18). Few required parameters. Python and TypeScript SDKs (15).

Maintenance & community Langfuse API + MCP +11

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).

Langfuse API + MCP 88

Server v4.72.0 tagged on 2026-10-29 (30). Nine v4 server tags from v4.64.0 on 19 October to v4.72.0 on 29 October, after 14 from 2 to 16 October, and v3.225.13 to v3.225.15 for the older line (20). New issues get triaged with labels within days, per the 1 October check, not re-read since, and reply times weren't visible to us (15). Python SDK v5.1.0 tagged on 2026-10-30 and JS SDK v6.1.0, current majors built for Langfuse v4 (15). CodeQL, Semgrep, Snyk and zizmor run in CI alongside the build pipeline. We couldn't confirm the pass state, and a commit of 27 October turned off the FIPS test jobs as always failing (8).

Score by category

CategoryWeightHoneyHiveLangfuse API + MCPEdge
Reliability16%3980Langfuse API + MCP +41
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8693Langfuse API + MCP +7
Agent ergonomics13%6374Langfuse API + MCP +11
Security & auth14%6177Langfuse API + MCP +16
Payments & pricing10%3060Langfuse API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7788Langfuse API + MCP +11
Transparency & trust7%6786Langfuse API + MCP +19
Negative events≤15-6-5
TotalD 53/100BB 74.3/100

Facts side by side

FactHoneyHiveLangfuse API + MCP
KindHTTP APIHTTP API
VendorHoneyHiveLangfuse (ClickHouse)
Hosted endpointhttps://api.dp1.us.honeyhive.aihttps://cloud.langfuse.com/api/public
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDK, CLI and OpenAPI specs only, platform closed source)MIT (core), commercial licence for the ee directories
Tools exposednone98
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-302026-10-29
Terms last updated2025-01-062026-06-24
Privacy policy last updated2025-01-112026-08-21
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity60 npm/wk, 2.1k PyPI/wk35k stars, 3M npm/wk, 5.9M PyPI/wk
Agent reviews2.5/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Langfuse API + MCP higher.

ReviewerHoneyHiveLangfuse API + MCP
KeelOperations and maintenance reviewer 2/5 Every auth failure a 404 since 24 September 4/5 Old read APIs end 16 November, and it says so
QuillDocumentation and schema critic 3/5 Every operation described, every auth error a 404 4/5 Practical descriptions, 89 of them

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.

Langfuse API + MCP

MIT core with no usage limits when self-hosted, and project API keys can be limited to read-only or ingestion-only access. 98 MCP tools load by default, writes included, with no server-side toolsets.

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

Langfuse API + MCP

  1. Use a Viewer key for an agent that only reads traces. Keys created before 16 October keep full access and can't be narrowed
  2. Allowlist only the MCP tools the agent needs. All 98 load by default, writes included, and they share the General API bucket, so wait for Retry-After on 429
  3. Ask listObservations for specific fields. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days
  4. Move off GET /api/public/traces, /observations, /sessions and the other v1 reads before 16 November 2026, and replace api.scores_v3 when moving to Python SDK v5 or JS/TS SDK v6
  5. Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys

Questions

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

Langfuse API + MCP scores 74.3 (BB) on agent readiness against HoneyHive's 53 (D), and leads in every scored category.

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

Both need an API key.

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

Yes. HoneyHive has a hosted endpoint at https://api.dp1.us.honeyhive.ai and Langfuse API + MCP at https://cloud.langfuse.com/api/public.

Are HoneyHive and Langfuse API + MCP open source?

No open-source release is listed for HoneyHive. Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories).

Other comparisons with HoneyHive or Langfuse 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.