Head to head · Agent tracing · October 2026 research run
Laminar API + MCP vs Respan API + MCP
Respan API + MCP scores 73.9 (BB) on agent readiness against Laminar API + MCP's 58.9 (C), and leads in 5 of 7 scored categories. Laminar API + MCP leads on transparency & trust. Both do agent tracing.
Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons
Which one, for what
Best for Teams running browser agents who want session replay next to traces, and for agents that read traces through SQL.
Ahead on
- Transparency & trust, 64 against 59
Also in its favour
- Open source
- Rated higher by the reviewer agents, 3.5 against 2.5 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
Best for Teams that want a gateway and tracing in one integration and an agent that can read logs and manage prompts, datasets and evaluators over MCP, read-only or not.
Ahead on
- Reliability, 83 against 52
- Agent ergonomics, 90 against 80
- Security & auth, 74 against 44
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Security fixes on 30 July, 28 August and 19 October 2026 disclosed only as one-line changelog entries
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.
Reliability Respan API + MCP +31
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.
Respan API + MCP 83
Better Stack page at status.respan.ai with six components (web, logging and gateway, each for the platform and Enterprise) and an incident history page (20). The 90 days to 1 November hold two incidents, both in late September, and none in October or November. The Responses API path through the gateway was affected for OpenAI and Anthropic requests for 13 hours 47 minutes on 26 September, and request logs were delayed across all regions for 1 hour 58 minutes on 29 September. The first affected about 0.5 per cent of OpenAI and Anthropic requests on that path. In the second, logs were delayed and for part of the time some API requests failed with server errors and some valid keys were rejected with 403s. By this run's reading both hit a subset of requests, so both are partial and minor (20, up from 10 where 26 September had been read as a major). Gateway and ingestion limits published per plan, 412 a minute on Free and 8,400 and 4,200 on Team, per the 1 October check (15). The OpenAPI spec declares 429 and the limits guide shows the 429 bodies and says requests go through when the period resets. We found no Retry-After or backoff guidance (10). The pricing page listed a 99.99 per cent uptime SLA on Enterprise on 1 October, terms not published, not re-read on 1 November (8). Gateway, logging and MCP are GA (10). 20 + 20 + 15 + 10 + 8 + 10 = 83.
Security & auth Respan API + MCP +30
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.
Respan API + MCP 74
API keys carry Read, Write, Gateway and Admin scopes since 25 September, can have an expiry and spend caps, are bound to one project and stop working at once when revoked. The MCP server also takes OAuth, now with mcp:read and mcp:write scopes (30). OAuth connections are read-only unless the user ticks "Also allow changes" (since 17 October), /mcp/readonly lists only read tools for any credential, and destructive tools are annotated so clients such as ChatGPT ask before running them. No confirmation step inside Respan itself (18, as exa-mcp). Guardrails V2 (9 October) blocks jailbreak and prompt-injection requests at the gateway, reading the latest user and tool messages, but we found no guidance for agents reading untrusted log content over MCP (8). Every gateway call is logged against its key. The compliance page mentions audit logging without saying what customers can see, per the 1 October check (8). SOC 2 Type II (report under NDA), HIPAA BAAs and GDPR per the compliance page, and optional multi-factor sign-in since 19 October. No security.txt or SECURITY.md, and security fixes appear in the changelog as one-liners (10). 30 + 18 + 8 + 8 + 10 = 74.
Agent ergonomics Respan API + MCP +10
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).
Respan API + MCP 90
Since 21 October the hosted MCP server's tools/list shows ten everyday tools (logs, traces, metrics, errors, behaviours, prompts) plus tool_search and tool_run, with listed descriptions cut to 300 characters and full contracts on request (15 for 12 tools). The rest of a catalogue of 293 backend tool contracts is found through tool_search, folded groups are searched only when named, and /mcp/readonly serves only read tools (10 back, 25). log_list pages and returns summary fields unless more are asked for, defaults to a recent window, and long pages report what was cut (20). API errors pass through with status and body, invalid filters return a typed validation_error naming the field, and a write from a read-only connection returns insufficient_scope saying how to reconnect (15). Every tool now carries readOnlyHint, destructiveHint and openWorldHint, with deletes and production changes marked destructive and any unlisted tool treated as destructive, but no idempotency keys were found (15). Python and TypeScript SDKs, a CLI and agent skills, with few required parameters (15). 25 + 20 + 15 + 15 + 15 = 90.
Transparency & trust Laminar API + MCP +5
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).
Respan API + MCP 59
Closed platform. The SDK monorepo is Apache-2.0 and the MCP server's README says MIT, though that repository has no LICENSE file (18). The privacy notice (25 February 2026) covers prompts and outputs and says they go to AI providers such as OpenAI, Anthropic and Google. Retention is per plan and adjustable per project, and DPAs and BAAs come by email (16). No deprecation policy found. The legacy /api/generate endpoint was retired on 11 September with no earlier dated notice we could find (5). EU residency on request and AI providers named, no full subprocessor list (8).
Score by category
| Category | Weight | Laminar API + MCP | Respan API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 52 | 83 | Respan API + MCP +31 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 89 | Respan API + MCP +1 |
| Agent ergonomics | 13% | 80 | 90 | Respan API + MCP +10 |
| Security & auth | 14% | 44 | 74 | Respan API + MCP +30 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 85 | Respan API + MCP +2 |
| Transparency & trust | 7% | 64 | 59 | Laminar API + MCP +5 |
| Negative events | ≤15 | -5 | -3 | |
| Total | C 58.9/100 | BB 73.9/100 |
Facts side by side
| Fact | Laminar API + MCP | Respan API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Laminar (LMNR AI) | Respan (formerly Keywords AI) |
| Hosted endpoint | https://api.lmnr.ai/v1 | https://api.respan.ai/api |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 (SDKs only, platform closed source) |
| Tools exposed | 3 | 12 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-11-03 | 2026-10-19 |
| Terms last updated | 2026-08-11 | 2026-02-25 |
| Privacy policy last updated | 2026-08-11 | 2026-02-25 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 3.3k stars, 80k npm/wk, 1.7M PyPI/wk | 270 npm/wk, 13k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Laminar API + MCP higher, the other way from the total score.
| Reviewer | Laminar API + MCP | Respan API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Weekly SDKs, and a domain move nobody dated | 2/5 A legacy endpoint retired with no notice found |
| QuillDocumentation and schema critic | 4/5 Descriptions that say what to call first | 3/5 Careful prose over 67 unannotated tools |
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.
Respan API + MCP
Project-bound API keys with Read, Write, Gateway and Admin scopes, and since October a hosted MCP server that lists twelve tools, annotates every tool and connects read-only by default. Security fixes, including a live-event stream flaw, appear only as one-line changelog entries with no advisory.
Before you call either
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
Respan API + MCP
- Connect to https://mcp.respan.ai/mcp/readonly for agents that only analyse logs, or use a key with only the Read scope
- Call
tool_searchwith resource and action words to find tools that aren't listed, thentool_runwith the returned schema - Pass
filterstolog_listrather than paging through everything. The default window is recent - Call
project_listfirst when results look empty over OAuth. Every tool acts on the active project only - Append
.mdto any docs URL for clean Markdown
Questions
Which is better for AI agents, Laminar API + MCP or Respan API + MCP?
Respan API + MCP scores 73.9 (BB) on agent readiness against Laminar API + MCP's 58.9 (C), and leads in 5 of 7 scored categories. Laminar API + MCP leads on transparency & trust.
Do Laminar API + MCP and Respan API + MCP need an API key?
Laminar API + MCP needs an API key. Respan API + MCP takes an API key or an OAuth sign-in.
Can an agent call Laminar API + MCP and Respan API + MCP without installing anything?
Yes. Laminar API + MCP has a hosted endpoint at https://api.lmnr.ai/v1 and Respan API + MCP at https://api.respan.ai/api.
Are Laminar API + MCP and Respan API + MCP open source?
Laminar API + MCP is open source (Apache-2.0). No open-source release is listed for Respan API + MCP.
Other comparisons with Laminar API + MCP or Respan API + MCP
- Agent Tree vs Laminar API + MCP
- Agent Tree vs Respan API + MCP
- agents-tree vs Laminar API + MCP
- agents-tree vs Respan API + MCP
- Arize Phoenix vs Laminar API + MCP
- Arize Phoenix vs Respan API + MCP
- Baserun vs Laminar API + MCP
- Baserun vs Respan API + MCP
- BotGauge vs Laminar API + MCP
- BotGauge vs Respan API + MCP
- Braintrust API + MCP vs Laminar API + MCP
- Braintrust API + MCP vs Respan API + MCP
- Galileo API + MCP vs Laminar API + MCP
- Galileo API + MCP vs Respan API + MCP
- Helicone AI Gateway + MCP vs Laminar API + MCP
- Helicone AI Gateway + MCP vs Respan API + MCP
- HoneyHive vs Laminar API + MCP
- HoneyHive vs Respan API + MCP
- Hue vs Laminar API + MCP
- Hue vs Respan 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 W&B Weave
- Langfuse API + MCP vs Respan API + MCP
- LangSmith API + MCP vs Respan API + MCP
- LangWatch vs Respan API + MCP
- MLflow Tracing vs Respan API + MCP
- Opik API + MCP vs Respan API + MCP
- Overmind vs Respan API + MCP
- Prefactor vs Respan API + MCP
- Pydantic Logfire vs Respan API + MCP
- Respan API + MCP vs W&B Weave
- DeepEval vs Laminar API + MCP
- DeepEval vs Respan API + MCP
- Gauge CLI vs Laminar API + MCP
- Gauge CLI vs Respan API + MCP
- Laminar API + MCP vs Plurai Simulation
- Plurai Simulation vs Respan API + MCP
- Navige vs Respan API + MCP
Machine-readable
- This page as Markdown
/compare/laminar-vs-respan.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/laminar.json·/api/v1/tools/respan.json - From a terminal
anchor compare laminar respan(the CLI) - Over MCP
compare_tools {"a": "laminar", "b": "respan"}at/mcp, no key