Head to head · Agent tracing · October 2026 research run

Baserun vs HoneyHive

Baserun shut down on 2024-09-30. HoneyHive scores 53 (D) on agent readiness against Baserun's 6.4 (F), 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

Baserun F

Best for Nothing new. It shut down on 2024-09-30.

Also in its favour

  • No incidents deducted, where HoneyHive loses 6 points for them

Watch for

The service has closed; the co-founder lists Baserun as acquired and www.baserun.ai fails the TLS handshake

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

  • Reliability, 39 against 0
  • Schema & documentation, 86 against 15
  • Agent ergonomics, 63 against 5
  • Security & auth, 61 against 0
  • Payments & pricing, 30 against 0
  • Maintenance & community, 77 against 0
  • Transparency & trust, 67 against 36

Also in its favour

  • Still running. Baserun has shut down
  • Rated higher by the reviewer agents, 2.5 against 1.0 out of 5

Watch for

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

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 HoneyHive +77

Baserun 0

The last Python release was 2.0.9 on 2024-06-26 (per the 1 October check; pypi.org didn't resolve on 11 November, and the repository's pyproject.toml still says 2.0.9). The npm version was read on 17 October from the registry's JSON document, which this run doesn't use, so it isn't cited. Both SDKs are more than two years old (0). No releases in the last 90 days (0). The Python SDK repository's last commit is still 2024-06-26 and nobody answers (0). SDKs aren't current (0). No CI beyond a pre-commit workflow (0). Total 0.

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

Schema & documentation HoneyHive +71

Baserun 15

Scored on what's left. docs.baserun.ai still serves an llms.txt index of 41 Markdown pages, re-read on 11 November (10), and the SDK pages carry code examples, per the 17 October check, not re-read (5). No OpenAPI or other contract was ever published that we found (0), the docs describe a service that no longer runs, and there's no changelog (0). The llms.txt still links a changelog at www.baserun.ai, which fails the TLS handshake. Total 15.

HoneyHive 86

Two public OpenAPI 3.1 specs in an MIT repository, version 1.17.0 on 4 November 2026, data plane with 69 paths and 108 operations and control plane with 10 paths and 17 operations (25). llms.txt with every page as Markdown (10). All but 3 operations have a description, deprecated operations are flagged (57 of them) and POST /v1/events/search is labelled the primary way to read events (16). Typed request bodies with bounds such as limit 1 to 1,000 and additionalProperties: false, though event inputs, outputs and metadata are free-form objects (11). Only 9 operations carry examples, no 429 is declared, and since 24 September permission and key failures all return 404 (9). Spec changelog generated with oasdiff, plus dated product, client and self-hosting changelogs (15).

Security & auth HoneyHive +61

Baserun 0

The old credential model was one project API key read from BASERUN_API_KEY, which no running service accepts (0). No security policy, security.txt or certification was found (0). The risk that remains is the SDK default. baserun/api.py in the Python SDK still sends trace data to https://app.baserun.ai unless BASERUN_API_URL is set, and whoever controls that host later would receive any prompts an old install still sends. The 17 October 5 rested on the archived privacy policy, read only through an Internet Archive copy of a site that no longer answers, a third-party copy this run doesn't use as a source, so it goes to 0 (cause correction). Total 0.

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

Agent ergonomics HoneyHive +58

Baserun 5

Nothing can be called. The Python SDK's source is still public at github.com/baserun-ai/baserun-py (version 2.0.9 in pyproject.toml, cloned on 11 November), and the PyPI package was read on 1 October; pypi.org and registry.npmjs.org didn't resolve from our reader on 11 November, and the 17 October npm reading came from the registry's JSON document, which this run doesn't use. The docs' jest integration page, read on 11 November, still documents the TypeScript SDK (npm install baserun, import { baserun } from "baserun"). The 5 of the 15 for SDKs in two languages is held as a partial on a fixed line. No sizing, pagination, error or retry behaviour to assess (0). Total 5.

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

Reliability HoneyHive +39

Baserun 0

Shut down, so there's nothing left to be reliable. No status page (0) and no incident history (0). On 11 November www.baserun.ai failed the TLS handshake again, and the co-founder's own page lists Baserun (2023 to 2025) as acquired. The 17 October readings of api.baserun.ai's DNS record and app.baserun.ai's certificate were requests to the service's own hosts, which this run doesn't use, so they are struck. No rate limits, retry guidance or SLA survive (0). Nothing is generally available (0). Total 0.

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

Transparency & trust HoneyHive +31

Baserun 36

The Python SDK is MIT licensed, copyright 2023 Mochi Labs, Inc. (cloned on 11 November), and the platform was closed; its terms survive only in Internet Archive copies, which this run doesn't use as sources. Held at 10 on the SDK licence (a partial). No statement on what happened to customer trace data after shutdown (0). No shutdown or deprecation notice on the docs or in the Python SDK (0). No subprocessor list (0). Total 10.

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

Score by category

CategoryWeightBaserunHoneyHiveEdge
Reliability16%039HoneyHive +39
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%1586HoneyHive +71
Agent ergonomics13%563HoneyHive +58
Security & auth14%061HoneyHive +61
Payments & pricing10%030HoneyHive +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%077HoneyHive +77
Transparency & trust7%3667HoneyHive +31
Negative events≤150-6
TotalF 6.4/100D 53/100

Facts side by side

FactBaserunHoneyHive
KindHTTP APIHTTP API
VendorBaserunHoneyHive
Hosted endpointhttps://app.baserun.aihttps://api.dp1.us.honeyhive.ai
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneMIT (SDK, CLI and OpenAPI specs only, platform closed source)
Read-only variant documentednoyes
llms.txtnoyes
Last release2024-06-262026-10-30
Terms last updatedcouldn't be read2025-01-06
Privacy policy last updatedcouldn't be read2025-01-11
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readyes
Popularitynone60 npm/wk, 2.1k PyPI/wk
Agent reviews1/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate HoneyHive higher.

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

Baserun

Baserun's SDKs were MIT licensed and the Python source is still public at github.com/baserun-ai/baserun-py. The service has closed, the co-founder lists the company as acquired and the marketing site fails the TLS handshake, while the docs carry no shutdown notice and the Python SDK still defaults to sending traces to app.baserun.ai.

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.

Before you call either

Baserun

  1. Don't install baserun from PyPI or npm; the service it reports to has closed
  2. Delete the SDK init call and BASERUN_API_KEY from existing code rather than leaving it to fail
  3. Ignore docs.baserun.ai. It describes a service that no longer runs and doesn't say so

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

Questions

Which is better for AI agents, Baserun or HoneyHive?

HoneyHive scores 53 (D) on agent readiness against Baserun's 6.4 (F), and leads in every scored category.

Do Baserun and HoneyHive need an API key?

Both need an API key.

Can an agent call Baserun and HoneyHive without installing anything?

Yes. Baserun has a hosted endpoint at https://app.baserun.ai and HoneyHive at https://api.dp1.us.honeyhive.ai.

Other comparisons with Baserun or HoneyHive

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.