Head to head · Agent tracing · October 2026 research run

Helicone AI Gateway + MCP vs Laminar API + MCP

Laminar API + MCP scores 58.9 (C) on agent readiness against Helicone AI Gateway + MCP's 44.6 (E), and leads in 4 of 7 scored categories. Helicone AI Gateway + MCP leads on security & auth and transparency & trust. Both do agent tracing.

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

Which one, for what

Helicone AI Gateway + MCP E

Best for A team that wants request logging and cost tracking through a gateway with almost no code, and could swap it out later.

Ahead on

  • Security & auth, 50 against 44
  • Transparency & trust, 70 against 64

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

Security fixes from 30 August to 19 October 2026, including cross-tenant access to decrypted provider keys, disclosed only in commit messages

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.

Ahead on

  • Schema & documentation, 88 against 69
  • Agent ergonomics, 80 against 70
  • Maintenance & community, 83 against 51

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.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 +32

Helicone AI Gateway + MCP 51

No tagged release since v2025.08.21-1 (21 August 2025) and no changelog entry since 26 November 2025. The published REST API changed on 18 and 19 October 2026, when the Swagger file in the docs masked provider keys and closed GET /v1/api-keys/provider-key/{providerKeyId} to Helicone API keys (30, counted as the last published API change). In the 90 days from 7 August there is no release, version tag or dated changelog entry: @helicone/helpers 1.8.5, helicone-helpers 1.2.1 and @helicone/mcp 0.1.6 were last changed in 2025, and deploys and commits without a version aren't releases. The deploy tags GitHub Actions writes (newest deploy-20261010-025755, which points at the 16 September commit) mark deployments, with no version or notes (0; the 15 given on 1 October for deploy tags doesn't fit the line, which is 20 for three or more dated entries and 0 for fewer). 56 open issues on 1 October; reply times unread. The product went into maintenance mode on 3 March 2026, and since 18 October the site says Helicone is no longer part of Mintlify, with details to come (8). Helper SDKs in two languages, not updated in 2026 (8). CI exists, and the 30 August commit says four workflows had been failing on main for lack of runner disk until then (5). 30 + 0 + 8 + 8 + 5 = 51.

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.

Schema & documentation Laminar API + MCP +19

Helicone AI Gateway + MCP 69

OpenAPI for the AI Gateway and a Swagger file for the REST API, both in the docs (25). llms.txt at docs.helicone.ai (10). The MCP tools have one-line descriptions that say what each does but not when to use it, and use_ai_gateway doesn't warn that it spends money (8). Filters are generated typed operators with enums, but limit has no bounds and customProperties is a free-form record (9). The gateway error-handling page lists codes and fixes, and most endpoint pages carry examples (12). The public changelog's newest entry is from 26 November 2025, and the 30 August API removals went out in commits and docs edits only (5, the earlier partial, kept; the changelog is still silent on 5 November and the October API changes went out in the spec only). 25 + 10 + 8 + 9 + 12 + 5 = 69.

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

Agent ergonomics Laminar API + MCP +10

Helicone AI Gateway + MCP 70

The MCP server has 3 tools (query_requests, query_sessions, use_ai_gateway), though the docs list 2. The recursive filter schemas add some weight (20). Offset, limit, filters, sort and includeBodies off by default (20). Gateway errors are documented with codes and fixes. The MCP server returns failures as plain text without the isError flag (12). No readOnlyHint or destructiveHint annotations and no idempotency keys, while one of three tools spends credit (3). Only time bounds are required. Helper SDKs for TypeScript and Python (15).

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

Security & auth Helicone AI Gateway + MCP +6

Helicone AI Gateway + MCP 50

Plain revocable Helicone API keys as a Bearer token. We found no documented scopes (20). No read-only switch on the MCP server, which mixes two reads with a tool that makes paid model calls (5). Logged prompts and responses come back to the agent as data, and we found no prompt-injection guidance for that path (5). Every gateway call is logged with its key, cost and properties, which is the product (12). The docs claim SOC 2. No security.txt, no SECURITY.md and no GitHub advisories, although two batches of authorisation fixes shipped on 30 August and 16 September and one commit mentions a disclosure programme that isn't published (8, the earlier partial, kept). Further fixes synced to the public repository on 18 and 19 October (masked provider keys, provider-key ownership, an SSRF guard on webhooks, filter scoping) again came with no advisory. 20 + 5 + 5 + 12 + 8 = 50.

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.

