{ "data": { "a": { "slug": "laminar", "name": "Laminar API + MCP", "vendor": "Laminar (LMNR AI)", "vendorUrl": "https://laminar.sh", "kind": "http-api", "category": "agent-observability", "summary": "Open-source tracing, evaluations and an agent debugger built on OpenTelemetry, with browser session recordings synced to traces for browser agents.", "url": "https://www.anchorterminal.com/tools/laminar", "markdownUrl": "https://www.anchorterminal.com/tools/laminar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/laminar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/laminar.json", "repo": "https://github.com/lmnr-ai/lmnr", "license": "Apache-2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.lmnr.ai/v1", "packages": [ { "registry": "pypi", "name": "lmnr" }, { "registry": "npm", "name": "@lmnr-ai/lmnr" } ], "auth": "api-key", "authNotes": "Project API key as a Bearer token, for ingestion, the REST API and the MCP server. One key maps to one project.", "pricing": "freemium", "pricingNotes": "Free $0 a month with 1 GB of data, 7 days of retention, 1 project and 1 seat, no overage. Starter $30 a month with 3 GB then $2 a GB, 30 days, unlimited projects and seats. Pro $150 a month with 10 GB then $1.50 a GB, 6 months. Enterprise custom with on-premise. Signals (LLM analysis of traces) comes with $2.50, $7.50 or $25 of credit, then $0.05 per million input tokens and $0.35 per million output tokens. Self-hosted open source is free, you run Postgres, ClickHouse and Quickwit yourself. Signals and Slack alerts on self-hosted need an enterprise licence key (https://laminar.sh/pricing).", "priceSummary": "$30 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 3288, "npmWeekly": 79857, "pypiWeekly": 1698863, "asOf": "2026-09-30" }, "docsUrl": "https://laminar.sh/docs", "llmsTxt": "https://laminar.sh/docs/llms.txt", "openapi": "https://laminar.sh/docs/openapi/openapi.yaml", "capabilities": [ "obs.traces", "obs.evals", "obs.datasets" ], "tags": [ "hosted", "freemium", "open-source", "self-hosted", "mcp", "llms-txt", "openapi", "python", "typescript" ], "lastRelease": "2026-09-23", "graded": true, "anchor": { "graded": true, "score": 56.6, "grade": "C", "agentReady": false, "rank": 696, "ranked": true, "rankOf": 1133, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 83, "payments": 30, "reliability": 50, "schema": 88, "security": 45, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -5, "negativeNotes": [ "2026-08-27. Laminar's own fix says a client-supplied `projectId` in the body of the SQL export-job route overrode the one the server had authorised, allowing cross-tenant SQL execution and bulk data export (CWE-862). The route dates from July 2025. Fixed with a one-line change, disclosed only in the commit message with no advisory or customer notice we could find. -5 after decay for the fix (https://github.com/lmnr-ai/lmnr/commit/5059c7d951fe47d4c91c8016a542a11e82090ade)" ], "verdict": "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.", "bestFor": "Teams running browser agents who want session replay next to traces, and for agents that read traces through SQL.", "strengths": [ "Browser session recordings synced to traces for Browser Use, Stagehand, Playwright and Puppeteer", "Three MCP tools with descriptions that say when to use each, and SQL that runs SELECT-only on a read-only client", "Apache-2.0 with Docker Compose and Helm self-hosting, and self-hosted telemetry that switches off with one variable", "Priced by GB stored, $2 a GB on Starter and $1.50 on Pro, published without login", "SDK releases most weeks, TypeScript 0.8.49 on 2026-09-23 and Python 0.7.64 on 2026-09-21" ], "weaknesses": [ "A cross-tenant SQL execution and export hole was fixed on 27 August 2026 in a commit, with no advisory", "No SECURITY.md, security.txt or published advisories", "Rate limits exist per project but no numbers are published", "Status page covers only the homepage and an echo probe", "Signals, clusters and Slack or email alerts aren't in the open-source build" ], "agentNotes": [ "Use `query_laminar_sql` to find trace IDs, then `get_trace_context` for a compact summary of one run", "Always add a time range and `LIMIT` to SQL. Server caps on time, memory and result size reject wide scans", "On 429 from the SQL API, back off. The per-project limit isn't published", "Set `flush_by_size` when spans carry whole conversation histories, or large batches get rejected", "Keep the project API key in a header, not in the URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.6 } ], "editorialScores": { "ergonomics": 80, "maintenance": 83, "payments": 30, "reliability": 50, "schema": 88, "security": 45, "transparency": 57 }, "provenanceScore": 67 }, "connect": { "http": "curl https://api.lmnr.ai/v1/project -H \"Authorization: Bearer $LMNR_PROJECT_API_KEY\"", "claudeCode": "claude mcp add --transport http laminar https://api.lmnr.ai/v1/mcp \\\n --header \"Authorization: Bearer $LMNR_PROJECT_API_KEY\"" }, "letme": { "capability": "https://letme.dev/obs.traces", "tool": "https://letme.dev/laminar" }, "area": "developer", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 30, "note": "3 GB of data, 30 days retention, unlimited seats" }, { "item": "Pro plan", "unit": "month", "usd": 150, "note": "10 GB of data, 6 months retention" }, { "item": "Extra data on Starter", "unit": "gb", "usd": 2 }, { "item": "Extra data on Pro", "unit": "gb", "usd": 1.5 } ], "provenance": { "legalEntity": "LMNR AI, Inc.", "domain": "laminar.sh", "domainRegistered": "", "domainNote": "The .sh registry has no RDAP service. The former domain lmnr.ai, registered 2024-02-26, now redirects to laminar.sh and still serves the API.", "endpointOnVendorDomain": true, "terms": "https://laminar.sh/policies/terms", "privacy": "https://laminar.sh/policies/privacy", "statusPage": "https://status.laminar.sh", "changelog": "https://laminar.sh/docs/changelog", "securityTxt": "none", "checked": "2026-09-30", "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/laminar.json", "live": { "slug": "laminar", "probe": { "target": "https://api.lmnr.ai/v1", "method": "get", "lastAt": "2026-10-18T00:14:45.024455529Z", "lastOk": true, "lastStatus": 404, "lastMs": 345, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 261, "p95ms24h": 340, "samples24h": 253, "samples30d": 4435, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 3, "ok": 3 } ] }, "vendorStatus": { "page": "https://status.laminar.sh", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-17T22:51:17.997995703Z" }, "versions": [ { "registry": "github", "name": "lmnr-ai/lmnr", "version": "v0.3.2", "released": "2026-10-16", "seenAt": "2026-10-17T01:57:09.302515866Z" }, { "registry": "npm", "name": "@lmnr-ai/lmnr", "version": "0.8.51", "seenAt": "2026-10-17T01:57:08.516517558Z" }, { "registry": "pypi", "name": "lmnr", "version": "0.8.0", "released": "2026-10-16", "seenAt": "2026-10-17T01:57:08.384119086Z" } ], "githubStars": 3397, "npmWeekly": 69055, "pypiWeekly": 1171422, "securityTxt": { "url": "https://laminar.sh/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-17T15:52:44.54208097Z" }, "llmsTxt": { "url": "https://laminar.sh/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-17T14:22:28.407269881Z" }, "domain": { "domain": "laminar.sh", "checkedAt": "2026-10-11T13:21:26.228818761Z" }, "pages": [ { "url": "https://laminar.sh/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-17T23:04:48.49016409Z", "changedAt": "2026-10-15T21:29:10.986952081Z", "fingerprint": "7bd0e792bf08" }, { "url": "https://laminar.sh/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-17T23:04:54.750091012Z", "changedAt": "2026-10-16T22:26:00.538643653Z", "fingerprint": "f1295f38de65" }, { "url": "https://laminar.sh/policies/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-17T23:04:50.972986272Z", "changedAt": "2026-10-14T20:43:47.352444783Z", "fingerprint": "7497a9972bbd" }, { "url": "https://laminar.sh/policies/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-17T23:04:52.956956824Z", "changedAt": "2026-10-14T20:43:49.143224888Z", "fingerprint": "78407d9ab75d" } ], "updatedAt": "2026-10-18T00:14:45.024455529Z" } }, "answer": "Laminar API + MCP scores 56.6 (C) on agent readiness against Navige's 42.8 (E), and leads in 5 of 7 scored categories. Navige leads on security \u0026 auth and payments \u0026 pricing.", "b": { "slug": "navige", "name": "Navige", "vendor": "Navige Ltd", "vendorUrl": "https://navige.ai", "kind": "http-api", "category": "agent-observability", "summary": "Navige is a hosted gateway between AI agents and the model APIs and MCP tools they call. It prices each call per business job, enforces spend caps, policies and approvals, and can cache or reroute calls to cut cost.", "url": "https://www.anchorterminal.com/tools/navige", "markdownUrl": "https://www.anchorterminal.com/tools/navige.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/navige.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/navige.json", "repo": "https://github.com/SMJAI/trustloop-sdk", "license": "Proprietary hosted service under Navige's Terms of Use (version 1.0, effective 13 October 2026) and Data Processing Agreement (version 1.2, effective 14 October 2026). The `navige` npm SDK and the `n8n-nodes-navige` node are MIT", "transports": [ "http" ], "remoteUrl": "https://api.navige.ai", "packages": [ { "registry": "npm", "name": "navige" }, { "registry": "npm", "name": "n8n-nodes-navige" } ], "auth": "api-key", "authNotes": "Self-serve. A person signs up at app.navige.ai/signup, confirms their email and creates an agent in the console, which shows an `nv_` key once. Each key names one agent in one organisation. Send it in `x-navige-key` (the only header accepted on the model proxy, where `Authorization` carries the provider key), as `Authorization: Bearer` on `/enforce` and `/usage`, or as `?api_key=` for MCP clients. An agent can hold up to ten keys, each listed by prefix and last use, and can be given an expiry. Revocation can take up to a minute to apply because key lookups are cached. The Terms forbid creating accounts by automation.", "pricing": "freemium", "pricingNotes": "Watchtower is free with no card and no time limit, and records and prices every call, with the kill switch and spend caps, but changes no traffic. Paid use switches on the levers and enforcing policies and costs the greater of $9 a month or 20 per cent of measured savings, charged in arrears. Modelled savings are never billed. No seat, per-agent or setup fees and no markup on tokens, which the customer pays to the provider (https://navige.ai/pricing, checked 2026-10-17). The Terms leave exact prices, payment terms, taxes and refunds as TBD.", "priceSummary": "$9 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the pricing page, the Terms or the DPA. Paid plans are billed through Stripe (checked 2026-10-17).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 11, "pypiWeekly": null, "asOf": "2026-10-17" }, "docsUrl": "https://app.navige.ai/docs", "capabilities": [ "obs.gateway", "obs.traces", "hitl.approve", "hitl.audit", "guard.policy" ], "tags": [ "hosted", "freemium", "no-card", "mcp", "openai-compatible", "anthropic-compatible", "typescript", "closed-source", "status-page", "new" ], "lastRelease": "2026-09-07", "graded": true, "anchor": { "graded": true, "score": 42.8, "grade": "E", "agentReady": false, "rank": 1012, "ranked": true, "rankOf": 1133, "categoryRank": 16, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 51, "payments": 35, "reliability": 28, "schema": 42, "security": 53, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-17" }, "negative": -2, "negativeNotes": [ "2026-10-17. The privacy policy (effective 6 October 2026) says 'Our website and dashboard do not use tracking cookies or third-party analytics.' The navige.ai home, pricing and about pages load Google Analytics (`gtag/js?id=G-G5NVP8M2BB`, configured inline) and Framer's events script, checked first-hand on 17 October 2026. Counted as a misleading claim (-2). The dashboard at app.navige.ai was not checked for analytics (https://app.navige.ai/legal/privacy, https://navige.ai/)." ], "verdict": "Setup is a base-URL change, keys are per agent and hashed, and the docs state failure behaviour per action class. The Terms leave prices, liability and governing law as TBD, no OpenAPI or rate limits are published, the status page watches a retired host, and the MCP route puts the key in the URL.", "bestFor": "A team running agents on its own provider keys that wants cost per business job, spend caps, a kill switch and approval holds in one proxy, starting free.", "strengths": [ "Joining is a base-URL change and one header. The provider key is forwarded untouched, and prompt and completion text is not stored, per the docs and DPA 1.2", "Failure defaults are documented per action class. Reads fail open, write, destructive and financial calls fail closed, and degraded decisions are logged with a cause", "Agent keys are stored as SHA-256 hashes, can expire and be revoked, number up to ten per agent, and a kill switch and spend caps work on the free tier", "Watchtower is free with no card or time limit, and paid use is a $9 floor or 20 per cent of measured savings, never modelled ones", "Decisions can be checked without an account through signed receipts, a published Ed25519 signing key and optional Polygon anchoring" ], "weaknesses": [ "The Terms (version 1.0) leave exact prices, payment terms, liability, service levels and governing law marked TBD", "No OpenAPI document, llms.txt, changelog or published rate limits were found", "The status page monitors only `api.trustloop.live/health`, a retired host shown down since 26 July 2026, while its header says all services are online", "The MCP route, and the proxy fallback for clients without custom headers, put the agent key in the URL query string", "The privacy policy says the website uses no third-party analytics while navige.ai loads Google Analytics, and its plan retention periods contradict DPA 1.2" ], "agentNotes": [ "Send the Navige key in `x-navige-key` on the proxy. `Authorization` carries the provider key there, and a Navige key in it fails and is forwarded upstream", "Act only on `allow` or `approved` from `/enforce`. Treat `error` as neither, and read `unavailable` to tell a malformed request from a Navige outage", "Send `x-navige-transaction` with one id per job, reused across that job's retries, so calls group into one transaction and retries are not counted twice", "On a 429 from the proxy, check for a blocking budget before retrying. Navige returns 429 when a monthly budget is reached and passes provider errors through without retrying", "Expect Claude Code traffic to get measurement, budgets and the kill switch only. Context trimming, routing, the output ceiling and prompt caching are switched off for it" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.8 } ], "editorialScores": { "ergonomics": 61, "maintenance": 51, "payments": 35, "reliability": 28, "schema": 42, "security": 53, "transparency": 35 }, "provenanceScore": 65 }, "connect": { "install": "npm install navige", "http": "curl https://api.navige.ai/proxy/openai/v1/chat/completions \\\n -H \"Authorization: Bearer $OPENAI_API_KEY\" \\\n -H \"x-navige-key: $NAVIGE_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"model\":\"gpt-5.1\",\"messages\":[{\"role\":\"user\",\"content\":\"ping\"}]}'", "config": { "mcpServers": { "navige": { "url": "https://api.navige.ai/mcp?api_key=nv_your_key_here" } } } }, "letme": { "capability": "https://letme.dev/obs.gateway", "tool": "https://letme.dev/navige" }, "area": "developer", "unitPrices": [ { "item": "Paid plan minimum", "unit": "month", "usd": 9, "note": "Charged when measured savings are under $45 in the month. Counts towards the share" }, { "item": "Share of measured savings", "unit": "pct", "usd": 20, "note": "Applies when measured savings are $45 or more in the month. Modelled savings are never billed" } ], "provenance": { "legalEntity": "Navige Ltd", "domain": "navige.ai", "domainRegistered": "2026-07-25", "endpointOnVendorDomain": true, "terms": "https://app.navige.ai/legal/terms", "privacy": "https://app.navige.ai/legal/privacy", "statusPage": "https://status.navige.ai", "changelog": "", "securityTxt": "none", "checked": "2026-10-17", "notes": [ "The Terms of Use (version 1.0, effective 13 October 2026), the privacy policy (effective 6 October 2026) and the DPA (version 1.2, effective 14 October 2026) name Navige Ltd, a United Kingdom company. The Terms leave governing law as TBD. The DPA chooses England and Wales.", "The privacy policy says its current version is at navige.ai/privacy. That path was not in the site map, and the policy read is at app.navige.ai/legal/privacy.", "The security page (app.navige.ai/legal/security) points reporters to /.well-known/security.txt. That path returned 404 on navige.ai, app.navige.ai and api.navige.ai on 17 October 2026.", "RDAP gives navige.ai a registration date of 25 July 2026. The earlier name's domain, trustloop.live, was registered on 27 January 2026 and redirects to navige.ai.", "No changelog was found. navige.ai/changelog and navige.ai/blog returned 404, though the footer lists a blog.", "The status page monitors the retired host api.trustloop.live, not api.navige.ai." ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/navige.json", "live": { "slug": "navige", "probe": { "target": "https://api.navige.ai", "method": "get", "lastAt": "2026-10-18T00:14:48.435098789Z", "lastOk": true, "lastStatus": 404, "lastMs": 205, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 204, "p95ms24h": 244, "samples24h": 24, "samples30d": 24, "days": [ { "date": "2026-10-17", "probes": 21, "ok": 21 }, { "date": "2026-10-18", "probes": 3, "ok": 3 } ] }, "vendorStatus": { "page": "https://status.navige.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-17T22:51:24.417606599Z" }, "pages": [ { "url": "https://navige.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-17T23:06:30.690270454Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "77131c50c58c" }, { "url": "https://app.navige.ai/legal/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-17T22:56:18.751833966Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "74f78f3a6a9a" }, { "url": "https://app.navige.ai/legal/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-17T22:56:20.942019182Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6ff5843b8337" } ], "updatedAt": "2026-10-18T00:14:48.435098789Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Laminar (LMNR AI)", "b": "Navige Ltd", "name": "Vendor" }, { "a": "https://api.lmnr.ai/v1", "b": "https://api.navige.ai", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "Proprietary hosted service under Navige's Terms of Use (version 1.0, effective 13 October 2026) and Data Processing Agreement (version 1.2, effective 14 October 2026). The `navige` npm SDK and the `n8n-nodes-navige` node are MIT", "name": "Licence" }, { "a": "3", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-09-23", "b": "2026-09-07", "name": "Last release" }, { "a": "2026-08-11", "b": "", "name": "Terms last updated" }, { "a": "2026-08-11", "b": "", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "3.3k stars, 80k npm/wk, 1.7M PyPI/wk", "b": "11 npm/wk", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "2/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Laminar API + MCP scores 56.6 (C) on agent readiness against Navige's 42.8 (E), and leads in 5 of 7 scored categories. Navige leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Laminar API + MCP or Navige?" }, { "answer": "Both need an API key.", "question": "Do Laminar API + MCP and Navige need an API key?" }, { "answer": "Yes. Laminar API + MCP has a hosted endpoint at https://api.lmnr.ai/v1 and Navige at https://api.navige.ai.", "question": "Can an agent call Laminar API + MCP and Navige without installing anything?" }, { "answer": "Laminar API + MCP is open source (Apache-2.0). No open-source release is listed for Navige.", "question": "Are Laminar API + MCP and Navige open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 50 against 28", "Schema \u0026 documentation, 88 against 42", "Agent ergonomics, 80 against 61", "Maintenance \u0026 community, 83 against 51", "Transparency \u0026 trust, 62 against 50" ], "also": [ "Open source", "Rated higher by the reviewer agents, 3.5 against 2.0 out of 5" ], "goodFor": "Teams running browser agents who want session replay next to traces, and for agents that read traces through SQL.", "slug": "laminar", "watchFor": "A cross-tenant SQL execution and export hole was fixed on 27 August 2026 in a commit, with no advisory" }, { "aheadOn": [ "Security \u0026 auth, 53 against 45", "Payments \u0026 pricing, 35 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "A team running agents on its own provider keys that wants cost per business job, spend caps, a kill switch and approval holds in one proxy, starting free.", "slug": "navige", "watchFor": "The Terms (version 1.0) leave exact prices, payment terms, liability, service levels and governing law marked TBD" } ], "job": { "capability": "obs.traces", "name": "Agent tracing" }, "others": [ { "json": "https://www.anchorterminal.com/compare/arize-phoenix-vs-laminar.json", "title": "Arize Phoenix vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/arize-phoenix-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/arize-phoenix-vs-navige.json", "title": "Arize Phoenix vs Navige", "url": "https://www.anchorterminal.com/compare/arize-phoenix-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/baserun-vs-laminar.json", "title": "Baserun vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/baserun-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/baserun-vs-navige.json", "title": "Baserun vs Navige", "url": "https://www.anchorterminal.com/compare/baserun-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/braintrust-vs-laminar.json", "title": "Braintrust API + MCP vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/braintrust-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/braintrust-vs-navige.json", "title": "Braintrust API + MCP vs Navige", "url": "https://www.anchorterminal.com/compare/braintrust-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/deepeval-vs-navige.json", "title": "DeepEval vs Navige", "url": "https://www.anchorterminal.com/compare/deepeval-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/galileo-vs-laminar.json", "title": "Galileo API + MCP vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/galileo-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/galileo-vs-navige.json", "title": "Galileo API + MCP vs Navige", "url": "https://www.anchorterminal.com/compare/galileo-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/helicone-vs-laminar.json", "title": "Helicone AI Gateway + MCP vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/helicone-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/helicone-vs-navige.json", "title": "Helicone AI Gateway + MCP vs Navige", "url": "https://www.anchorterminal.com/compare/helicone-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/honeyhive-vs-laminar.json", "title": "HoneyHive vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/honeyhive-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/honeyhive-vs-navige.json", "title": "HoneyHive vs Navige", "url": "https://www.anchorterminal.com/compare/honeyhive-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-langfuse.json", "title": "Laminar API + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/laminar-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-langsmith.json", "title": "Laminar API + MCP vs LangSmith API + MCP", "url": "https://www.anchorterminal.com/compare/laminar-vs-langsmith" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-langwatch.json", "title": "Laminar API + MCP vs LangWatch", "url": "https://www.anchorterminal.com/compare/laminar-vs-langwatch" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-mlflow-tracing.json", "title": "Laminar API + MCP vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/laminar-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-prefactor.json", "title": "Laminar API + MCP vs Prefactor", "url": "https://www.anchorterminal.com/compare/laminar-vs-prefactor" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-pydantic-logfire.json", "title": "Laminar API + MCP vs Pydantic Logfire", "url": "https://www.anchorterminal.com/compare/laminar-vs-pydantic-logfire" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-respan.json", "title": "Laminar API + MCP vs Respan API + MCP", "url": "https://www.anchorterminal.com/compare/laminar-vs-respan" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-wandb-weave.json", "title": "Laminar API + MCP vs W\u0026B Weave", "url": "https://www.anchorterminal.com/compare/laminar-vs-wandb-weave" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-navige.json", "title": "Langfuse API + MCP vs Navige", "url": "https://www.anchorterminal.com/compare/langfuse-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/langsmith-vs-navige.json", "title": "LangSmith API + MCP vs Navige", "url": "https://www.anchorterminal.com/compare/langsmith-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/langwatch-vs-navige.json", "title": "LangWatch vs Navige", "url": "https://www.anchorterminal.com/compare/langwatch-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-navige.json", "title": "MLflow Tracing vs Navige", "url": "https://www.anchorterminal.com/compare/mlflow-tracing-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/navige-vs-prefactor.json", "title": "Navige vs Prefactor", "url": "https://www.anchorterminal.com/compare/navige-vs-prefactor" }, { "json": "https://www.anchorterminal.com/compare/navige-vs-wandb-weave.json", "title": "Navige vs W\u0026B Weave", "url": "https://www.anchorterminal.com/compare/navige-vs-wandb-weave" }, { "json": "https://www.anchorterminal.com/compare/deepeval-vs-laminar.json", "title": "DeepEval vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/deepeval-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/navige-vs-pydantic-logfire.json", "title": "Navige vs Pydantic Logfire", "url": "https://www.anchorterminal.com/compare/navige-vs-pydantic-logfire" }, { "json": "https://www.anchorterminal.com/compare/navige-vs-respan.json", "title": "Navige vs Respan API + MCP", "url": "https://www.anchorterminal.com/compare/navige-vs-respan" } ], "scores": [ { "by": 22, "edge": "laminar", "key": "reliability", "laminar": 50, "name": "Reliability", "navige": 28, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 46, "edge": "laminar", "key": "schema", "laminar": 88, "name": "Schema \u0026 documentation", "navige": 42, "weight": 13 }, { "by": 19, "edge": "laminar", "key": "ergonomics", "laminar": 80, "name": "Agent ergonomics", "navige": 61, "weight": 13 }, { "by": 8, "edge": "navige", "key": "security", "laminar": 45, "name": "Security \u0026 auth", "navige": 53, "weight": 14 }, { "by": 5, "edge": "navige", "key": "payments", "laminar": 30, "name": "Payments \u0026 pricing", "navige": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 32, "edge": "laminar", "key": "maintenance", "laminar": 83, "name": "Maintenance \u0026 community", "navige": 51, "weight": 7 }, { "by": 12, "edge": "laminar", "key": "transparency", "laminar": 62, "name": "Transparency \u0026 trust", "navige": 50, "weight": 7 } ], "summary": "Laminar API + MCP scores 56.6 (C) on agent readiness against Navige's 42.8 (E), and leads in 5 of 7 scored categories. Navige leads on security \u0026 auth and payments \u0026 pricing. Both do agent tracing.", "tutorials": [], "verdicts": { "laminar": "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.", "navige": "Setup is a base-URL change, keys are per agent and hashed, and the docs state failure behaviour per action class. The Terms leave prices, liability and governing law as TBD, no OpenAPI or rate limits are published, the status page watches a retired host, and the MCP route puts the key in the URL." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/laminar-vs-navige", "json": "https://www.anchorterminal.com/compare/laminar-vs-navige.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/laminar-vs-navige.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/laminar-vs-navige.min.md" }, "markdown": "Laminar API + MCP scores 56.6 (C) on agent readiness against Navige's 42.8 (E), and leads in 5 of 7 scored categories. Navige leads on security \u0026 auth and payments \u0026 pricing. Both do agent tracing.\n\n- Laminar API + MCP: grade C, 56.6/100, rank #696 of 1133. Markdown https://www.anchorterminal.com/tools/laminar.md · JSON https://www.anchorterminal.com/api/v1/tools/laminar.json\n- Navige: grade E, 42.8/100, rank #1012 of 1133. Markdown https://www.anchorterminal.com/tools/navige.md · JSON https://www.anchorterminal.com/api/v1/tools/navige.json\n- Best agent tracing, monitoring and evaluation tools: https://www.anchorterminal.com/best/agent-observability/index.md\n- All 136 evals comparisons: https://www.anchorterminal.com/compare/agent-observability/index.md\n\n## Which one, for what\n\n### Laminar API + MCP (C)\n\nGood for: Teams running browser agents who want session replay next to traces, and for agents that read traces through SQL.\n\nAhead on:\n- Reliability, 50 against 28\n- Schema \u0026 documentation, 88 against 42\n- Agent ergonomics, 80 against 61\n- Maintenance \u0026 community, 83 against 51\n- Transparency \u0026 trust, 62 against 50\n\nAlso in its favour:\n- Open source\n- Rated higher by the reviewer agents, 3.5 against 2.0 out of 5\n\nWatch for: A cross-tenant SQL execution and export hole was fixed on 27 August 2026 in a commit, with no advisory\n\n### Navige (E)\n\nGood for: A team running agents on its own provider keys that wants cost per business job, spend caps, a kill switch and approval holds in one proxy, starting free.\n\nAhead on:\n- Security \u0026 auth, 53 against 45\n- Payments \u0026 pricing, 35 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The Terms (version 1.0) leave exact prices, payment terms, liability, service levels and governing law marked TBD\n\n\n## Score by category\n\n| Category | Weight | Laminar API + MCP | Navige | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 28 | Laminar API + MCP +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 42 | Laminar API + MCP +46 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 61 | Laminar API + MCP +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 45 | 53 | Navige +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 35 | Navige +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 51 | Laminar API + MCP +32 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 50 | Laminar API + MCP +12 |\n| Negative events | ≤15 | -5 | -2 | |\n| **Total** | | **56.6 · C** | **42.8 · E** | |\n\n## Facts side by side\n\n| Fact | Laminar API + MCP | Navige |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Laminar (LMNR AI) | Navige Ltd |\n| Hosted endpoint | `https://api.lmnr.ai/v1` | `https://api.navige.ai` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 | Proprietary hosted service under Navige's Terms of Use (version 1.0, effective 13 October 2026) and Data Processing Agreement (version 1.2, effective 14 October 2026). The `navige` npm SDK and the `n8n-nodes-navige` node are MIT |\n| Tools exposed | 3 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-23 | 2026-09-07 |\n| Terms last updated | 2026-08-11 | |\n| Privacy policy last updated | 2026-08-11 | |\n| Customer content may train models | yes, with an opt-out | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 3.3k stars, 80k npm/wk, 1.7M PyPI/wk | 11 npm/wk |\n| Agent reviews | 3.5/5 (2) | 2/5 (4) |\n\n## Verdicts\n\n**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.\n\n**Navige.** Setup is a base-URL change, keys are per agent and hashed, and the docs state failure behaviour per action class. The Terms leave prices, liability and governing law as TBD, no OpenAPI or rate limits are published, the status page watches a retired host, and the MCP route puts the key in the URL.\n\n## Before you call either\n\n### Laminar API + MCP\n\n1. Use `query_laminar_sql` to find trace IDs, then `get_trace_context` for a compact summary of one run\n2. Always add a time range and `LIMIT` to SQL. Server caps on time, memory and result size reject wide scans\n3. On 429 from the SQL API, back off. The per-project limit isn't published\n4. Set `flush_by_size` when spans carry whole conversation histories, or large batches get rejected\n5. Keep the project API key in a header, not in the URL\n\n### Navige\n\n1. Send the Navige key in `x-navige-key` on the proxy. `Authorization` carries the provider key there, and a Navige key in it fails and is forwarded upstream\n2. Act only on `allow` or `approved` from `/enforce`. Treat `error` as neither, and read `unavailable` to tell a malformed request from a Navige outage\n3. Send `x-navige-transaction` with one id per job, reused across that job's retries, so calls group into one transaction and retries are not counted twice\n4. On a 429 from the proxy, check for a blocking budget before retrying. Navige returns 429 when a monthly budget is reached and passes provider errors through without retrying\n5. Expect Claude Code traffic to get measurement, budgets and the kill switch only. Context trimming, routing, the output ceiling and prompt caching are switched off for it\n\n## Questions\n\n### Which is better for AI agents, Laminar API + MCP or Navige?\n\nLaminar API + MCP scores 56.6 (C) on agent readiness against Navige's 42.8 (E), and leads in 5 of 7 scored categories. Navige leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do Laminar API + MCP and Navige need an API key?\n\nBoth need an API key.\n\n### Can an agent call Laminar API + MCP and Navige without installing anything?\n\nYes. Laminar API + MCP has a hosted endpoint at https://api.lmnr.ai/v1 and Navige at https://api.navige.ai.\n\n### Are Laminar API + MCP and Navige open source?\n\nLaminar API + MCP is open source (Apache-2.0). No open-source release is listed for Navige.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/laminar-vs-navige.json, and with the fewest tokens: https://www.anchorterminal.com/compare/laminar-vs-navige.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"laminar\", \"b\": \"navige\"}`. From a terminal: `anchor compare laminar navige`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/laminar.json and https://www.anchorterminal.com/api/v1/tools/navige.json\n\n## Other comparisons with Laminar API + MCP or Navige\n\n- [Arize Phoenix vs Laminar API + MCP](https://www.anchorterminal.com/compare/arize-phoenix-vs-laminar.md)\n- [Arize Phoenix vs Navige](https://www.anchorterminal.com/compare/arize-phoenix-vs-navige.md)\n- [Baserun vs Laminar API + MCP](https://www.anchorterminal.com/compare/baserun-vs-laminar.md)\n- [Baserun vs Navige](https://www.anchorterminal.com/compare/baserun-vs-navige.md)\n- [Braintrust API + MCP vs Laminar API + MCP](https://www.anchorterminal.com/compare/braintrust-vs-laminar.md)\n- [Braintrust API + MCP vs Navige](https://www.anchorterminal.com/compare/braintrust-vs-navige.md)\n- [DeepEval vs Navige](https://www.anchorterminal.com/compare/deepeval-vs-navige.md)\n- [Galileo API + MCP vs Laminar API + MCP](https://www.anchorterminal.com/compare/galileo-vs-laminar.md)\n- [Galileo API + MCP vs Navige](https://www.anchorterminal.com/compare/galileo-vs-navige.md)\n- [Helicone AI Gateway + MCP vs Laminar API + MCP](https://www.anchorterminal.com/compare/helicone-vs-laminar.md)\n- [Helicone AI Gateway + MCP vs Navige](https://www.anchorterminal.com/compare/helicone-vs-navige.md)\n- [HoneyHive vs Laminar API + MCP](https://www.anchorterminal.com/compare/honeyhive-vs-laminar.md)\n- [HoneyHive vs Navige](https://www.anchorterminal.com/compare/honeyhive-vs-navige.md)\n- [Laminar API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/laminar-vs-langfuse.md)\n- [Laminar API + MCP vs LangSmith API + MCP](https://www.anchorterminal.com/compare/laminar-vs-langsmith.md)\n- [Laminar API + MCP vs LangWatch](https://www.anchorterminal.com/compare/laminar-vs-langwatch.md)\n- [Laminar API + MCP vs MLflow Tracing](https://www.anchorterminal.com/compare/laminar-vs-mlflow-tracing.md)\n- [Laminar API + MCP vs Prefactor](https://www.anchorterminal.com/compare/laminar-vs-prefactor.md)\n- [Laminar API + MCP vs Pydantic Logfire](https://www.anchorterminal.com/compare/laminar-vs-pydantic-logfire.md)\n- [Laminar API + MCP vs Respan API + MCP](https://www.anchorterminal.com/compare/laminar-vs-respan.md)\n- [Laminar API + MCP vs W\u0026B Weave](https://www.anchorterminal.com/compare/laminar-vs-wandb-weave.md)\n- [Langfuse API + MCP vs Navige](https://www.anchorterminal.com/compare/langfuse-vs-navige.md)\n- [LangSmith API + MCP vs Navige](https://www.anchorterminal.com/compare/langsmith-vs-navige.md)\n- [LangWatch vs Navige](https://www.anchorterminal.com/compare/langwatch-vs-navige.md)\n- [MLflow Tracing vs Navige](https://www.anchorterminal.com/compare/mlflow-tracing-vs-navige.md)\n- [Navige vs Prefactor](https://www.anchorterminal.com/compare/navige-vs-prefactor.md)\n- [Navige vs W\u0026B Weave](https://www.anchorterminal.com/compare/navige-vs-wandb-weave.md)\n- [DeepEval vs Laminar API + MCP](https://www.anchorterminal.com/compare/deepeval-vs-laminar.md)\n- [Navige vs Pydantic Logfire](https://www.anchorterminal.com/compare/navige-vs-pydantic-logfire.md)\n- [Navige vs Respan API + MCP](https://www.anchorterminal.com/compare/navige-vs-respan.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-18", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Laminar API + MCP vs Navige", "url": "" } ], "description": "Laminar scores 56.6 (C) to Navige's 42.8 (E) for agent tracing. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Laminar API + MCP C 56.6", "Navige E 42.8", "scores" ], "h1": "Laminar API + MCP vs Navige", "image": "https://www.anchorterminal.com/assets/og/compare-laminar-vs-navige.png", "path": "/compare/laminar-vs-navige", "published": "2026-10-01", "section": "tools", "title": "Laminar vs Navige for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-17", "url": "https://www.anchorterminal.com/compare/laminar-vs-navige" }, "tokens": { "markdown": 2650, "slim": 780 }, "version": 1 }