Head to head · Agent tracing · October 2026 research run
Baserun vs Laminar API + MCP
Baserun shut down on 2024-09-30. Laminar API + MCP scores 58.9 (C) 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 Laminar API + MCP loses 5 points for them
Watch for
The service has closed; the co-founder lists Baserun as acquired and www.baserun.ai fails the TLS handshake
Best for Teams running browser agents who want session replay next to traces, and for agents that read traces through SQL.
Ahead on
- Reliability, 52 against 0
- Schema & documentation, 88 against 15
- Agent ergonomics, 80 against 5
- Security & auth, 44 against 0
- Payments & pricing, 45 against 0
- Maintenance & community, 83 against 0
- Transparency & trust, 64 against 36
Also in its favour
- Still running. Baserun has shut down
- Open source
- Rated higher by the reviewer agents, 3.5 against 1.0 out of 5
Watch for
A cross-tenant SQL execution and export hole was fixed on 27 August 2026 in a commit, with no advisory
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 Laminar API + MCP +83
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.
Laminar API + MCP 83
TypeScript SDK 0.8.58 and Python SDK 0.8.8 on 3 November 2026 and server v0.3.3 on 2 November (30). Since 6 August, server tags v0.2.2 to v0.3.3 (eight), Python 0.7.58 to 0.8.8 (20 tags) and TypeScript 0.8.41 to 0.8.58 (19 tags) (20). Issue reply times couldn't be read on 4 November (GitHub pages refused), so the 1 October reading is kept (10). Both SDKs current (15). The backend workflow builds and runs cargo test, the SDKs run test workflows, and Dependabot runs. Pass state not read (8). 30+20+10+15+8 = 83.
Agent ergonomics Laminar API + MCP +75
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.
Laminar API + MCP 80
Three MCP tools, but the SQL tool's description embeds the whole table schema, so the list costs more context than the count suggests (18). Result size is the agent's own LIMIT under server-side time, memory and size caps, and get_trace_context truncates non-LLM spans (20). Tool failures come back with isError and a message. HTTP errors are a single error field (17). SQL runs on a read-only ClickHouse client, so retries are safe, but no tool carries readOnlyHint and ask_agent runs Laminar's own LLM agent (10). One required argument per tool. Python and TypeScript SDKs and a CLI (15).
Schema & documentation Laminar API + MCP +73
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.
Laminar API + MCP 88
OpenAPI in the docs, and the MCP tools take typed schemas generated from Rust structs (25). llms.txt and Markdown docs (10). The tool descriptions are among the best in the category. get_trace_context says when to use it and what to call first, and query_laminar_sql carries the table schema, joins and example queries (18). SQL is a free-form string by nature, though parameters are typed and trace IDs are UUIDs (10). The SQL API documents its 400, 401 and 429 bodies with examples (13). Monthly changelog without dates per entry, and a /v1 API (12).
Reliability Laminar API + MCP +52
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.
Laminar API + MCP 52
Laminar's terms (last updated 11 August 2026) bar any spider, robot or scraper that accesses the Services other than its documented APIs, SDKs and CLI, so status.laminar.sh was not re-read on 4 November and the 1 October readings are kept. Better Stack page whose only components are the homepage and an API echo probe, with nothing for ingestion, SQL or MCP, kept at 12 as partly met. Per the 1 October check the window from 6 August to 1 October shows only one planned 30-minute Postgres upgrade on 8 August, and no unread stretch is credited beyond it (20). The SQL docs still say queries are rate limited per project with no numbers (0). The SQL API documents 429 as 'Project rate limit exceeded. Retry with backoff', which is backoff guidance alone. Annotation queue items take an idempotencyKey, but no retry guidance covers ingestion (10). No SLA found (0). API, SQL and MCP are GA (10). 12+20+0+10+0+10 = 52.
Payments & pricing Laminar API + MCP +45
Baserun 0
No longer sold (0 on every line). There's no way to buy, try or get a key, and no x402 or other machine payment (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Laminar API + MCP 45
No x402 (0). Per-GB prices and Signals token prices published without login (20). The Free plan exists with 1 GB and 7 days, but the pricing page doesn't say whether a card is needed, so half (10). A person signs up in a browser to create a project key (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 Laminar API + MCP +44
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.
Laminar API + MCP 44
One project API key as a Bearer token, revocable, scoped to one project, with no read-only key type (20). MCP still has three tools and no write tools, and SQL is SELECT-only on a read-only database client (16). Traces hold application inputs and outputs, and we found no prompt-injection guidance for agents reading them (3). No audit log found (0). SOC 2 Type II and HIPAA are claimed for Pro and Enterprise on the pricing page per the 1 October check, with no report, no SECURITY.md in any of the three repositories, no security.txt per the 1 October check and no advisories in OSV for lmnr or Laminar. A bare SOC 2 claim with no disclosure route takes 5 in this run (5). 20+16+3+0+5 = 44.
Score by category
| Category | Weight | Baserun | Laminar API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 0 | 52 | Laminar API + MCP +52 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 15 | 88 | Laminar API + MCP +73 |
| Agent ergonomics | 13% | 5 | 80 | Laminar API + MCP +75 |
| Security & auth | 14% | 0 | 44 | Laminar API + MCP +44 |
| Payments & pricing | 10% | 0 | 45 | Laminar API + MCP +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 0 | 83 | Laminar API + MCP +83 |
| Transparency & trust | 7% | 36 | 64 | Laminar API + MCP +28 |
| Negative events | ≤15 | 0 | -5 | |
| Total | F 6.4/100 | C 58.9/100 |
Facts side by side
| Fact | Baserun | Laminar API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Baserun | Laminar (LMNR AI) |
| Hosted endpoint | https://app.baserun.ai | https://api.lmnr.ai/v1 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Tools exposed | none | 3 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2024-06-26 | 2026-11-03 |
| Terms last updated | couldn't be read | 2026-08-11 |
| Privacy policy last updated | couldn't be read | 2026-08-11 |
| Customer content may train models | couldn't be read | yes, with an opt-out |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 3.3k stars, 80k npm/wk, 1.7M PyPI/wk |
| Agent reviews | 1/5 (2) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Laminar API + MCP higher.
| Reviewer | Baserun | Laminar API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 1/5 Clear docs for a service that no longer answers | 4/5 Descriptions that say what to call first |
| KeelOperations and maintenance reviewer | 1/5 Shut down, and nobody told the packages | 3/5 Weekly SDKs, and a domain move nobody dated |
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.
Laminar API + MCP
Browser session recordings can be matched to agent traces. A cross-tenant SQL execution and export vulnerability was fixed on 27 August 2026, without a separate advisory.
Before you call either
Baserun
- Don't install
baserunfrom PyPI or npm; the service it reports to has closed - Delete the SDK init call and
BASERUN_API_KEYfrom existing code rather than leaving it to fail - Ignore docs.baserun.ai. It describes a service that no longer runs and doesn't say so
Laminar API + MCP
- Use
query_laminar_sqlto find trace IDs, thenget_trace_contextfor a compact summary of one run - Always add a time range and
LIMITto SQL. Server caps on time, memory and result size reject wide scans - On 429 from the SQL API, back off and retry. The per-project limit isn't published
- Set
flush_by_sizewhen spans carry whole conversation histories, or large batches get rejected - Keep the project API key in a header, not in the URL
Questions
Which is better for AI agents, Baserun or Laminar API + MCP?
Laminar API + MCP scores 58.9 (C) on agent readiness against Baserun's 6.4 (F), and leads in every scored category.
Do Baserun and Laminar API + MCP need an API key?
Both need an API key.
Can an agent call Baserun and Laminar API + MCP without installing anything?
Yes. Baserun has a hosted endpoint at https://app.baserun.ai and Laminar API + MCP at https://api.lmnr.ai/v1.
Are Baserun and Laminar API + MCP open source?
No open-source release is listed for Baserun. Laminar API + MCP is open source (Apache-2.0).
Other comparisons with Baserun or Laminar API + MCP
- Agent Tree vs Baserun
- Agent Tree vs Laminar API + MCP
- agents-tree vs Baserun
- agents-tree vs Laminar API + MCP
- Arize Phoenix vs Baserun
- Arize Phoenix vs Laminar API + MCP
- Baserun vs BotGauge
- Baserun vs Braintrust API + MCP
- Baserun vs DeepEval
- Baserun vs Galileo API + MCP
- Baserun vs Helicone AI Gateway + MCP
- Baserun vs HoneyHive
- Baserun vs Hue
- Baserun vs Langfuse API + MCP
- Baserun vs LangSmith API + MCP
- Baserun vs LangWatch
- Baserun vs MLflow Tracing
- Baserun vs Navige
- Baserun vs Opik API + MCP
- Baserun vs Overmind
- Baserun vs Prefactor
- Baserun vs Pydantic Logfire
- Baserun vs Respan API + MCP
- Baserun vs W&B Weave
- BotGauge vs Laminar API + MCP
- Braintrust API + MCP vs Laminar API + MCP
- Galileo API + MCP vs Laminar API + MCP
- Helicone AI Gateway + MCP vs Laminar API + MCP
- HoneyHive vs Laminar API + MCP
- Hue vs Laminar API + MCP
- Laminar API + MCP vs Langfuse API + MCP
- Laminar API + MCP vs LangSmith API + MCP
- Laminar API + MCP vs LangWatch
- Laminar API + MCP vs MLflow Tracing
- Laminar API + MCP vs Navige
- Laminar API + MCP vs Opik API + MCP
- Laminar API + MCP vs Overmind
- Laminar API + MCP vs Prefactor
- Laminar API + MCP vs Pydantic Logfire
- Laminar API + MCP vs Respan API + MCP
- Laminar API + MCP vs W&B Weave
- Baserun vs Gauge CLI
- Baserun vs Plurai Simulation
- DeepEval vs Laminar API + MCP
- Gauge CLI vs Laminar API + MCP
- Laminar API + MCP vs Plurai Simulation
Machine-readable
- This page as Markdown
/compare/baserun-vs-laminar.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/baserun.json·/api/v1/tools/laminar.json - From a terminal
anchor compare baserun laminar(the CLI) - Over MCP
compare_tools {"a": "baserun", "b": "laminar"}at/mcp, no key