Head to head · Agent tracing · October 2026 research run

Baserun vs LangSmith API + MCP

Baserun shut down on 2024-09-30. LangSmith API + MCP scores 74.1 (BB) 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 LangSmith API + MCP loses 4 points for them

Watch for

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

LangSmith API + MCP BB

Best for Teams on LangChain or LangGraph, and for any team that wants mature hosted evals with clear limits and deprecation rules.

Ahead on

  • Reliability, 81 against 0
  • Schema & documentation, 86 against 15
  • Agent ergonomics, 76 against 5
  • Security & auth, 79 against 0
  • Payments & pricing, 60 against 0
  • Maintenance & community, 85 against 0
  • Transparency & trust, 78 against 36

Also in its favour

  • Still running. Baserun has shut down
  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.0 against 1.0 out of 5

Watch for

Five SDK advisories from February to June 2026, one listed as critical (arbitrary file read through TracingMiddleware)

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 LangSmith API + MCP +85

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.

LangSmith API + MCP 85

The SDKs moved on 16 October from langsmith-sdk (now archived) to langsmith-python and langsmith-javascript, with the same PyPI and npm packages. Python 0.14.16 on 29 October and JavaScript 0.11.6 dated 31 October in its changelog (30). 31 Python SDK tags in the 90 days to 1 November, 0.10.16 (5 August) to 0.14.16 across the old and new repositories, and JavaScript releases to 0.11.6 (20). Both new repositories take commits daily and auto-label new issues. We didn't load reply times (12). Python and TypeScript SDKs both current (15). CI, release and benchmark workflows run in public in both repositories. Pass state not checked (8). 30+20+12+15+8 = 85.

Reliability LangSmith API + MCP +81

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.

LangSmith API + MCP 81

incident.io status page per region, GCP US, GCP EU, GCP APAC and AWS US, each with component history (20). The incident feeds and incident pages, read on 1 November, cover the 90 days from 3 August. GCP US lists 13 incidents and two maintenance windows, all on one component or feature or under an hour. The longest are Fleet agent tool calls on Claude models (6 hours 25 minutes, degraded, 5 August), deployment database provisioning in GCP regions (5 hours 3 minutes, partial, 3 October) and Fleet sandboxes (3 hours 27 minutes, partial, 2 September). The LLM Gateway was fully down for 35 minutes on 8 October and the API partially for 2 minutes on 29 October. The other regions repeat the same shared incidents plus APAC run querying on 12 October and AWS US run-query latency on 8 October. Minor only (20). Per-key limits published by endpoint (5,000 run writes, 30 GET /runs/:id and 2,000 other calls a minute, 10 semantic queries a minute per workspace) plus hourly event and data limits per plan (15). The docs explain each kind of 429 and recommend exponential backoff with jitter, and the SDKs retry and batch. Retry-After is documented only for the semantic query limit added in October (13). Enterprise has a support SLA. We found no uptime SLA (3). API and remote MCP are GA (10). 20+20+15+13+3+10 = 81.

Security & auth LangSmith API + MCP +79

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.

LangSmith API + MCP 79

Personal access tokens inherit the user's permissions. Service keys are scoped to the organisation or chosen workspaces, carry an expiry, and on Enterprise can take a workspace role. Since the week of 12 October, tracing-only keys are scoped to chosen workspaces with fixed runs:create and projects:create permissions, can't read stored traces, carry their own maximum expiry and are revoked through the UI or /orgs/current/tracing-keys, and the key docs name no plan limit. The remote MCP uses OAuth 2.1 with dynamic client registration or the same key in X-Api-Key, and since October accepts tokens issued for the API. Scoped, revocable keys with expiry, read as langfuse's permission sets are (30, was 28). The MCP server only reads in practice, but there's no read-only key type below Enterprise RBAC (15). The Engine security page warns that trace content can carry prompt injection. The MCP page says nothing about it (6). Audit logs on Enterprise, queryable by API (10). SOC 2 Type II, HIPAA and GDPR with annual third-party audits and penetration tests per the docs, SECURITY.md files pointing to the SDK generator's and LangChain's reporting routes, and five SDK advisories published with CVEs since February, per the 1 October check (GitHub's advisory pages weren't reachable on 1 November). www.langchain.com answers "Invalid .well-known request" for security.txt, so none (18). 30+15+6+10+18 = 79.

Schema & documentation LangSmith API + MCP +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.

LangSmith API + MCP 86