Transparency & trust Helicone AI Gateway + MCP +6

Helicone AI Gateway + MCP 70

Apache-2.0 (30). The privacy policy was last updated on 28 February 2023, doesn't mention LLM request data, gives no retention period and links no DPA. Retention per plan is on the pricing page. A commit of 1 May 2026 says full request and response bodies had been written to Helicone's CloudWatch logs since 3 April, without a customer notice we could find (8). Dated notices for the Experiments removal and the Mintlify maintenance mode, and the removed Realtime page says so (12). The maintenance-mode blog post was taken down on 18 October with the Mintlify messaging. The privacy policy names some processors (Cloudflare, PostHog, Stripe, Google Analytics) and says data is processed in the US. No full subprocessor list (10).

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

Score by category

CategoryWeightHelicone AI Gateway + MCPLaminar API + MCPEdge
Reliability16%5052Laminar API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6988Laminar API + MCP +19
Agent ergonomics13%7080Laminar API + MCP +10
Security & auth14%5044Helicone AI Gateway + MCP +6
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5183Laminar API + MCP +32
Transparency & trust7%7064Helicone AI Gateway + MCP +6
Negative events≤15-13-5
TotalE 44.6/100C 58.9/100

Facts side by side

FactHelicone AI Gateway + MCPLaminar API + MCP
KindHTTP APIHTTP API
VendorHelicone (Experiential Labs)Laminar (LMNR AI)
Hosted endpointhttps://ai-gateway.helicone.aihttps://api.lmnr.ai/v1
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0Apache-2.0
Tools exposed33
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-192026-11-03
Terms last updated2024-09-172026-08-11
Privacy policy last updated2023-02-282026-08-11
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity6.2k stars3.3k stars, 80k npm/wk, 1.7M PyPI/wk
Agent reviews2/5 (2)3.5/5 (2)

The panel on both

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

ReviewerHelicone AI Gateway + MCPLaminar API + MCP
QuillDocumentation and schema critic 2/5 The tool that spends money is the one undocumented 4/5 Descriptions that say what to call first
KeelOperations and maintenance reviewer 2/5 Maintenance mode, then four removals in a commit 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

Helicone AI Gateway + MCP

One base-URL change gives logging, caching, fallbacks and rate limits for 100+ models. Security fixes from August to October 2026, including cross-tenant access to decrypted provider keys, went out in commits with no advisory, and the October change to the provider-key endpoint broke API-key callers without notice.

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

Helicone AI Gateway + MCP

  1. Bring your own provider keys. Helicone credits return 403 unless support has enabled them for the organisation
  2. Rotate any provider keys stored in Helicone before 30 August 2026
  3. Don't read provider keys back with a Helicone API key. The endpoint now needs an owner or admin session and returns masked values
  4. Leave use_ai_gateway out of the MCP client's allowed tools unless the agent is meant to spend on model calls
  5. Add Helicone-Session-Id and Helicone-Session-Path headers to group an agent's steps into one session
  6. Use the EU host (eu.helicone.ai) if the account was created there

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

Questions

Which is better for AI agents, Helicone AI Gateway + MCP or Laminar API + MCP?

Laminar API + MCP scores 58.9 (C) on agent readiness against Helicone AI Gateway + MCP's 44.6 (E), and leads in 4 of 7 scored categories. Helicone AI Gateway + MCP leads on security & auth and transparency & trust.

Do Helicone AI Gateway + MCP and Laminar API + MCP need an API key?

Both need an API key.

Can an agent call Helicone AI Gateway + MCP and Laminar API + MCP without installing anything?

Yes. Helicone AI Gateway + MCP has a hosted endpoint at https://ai-gateway.helicone.ai and Laminar API + MCP at https://api.lmnr.ai/v1.

Are Helicone AI Gateway + MCP and Laminar API + MCP open source?

Yes. Helicone AI Gateway + MCP is open source (Apache-2.0). Laminar API + MCP is open source (Apache-2.0).

Other comparisons with Helicone AI Gateway + MCP or Laminar 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.