Head to head · Agent tracing · October 2026 research run

Laminar API + MCP vs LangSmith API + MCP

LangSmith API + MCP scores 74.1 (BB) on agent readiness against Laminar API + MCP's 58.9 (C), and leads in 5 of 7 scored categories. Both do agent tracing.

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

Which one, for what

Laminar API + MCP C

Best for Teams running browser agents who want session replay next to traces, and for agents that read traces through SQL.

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.5 against 3.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

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 52
  • Security & auth, 79 against 44
  • Payments & pricing, 60 against 45
  • Transparency & trust, 78 against 64

Also in its favour

  • Agent-ready, a grade of BB or better

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.

Security & auth LangSmith API + MCP +35

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.

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.

Reliability LangSmith API + MCP +29

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.

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.

Payments & pricing LangSmith API + MCP +15

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.

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.

Transparency & trust LangSmith API + MCP +14

Laminar API + MCP 64

Apache-2.0, with Signals and Slack alerts held back from the open-source images behind a licence key (28). The privacy policy covers account data in general terms with no retention period for trace data, no subprocessor list and no DPA link we could find. Retention per plan is on the pricing page and PII redaction is documented (12). No deprecation policy. The move from lmnr.ai to laminar.sh while the API stayed on api.lmnr.ai wasn't dated in the changelog (5). Self-hosted telemetry, on by default since 8 June 2026, is disclosed in the README as anonymised, with LAMINAR_TELEMETRY_DISABLED=true to switch it off. The code sends a per-deployment UUID, version, environment and row counts, with the source IP dropped. Until v0.3.2 (16 October) the documented opt-out didn't reach the Compose frontend containers (7280cc17). No subprocessor or data-location list for the cloud (12).

LangSmith API + MCP 78

Closed platform. The SDKs and the open-source MCP server are MIT (18). Retention (14 days base, 180 extended) and data purging are documented and the regions FAQ states SOC 2, HIPAA and GDPR, with a DPA on request. The 180-day cap on extended retention appeared in the changelog entry for 7 to 14 September and took effect on 14 September (20). Published deprecation policy with a 6-month cloud window and Deprecation and Sunset headers, and the v1 runs endpoints carry a 31 January 2027 sunset. The POST /feedback/eager removal on 10 August 2026 was announced in the changelog for 6 to 10 July, about a month ahead, before the six-month policy page was published on 27 July, and October entries cap trace tree requests at 1,000 runs and invalidate saved agent-list cursors with notice on the day (20). US, EU and APAC regions on GCP and a US region on AWS are documented, and Engine's model subprocessors are listed. We couldn't read a full subprocessor list (12). 18+20+20+12 = 70.

Score by category

CategoryWeightLaminar API + MCPLangSmith API + MCPEdge
Reliability16%5281LangSmith API + MCP +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8886Laminar API + MCP +2
Agent ergonomics13%8076Laminar API + MCP +4
Security & auth14%4479LangSmith API + MCP +35
Payments & pricing10%4560LangSmith API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8385LangSmith API + MCP +2
Transparency & trust7%6478LangSmith API + MCP +14
Negative events≤15-5-4
TotalC 58.9/100BB 74.1/100

Facts side by side

FactLaminar API + MCPLangSmith API + MCP
KindHTTP APIHTTP API
VendorLaminar (LMNR AI)LangChain
Hosted endpointhttps://api.lmnr.ai/v1https://api.smith.langchain.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
Price for agent tracingnot published$2.50 per 1,000 requests
x402nono
LicenceApache-2.0MIT (SDK only, platform closed source)
Tools exposed3none
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-11-032026-10-31
Terms last updated2026-08-112026-06-02
Privacy policy last updated2026-08-112024-04-28
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity3.3k stars, 80k npm/wk, 1.7M PyPI/wk1.1k stars, 7.6M npm/wk, 17.8M PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Laminar API + MCP higher, the other way from the total score.

ReviewerLaminar API + MCPLangSmith API + MCP
QuillDocumentation and schema critic 4/5 Descriptions that say what to call first 3/5 Four tools named like actions that only explain
KeelOperations and maintenance reviewer 3/5 Weekly SDKs, and a domain move nobody dated 3/5 Six months promised, a week given on retention

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

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.

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

Laminar API + MCP

  1. Use query_laminar_sql to find trace IDs, then get_trace_context for a compact summary of one run
  2. Always add a time range and LIMIT to SQL. Server caps on time, memory and result size reject wide scans
  3. On 429 from the SQL API, back off and retry. The per-project limit isn't published
  4. Set flush_by_size when spans carry whole conversation histories, or large batches get rejected
  5. Keep the project API key in a header, not in the URL

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, Laminar API + MCP or LangSmith API + MCP?

LangSmith API + MCP scores 74.1 (BB) on agent readiness against Laminar API + MCP's 58.9 (C), and leads in 5 of 7 scored categories.

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

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

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

Yes. Laminar API + MCP has a hosted endpoint at https://api.lmnr.ai/v1 and LangSmith API + MCP at https://api.smith.langchain.com.

Are Laminar API + MCP and LangSmith API + MCP open source?

Laminar API + MCP is open source (Apache-2.0). No open-source release is listed for LangSmith API + MCP.

Other comparisons with Laminar API + MCP 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.