Public OpenAPI 3.1 at api.smith.langchain.com/openapi.json, re-read on 1 November with 413 paths and 613 operations, 40 of them flagged deprecated (25). llms.txt and Markdown docs (10). MCP tool docstrings are long and practical. fetch_runs explains character-budget paging, FQL operators and gives five filter examples. But four tools named like actions (push_prompt, create_dataset, update_examples, run_experiment) only return how-to text, which the docstrings say and the names don't, per the open-source server at its last commit of 11 August (16). Several MCP parameters take strings where a type would do, such as error and is_root as "true" or "false", a JSON array inside project_name and free-form FQL in filter (9). Examples throughout the docs and docstrings. Only 8 of the 613 operations declare a 429 and error bodies get little documentation (11). Versioned /api/v1 and /v2 routes, a weekly dated changelog with an RSS feed and a published deprecation policy (15). 25+10+16+9+11+15 = 86.

Agent ergonomics LangSmith API + MCP +71

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.

LangSmith API + MCP 76

The remote MCP lists 15 tools in its docs, and the changelog has since added list_model_price_maps and Engine issue tools, so roughly 16 to 20, with no toolsets or allowlist header (15). fetch_runs caps limit at 100, pages by a 25,000-character budget, trims fields to 150-character previews and takes time bounds (20). 429s are typed by cause in the docs, run-query timeouts return without retrying, and MCP errors come back as messages (14). The MCP server has no readOnlyHint or destructiveHint annotations in its source. In practice it only reads, since the write-named tools return documentation (12). Python and TypeScript SDKs. LANGSMITH_TRACING=true and a key are the only setup for LangChain apps (15).

Payments & pricing LangSmith API + MCP +60

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.

LangSmith API + MCP 60

No x402 or other machine payment (0). Per-trace pricing is public, a base trace at 0.005 LSU and the extended-retention upgrade at 0.0025 LSU, with LSU = $1, Developer $0 with 5,000 base traces and Plus $39 a seat with 10,000, re-read on 1 November (20). Developer is free for 5,000 traces a month with no payment method on file, per the usage docs (20). A person signs up in a browser to create a key (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightBaserunLangSmith API + MCPEdge
Reliability16%081LangSmith API + MCP +81
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%1586LangSmith API + MCP +71
Agent ergonomics13%576LangSmith API + MCP +71
Security & auth14%079LangSmith API + MCP +79
Payments & pricing10%060LangSmith API + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%085LangSmith API + MCP +85
Transparency & trust7%3678LangSmith API + MCP +42
Negative events≤150-4
TotalF 6.4/100BB 74.1/100

Facts side by side

FactBaserunLangSmith API + MCP
KindHTTP APIHTTP API
VendorBaserunLangChain
Hosted endpointhttps://app.baserun.aihttps://api.smith.langchain.com
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
Price for agent tracingnot published$2.50 per 1,000 requests
x402nono
LicencenoneMIT (SDK only, platform closed source)
Read-only variant documentednoyes
llms.txtnoyes
Last release2024-06-262026-10-31
Terms last updatedcouldn't be read2026-06-02
Privacy policy last updatedcouldn't be read2024-04-28
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 readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularitynone1.1k stars, 7.6M npm/wk, 17.8M PyPI/wk
Agent reviews1/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate LangSmith API + MCP 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.

LangSmith API + MCP

Rate limits published per endpoint and per plan, with each kind of 429 explained. Five SDK advisories from February to June 2026, one listed as critical (arbitrary file read through TracingMiddleware).

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

LangSmith API + MCP

  1. Batch run reads. GET /runs/:id allows 30 calls a minute per key, so use fetch_runs or POST /runs/query instead
  2. Pass trace_id or min_start_time to fetch_runs and keep limit low. Results page by a 25,000-character budget
  3. Don't call create_dataset or run_experiment over MCP to make changes. They return how-to text, not results
  4. Send X-Api-Key and point at the regional host (eu., apac. or aws.api.smith.langchain.com) that matches the workspace
  5. Move off the v1 runs query and retrieve endpoints before their 31 January 2027 sunset
  6. Give a tracing agent a tracing-only key (lsv2_tr_ prefix), not a personal or service key, so a leak can't read traces

Questions

Which is better for AI agents, Baserun or LangSmith API + MCP?

LangSmith API + MCP scores 74.1 (BB) on agent readiness against Baserun's 6.4 (F), and leads in every scored category.

Do Baserun and LangSmith API + MCP need an API key?

Baserun needs an API key. LangSmith API + MCP takes an API key or an OAuth sign-in.

Can an agent call Baserun and LangSmith API + MCP without installing anything?

Yes. Baserun has a hosted endpoint at https://app.baserun.ai and LangSmith API + MCP at https://api.smith.langchain.com.

Other comparisons with Baserun or LangSmith 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.