LangSmith vs Braintrust

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to LangSmith
   LangSmith✓fullprobed8/10

   Direct probe evidence confirms LangSmith hosts a working llms.txt file (HTTP 200) plus markdown-formatted docs pages that explicitly point agents to the llms.txt index, making the docs agent-consumable by design. missing for 10: no independent/community confirmation that agents actually consume this successfully in practice, and no explicit vendor statement framing this as an intentional agent-facing feature.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.langchain.com/llms.txt # Docs by LangChain > Documentation for LangSmith, Fleet, and our open sour…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.langchain.com/langsmith/home.md > ## Documentation Index > Fetch the complete documentation index at…”

   proof ↗⚑ flag

   Braintrust~partialprobed6/10

   A live probe confirms llms.txt exists at braintrust.dev/llms.txt returning 200 with a concise agent-oriented description, directly satisfying the story's core requirement. However, docs.md and OpenAPI/machine-readable doc endpoints return 404, indicating incomplete agent-oriented documentation coverage beyond the single llms.txt file. missing for 10: full docs-as-markdown or OpenAPI endpoints for deeper agent consumption, independent confirmation that agents successfully use llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.braintrust.dev/llms.txt # Braintrust > Braintrust is the active observability platform for instrume…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.braintrust.dev/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.braintrust.dev/openapi.json, https://www.braintrust.dev/swagger.json, https://www.braint…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Braintrust
   LangSmith~partialclaimed6/10

   LangSmith exposes SDKs (Python/TS/Go/Java) and OpenTelemetry-based tracing that let you programmatically run evaluations and send traces without the UI, and evaluation experiments can be scripted with configurable concurrency/repetitions, which is consistent with running as part of automated pipelines. However there is no explicit CI/CD example, GitHub Actions template, or documented CLI for headless automation. missing for 10: explicit CI/CD integration guide or example, a dedicated headless CLI, and independent confirmation of automated pipeline usage.

   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”
   • [claimed-docs] “LangSmith supports OpenTelemetry-based tracing, allowing you to send traces from any OpenTelemetry-compatible application.”
   • [claimed-docs] “Run evaluations on curated datasets during development to compare versions, benchmark performance, and catch regressions.”
   • [claimed-docs] “Trace your preferred framework or integrate LangSmith with any agent stack using our Python, Typescript, Go, or Java SDKs.”
   • [github] “client = wrap_openai(openai.Client())”

   proof ↗⚑ flag

   Braintrust✓fullprobed9/10

   Braintrust supports headless/CI usage via code-based Eval() runs, an API for programmatic control, a CLI (`bt`) for auth/eval/log operations from the terminal, and explicit documentation of CI/CD integration to run evals on every pull request. This combination clearly enables automated, non-interactive operation in pipelines. Missing for 10: independent hands-on confirmation of CI pipeline usage beyond vendor docs.

   • [claimed-docs] “Automate in CI/CD — Run evals on every pull request to catch regressions”
   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [probe] “official CLI documented at https://www.braintrust.dev/docs/reference/cli/quickstart”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Braintrust
   LangSmith~partialprobed4/10

   There is direct evidence of an official LangSmith MCP server repository (langsmith-mcp-server), confirming LangSmith ships a first-party MCP server that agents could connect to. However, the evidence pack has no further detail on setup, supported tools/capabilities, or independent confirmation of it working end-to-end with an agent, so the story is only thinly supported. missing for 10: detailed docs on MCP server capabilities/setup, independent/hands-on verification that an agent successfully connects and uses it, and integration guidance beyond the bare repo reference.

   • [probe] “official MCP server documented at https://github.com/langchain-ai/langsmith-mcp-server”

   proof ↗⚑ flag

   Braintrust✓fullprobed8/10

   Braintrust documents an official MCP server that lets Claude Code, Cursor, Codex, VS Code, and other MCP-compatible clients query logs, author prompts/scorers, configure monitoring, and run evals — a clear server-side MCP offering that agents can connect to. Missing for 10: independent/hands-on third-party confirmation that the MCP server works as documented (only first-party docs and a probe confirm its existence).

   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”
   • [claimed-docs] “Connect Claude Code, Cursor, Codex, and other MCP clients to Braintrust. Query logs, author scorers, configure Topics, and run evals from yo…”
   • [probe] “official MCP server documented at https://www.braintrust.dev/docs/integrations/developer-tools/mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Braintrust
   LangSmith—none0/10

   No evidence pack item mentions an official LangSmith CLI tool; the SDKs (Python/TS/Go/Java) and APIs are referenced but not a dedicated CLI for AI-native workflows.

   ⚑ flag

   Braintrust✓fullprobed9/10

   Braintrust ships an official `bt` CLI, documented with a dedicated quickstart, allowing authentication, tracing coding-agent sessions, running evals, browsing/querying logs, syncing data, and managing functions from the terminal — directly matching AI-native/agentic CLI usage. Missing for 10: independent/hands-on community corroboration of the CLI itself (community evidence is generic, not CLI-specific).

   • [claimed-docs] “Install the `bt` CLI to set up, instrument, and run Braintrust with your coding agent”
   • [claimed-docs] “It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, sync data, and manage functions without leaving you…”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with [`bt view logs`](/docs/reference/cli/view).”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”
   • [probe] “official CLI documented at https://www.braintrust.dev/docs/reference/cli/quickstart”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Braintrust
   LangSmith~partialprobed6/10

   LangSmith explicitly advertises programmatic access ('Filter, export, share, and compare traces... via the UI or API') and ships official SDKs for Python, TypeScript, Go, and Java plus webhook-based automation, indicating a documented public API surface. However, a probe for a discoverable OpenAPI/swagger spec returned 404s across standard paths, suggesting no easily found canonical API reference, and no independent developer confirmation of full API coverage was found. missing for 10: a public OpenAPI/reference doc, independent/hands-on confirmation of API completeness.

   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”
   • [claimed-docs] “Trace your preferred framework or integrate LangSmith with any agent stack using our Python, Typescript, Go, or Java SDKs.”
   • [claimed-docs] “Automate workflows with rules, webhooks, and online evaluations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.langchain.com/openapi.json, https://docs.langchain.com/swagger.json, https://docs.langc…”

   proof ↗⚑ flag

   Braintrust✓fullprobed8/10

   Braintrust documents a full public API reference for managing projects, experiments, datasets, prompts, scorers, and logging programmatically (braintrust-docs-11, -34), backed by SDKs (braintrust-gh-1/2), a CLI (braintrust-docs-33), and MCP server for agent-driven access (braintrust-docs-9, -25). Missing for 10: no discoverable OpenAPI/swagger spec (braintrust-probe-3 shows 404s) and no independent third-party corroboration of API robustness beyond docs.

   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.braintrust.dev/openapi.json, https://www.braintrust.dev/swagger.json, https://www.braint…”
   • [probe] “official CLI documented at https://www.braintrust.dev/docs/reference/cli/quickstart”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   LangSmith—none0/10

   The evidence pack covers tracing, evaluation, dashboards, alerts, and self-hosting, but contains no mention of API key scoping, permissions, roles, or least-privilege credential issuance for agents. No documentation of scoped/limited API keys or RBAC-style credential controls is present.

   ⚑ flag

   Braintrust—none0/10

   The evidence describes Braintrust's general API, CLI, and MCP integrations but contains no mention of scoped, role-based, or least-privilege API key/credential issuance for agents; the only security-related item is a breach report telling customers to rotate keys, which does not demonstrate a scoping/least-privilege capability.

   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [community] “AI evaluation startup Braintrust confirms breach, tells every customer to rotate sensitive keys.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   LangSmith✓fullcommunity8/10

   LangSmith documents official SDKs in Python, TypeScript, Go, and Java, backed by a public GitHub SDK repo with working code examples (e.g., wrap_openai), and also supports OpenTelemetry-based tracing for any compatible stack. Missing for 10: independent hands-on verification of SDK completeness across all four languages, and community notes (langsmith-comm-3) indicate weaker support for non-LangChain frameworks like crewai, which slightly tempers confidence in universal SDK-native coverage.

   • [claimed-docs] “Trace your preferred framework or integrate LangSmith with any agent stack using our Python, Typescript, Go, or Java SDKs.”
   • [github] “client = wrap_openai(openai.Client())”
   • [claimed-docs] “LangSmith supports OpenTelemetry-based tracing, allowing you to send traces from any OpenTelemetry-compatible application.”
   • [community] “Langsmith only shows the llm inferences. Also it hardly works with other frameworks like crewai for instance.”

   proof ↗⚑ flag

   Braintrust✓fullprobed8/10

   Braintrust ships official JS SDK (github examples using Eval()), an API reference for programmatic access, a CLI (bt), and an MCP server, giving AI-native developers multiple official, documented ways to build against the platform. One community comment calls docs 'sparse' but this is general skepticism, not a concrete contradiction of SDK functionality. missing for 10: independent hands-on validation of the SDK itself (beyond vendor docs/examples) and a public OpenAPI spec (probe found 404s).

   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”
   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”
   • [probe] “official MCP server documented at https://www.braintrust.dev/docs/integrations/developer-tools/mcp”
   • [probe] “official CLI documented at https://www.braintrust.dev/docs/reference/cli/quickstart”
   • [community] “Braintrust: Interesting approach to evaluation but feels like an early-stage product. Documentation is sparse and integration options are li…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to LangSmith
   LangSmith~partialclaimed6/10

   LangSmith docs explicitly state that alerts and automation rules can route to webhooks/any HTTP endpoint, letting users subscribe to events like errors, cost, or feedback thresholds via webhook. However, this is scoped to alert/automation rules rather than a general-purpose event subscription API, and there's no independent or hands-on confirmation of webhook reliability or payload structure. missing for 10: broader documentation of webhook event types/payloads beyond alert thresholds, independent/hands-on validation of webhook delivery.

   • [claimed-docs] “Automate workflows with rules, webhooks, and online evaluations.”
   • [claimed-docs] “Alerts can route to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”
   • [claimed-docs] “Alerts can [route](#step-4-configure-notification-channel) to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”

   proof ↗⚑ flag

   Braintrust—none0/10

   No evidence in the pack mentions webhooks or any event-subscription mechanism; Braintrust's documented interfaces are API, CLI, MCP server, and UI, none of which are shown to support webhook subscriptions.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Braintrust
   LangSmith~partialcommunity5/10

   LangSmith offers LLM-as-judge evaluators, automated root-cause detection via 'LangSmith Engine' (langsmith-docs-6), and alerting/dashboards that surface quality signals, which constitute AI-generated insight generation embedded in the product. However, evidence doesn't show a general-purpose AI assistant proactively surfacing free-form suggestions across the whole product, and community feedback notes trace visibility is LLM-inference-only and framework-limited (langsmith-comm-3). Missing for 10: broader proactive AI-generated recommendations beyond eval/root-cause detection, first-hand demonstration of LangSmith Engine's insight quality, and independent corroboration of its effectiveness.

   • [claimed-docs] “Automatically detect recurring issues in your traces, diagnose their root cause, and resolve them with LangSmith Engine.”
   • [claimed-docs] “Create evaluators to score performance: Human review, Code rules, LLM-as-judge, Pairwise comparison”
   • [claimed-docs] “Set up evaluators to run automatically on production traces: safety checks, format validation, quality heuristics, and reference-free LLM-as…”
   • [claimed-docs] “Human review * Code rules * LLM-as-judge * Pairwise comparison”
   • [community] “Langsmith only shows the llm inferences. Also it hardly works with other frameworks like crewai for instance.”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Braintrust ships Loop, an AI agent that investigates logs via natural language and can build scorers/datasets/dashboards, plus Patterns which proactively scans trace backlogs for recurring issues and suggests fixes, and Topics which auto-clusters/classifies traces against business dimensions — all directly generating AI insights/suggestions inside the product. Missing for 10: independent/hands-on validation of Loop/Patterns quality (evidence is vendor docs only) and no third-party review confirming suggestion usefulness.

   • [claimed-docs] “Loop is Braintrust’s AI agent. It understands your data structure, so you can investigate your logs through natural language instead of writ…”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Ask Braintrust’s AI agent to investigate your data and build scorers, datasets, and dashboards”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Topics automatically analyze and classify your logs without manual review.”
   • [claimed-docs] “Define the dimensions that matter to your business, like use case, customer segment, compliance, or tone. Topics continuously clusters every…”
   • [claimed-docs] “Topics automatically analyze and classify your logs without manual review. Each trace is analyzed by facets that extract sho”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   LangSmith~partialclaimed6/10

   LangSmith supports background automations via rules/webhooks, alerts that route to Slack/PagerDuty/HTTP endpoints, and online evaluators that run automatically on live production traces without user intervention (docs-4, docs-10, docs-12/13). It also offers optional 'LangSmith Deployment' to run and manage agents (docs-17), suggesting some autonomous agent execution capability, but this is a secondary/optional feature and detail is thin. Missing for 10: independent/hands-on evidence that these automations actually run unattended over time, more detail on scheduling/triggers beyond alerts, and clearer scope of 'LangSmith Deployment' for autonomous agent runs.

   • [claimed-docs] “Automate workflows with rules, webhooks, and online evaluations.”
   • [claimed-docs] “Set up evaluators to run automatically on production traces: safety checks, format validation, quality heuristics, and reference-free LLM-as…”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”
   • [claimed-docs] “Alerts can route to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”

   proof ↗⚑ flag

   Braintrust~partialclaimed6/10

   Braintrust supports autonomous background automation via 'Patterns', which runs Loop (its AI agent) on a schedule against the trace backlog to surface recurring issues and suggested fixes, plus online scoring that runs asynchronously on production traces and CI/CD-triggered evals. However, this is narrower than general-purpose autonomous automations — it's scoped to trace analysis/scoring rather than arbitrary user-defined background tasks, and there's no independent/hands-on corroboration of Patterns actually running unattended. Missing for 10: broader/customizable scheduled automation beyond Patterns and online scoring, independent evidence of reliability, and detail on failure handling or configurability of these background jobs.

   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they’re logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they're logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Automate in CI/CD — Run evals on every pull request to catch regressions”
   • [claimed-docs] “Loop is Braintrust’s AI agent. It understands your data structure, so you can investigate your logs through natural language instead of writ…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Braintrust
   LangSmith~partialclaimed3/10

   LangSmith Engine is described as automatically detecting recurring issues, diagnosing root causes, and resolving them, which functions like a built-in AI assistant for debugging tasks, but this is only a single, thin doc line with no further elaboration, UI walkthrough, or independent corroboration of how tasks are 'delegated' to it. missing for 10: detailed documentation of assistant capabilities/UX, examples of delegated task execution, independent/hands-on confirmation.

   • [claimed-docs] “Automatically detect recurring issues in your traces, diagnose their root cause, and resolve them with LangSmith Engine.”

   proof ↗⚑ flag

   Braintrust✓fullclaimed7/10

   Braintrust ships "Loop," a built-in AI agent that can investigate logs via natural language, build scorers/datasets/dashboards, and "Patterns" which runs Loop automatically on trace backlogs to surface issues and fixes — a clear built-in AI assistant delegated to perform tasks within the product. missing for 10: independent/hands-on user validation of Loop's task delegation (community evidence is thin/mixed and doesn't specifically address Loop), and more detail on the scope/limits of tasks it can autonomously complete.

   • [claimed-docs] “Loop is Braintrust’s AI agent. It understands your data structure, so you can investigate your logs through natural language instead of writ…”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Ask Braintrust’s AI agent to investigate your data and build scorers, datasets, and dashboards”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Loop is Braintrust's AI agent. It understands your data structure, so you can investigate your logs through natural language instead of writ…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Braintrust
   LangSmith—none0/10

   LangSmith is an observability/evaluation platform with a UI, API, and SDKs, but there is no evidence of natural-language command interfaces for operating the product itself (e.g., a chat-based control plane). The MCP server exposes tools to agents but that's a different axis from a user issuing NL commands to operate the product. missing for 10: any documented NL command interface, chat-based control of dashboards/alerts/experiments, or evidence of conversational operation.

   • [probe] “official MCP server documented at https://github.com/langchain-ai/langsmith-mcp-server”

   proof ↗⚑ flag

   Braintrust✓fullprobed8/10

   Braintrust's Loop agent lets users investigate logs and build scorers/datasets/dashboards via natural language instead of writing queries, and this is exposed through an official MCP server so natural-language commands work from Claude Code, Cursor, Codex, etc. Missing for 10: independent hands-on validation of natural-language command accuracy/reliability and broader coverage beyond Loop's stated scope.

   • [claimed-docs] “Loop is Braintrust’s AI agent. It understands your data structure, so you can investigate your logs through natural language instead of writ…”
   • [claimed-docs] “Ask Braintrust’s AI agent to investigate your data and build scorers, datasets, and dashboards”
   • [claimed-docs] “Loop is Braintrust's AI agent. It understands your data structure, so you can investigate your logs through natural language instead of writ…”
   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”
   • [claimed-docs] “Connect Claude Code, Cursor, Codex, and other MCP clients to Braintrust. Query logs, author scorers, configure Topics, and run evals from yo…”
   • [probe] “official MCP server documented at https://www.braintrust.dev/docs/integrations/developer-tools/mcp”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   LangSmith—none0/10

   No evidence of an interactive API reference with runnable examples; the OpenAPI probe explicitly returned 404s at all candidate paths, and no docs mention a Swagger/Redoc-style interactive reference or embedded runnable code snippets.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.langchain.com/openapi.json, https://docs.langchain.com/swagger.json, https://docs.langc…”

   proof ↗⚑ flag

   Braintrust—none0/10

   Braintrust has an API reference page (braintrust-docs-11/34) but the evidence pack shows no interactive or runnable-example capability — probes for an OpenAPI/swagger spec (needed for typical interactive API explorers) all returned 404, and there's no mention of a try-it-now console or embedded runnable snippets in the API reference itself. missing for 10: evidence of an interactive API console, runnable code snippets embedded in the reference, or a machine-readable OpenAPI spec powering such interactivity.

   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.braintrust.dev/openapi.json, https://www.braintrust.dev/swagger.json, https://www.braint…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.braintrust.dev/docs.md”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   LangSmith—none0/10

   LangSmith exposes a REST API (referenced for filtering/exporting traces) but the evidence pack shows a direct probe for OpenAPI/swagger specs at the docs site returned 404 on all candidate paths, and no other citation points to a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.langchain.com/openapi.json, https://docs.langchain.com/swagger.json, https://docs.langc…”
   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”

   proof ↗⚑ flag

   Braintrust—none0/10

   Braintrust documents a REST API (api-reference) but explicit probes for OpenAPI/swagger specs at all standard paths returned 404, and no docs mention a downloadable machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.braintrust.dev/openapi.json, https://www.braintrust.dev/swagger.json, https://www.braint…”
   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to LangSmith
   LangSmith~partialclaimed5/10

   LangSmith supports datasets with curated/synthetic examples and running evaluations/experiments against them separately from production traces, which functions like a sandbox testing workflow rather than testing directly on live production data. However, there's no explicit documentation of an isolated 'sandbox environment' concept, staging/prod environment separation, or data isolation guarantees — evaluation datasets can be built from historical production traces, blurring the separation. missing for 10: explicit sandbox/staging environment documentation, guarantees of production data isolation, and independent confirmation that dataset-based testing avoids touching production systems.

   • [claimed-docs] “Create a dataset with examples from manually curated test cases, historical production traces, or synthetic data generation.”
   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”
   • [claimed-docs] “Run evaluations on curated datasets during development to compare versions, benchmark performance, and catch regressions.”
   • [claimed-docs] “Create a [dataset](/langsmith/manage-datasets) with [examples](/langsmith/evaluation-concepts#examples) from manually curated test cases, hi…”
   • [claimed-docs] “Execute your application on the dataset to create an [experiment](/langsmith/evaluation-concepts#experiment). Configure [repetitions, concur…”

   proof ↗⚑ flag

   Braintrust~partialclaimed4/10

   Braintrust supports evals/experiments/datasets and separate projects that could function as a sandbox for testing without hitting production logs, and self-hosting offers infrastructure isolation, but there is no explicit documentation of a dedicated 'sandbox environment' or isolation guarantee preventing test runs from touching production data. missing for 10: explicit sandbox/staging environment concept, documentation on isolating test evals from production datasets/logs, and independent confirmation that eval runs never write to production stores.

   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [claimed-docs] “Datasets are versioned collections of test cases that you use to run evaluations and track improvements over time. Build datasets from produ…”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management.”
   • [claimed-docs] “Self-hosting is designed for organizations with specific requirements: Data residency and compliance: Meet regulatory or contractual obligat…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   LangSmith—none0/10

   No evidence pack item documents API versioning scheme or a deprecation policy; the OpenAPI probe returned 404s and no docs page addresses version support lifecycle or breaking-change policy.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.langchain.com/openapi.json, https://docs.langchain.com/swagger.json, https://docs.langc…”

   proof ↗⚑ flag

   Braintrust—none0/10

   There is an API reference documenting functionality, but no evidence of API versioning scheme or any documented deprecation policy; probes even show no OpenAPI spec discoverable at standard locations. Missing for 10: versioning scheme documentation, explicit deprecation policy, changelog/migration guides.

   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.braintrust.dev/openapi.json, https://www.braintrust.dev/swagger.json, https://www.braint…”

   proof ↗⚑ flag

Monitoring

1. ml engineerBuild custom dashboards over latency, error, cost, and eval-score metrics

   weight 2 · round to LangSmith
   LangSmith✓fullclaimed8/10

   LangSmith docs explicitly describe building custom dashboards ('tailored collections of charts') and prebuilt dashboards covering trace count, error rates, token usage, plus threshold alerts on Run Count, Cost, Errors, Feedback Score, and Latency, covering latency, error, cost, and eval-score metrics with group-by tag/metadata support for slicing. Missing for 10: independent/hands-on confirmation of dashboard-building UX and eval-score charting specifically.

   • [claimed-docs] “Prebuilt dashboards are created automatically for each project and cover essential metrics, such as trace count, error rates, token usage, a…”
   • [claimed-docs] “Create tailored collections of charts for tracking metrics that matter most for your application.”
   • [claimed-docs] “Custom dashboards: Collections of charts you can configure to your needs.”
   • [claimed-docs] “You can use group by [run tag or metadata](/langsmith/add-metadata-tags) to split data over attributes that are important to your applicatio…”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”
   • [claimed-docs] “You can use group by run tag or metadata to split data over attributes that are important to your application.”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust captures latency, token/cost, and eval-score metrics via tracing and experiments (braintrust-docs-1, braintrust-docs-27), and one doc line explicitly says you can 'ask Braintrust's AI agent to investigate your data and build scorers, datasets, and dashboards' (braintrust-docs-18), implying custom dashboard creation. However there is no dedicated dashboard-building documentation, no detail on customizing charts/widgets, and no explicit mention of error-rate metrics or alerting tied to dashboards. Missing for 10: dedicated dashboard-configuration docs, explicit error-metric support, and independent/hands-on evidence of building a custom dashboard.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [claimed-docs] “Ask Braintrust’s AI agent to investigate your data and build scorers, datasets, and dashboards”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they're logged, running asynchronously with no impact on latency.”

   proof ↗⚑ flag

2. developerSet alerts on error rates, cost spikes, or eval-score drops and get notified in Slack, PagerDuty, or email

   weight 2 · round to LangSmith
   LangSmith✓fullclaimed8/10

   LangSmith docs explicitly describe threshold-based alerting on Errors, Cost, Feedback Score (eval score), Run Count, and Latency, with routing to Slack, PagerDuty, Dynatrace, or any HTTP webhook (which can cover email/other integrations), directly matching the story. Missing for 10: independent/hands-on confirmation of alert delivery reliability and no explicit mention of native email notification channel beyond webhook routing.

   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”
   • [claimed-docs] “Alerts can route to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics:”
   • [claimed-docs] “Alerts can [route](#step-4-configure-notification-channel) to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”
   • [claimed-docs] “Build dashboards and set alerts to track quality and catch issues early.”

   proof ↗⚑ flag

   Braintrust—none0/10

   The evidence pack covers tracing, evals, online scoring, Loop/Patterns/Topics analysis, and self-hosting, but contains no mention of configurable alerts, thresholds, or notification integrations (Slack, PagerDuty, email) for error rates, cost spikes, or eval-score drops.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Braintrust
   LangSmith~partialclaimed6/10

   LangSmith documents dataset-wide evaluation runs (execute across many examples with configurable concurrency/repetitions), bulk trace filter/export/share/compare via API, and bulk dataset creation from historical traces or synthetic generation—supporting operations across many items at once. However, there's no explicit documentation of general bulk actions (e.g., bulk delete/tag/annotate across arbitrary trace sets) beyond evaluation and dataset contexts, and no independent/hands-on confirmation of bulk-op reliability at scale. Missing for 10: explicit bulk edit/delete/tag API documentation, independent hands-on verification of large-scale bulk operations.

   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”
   • [claimed-docs] “Create a dataset with examples from manually curated test cases, historical production traces, or synthetic data generation.”
   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”
   • [claimed-docs] “Create a [dataset](/langsmith/manage-datasets) with [examples](/langsmith/evaluation-concepts#examples) from manually curated test cases, hi…”
   • [claimed-docs] “Execute your application on the dataset to create an [experiment](/langsmith/evaluation-concepts#experiment). Configure [repetitions, concur…”
   • [github] “client = wrap_openai(openai.Client())”

   proof ↗⚑ flag

   Braintrust✓fullclaimed7/10

   Braintrust evals run against entire datasets in one operation, Patterns scans the full trace backlog on a schedule, Topics classifies every trace automatically, and the CLI/API support bulk sync ('bt sync pull'), bulk log queries, and programmatic management of experiments/datasets/prompts at scale. Missing for 10: explicit documentation of bulk edit/delete/update operations on datasets or logs, and independent (non-vendor) confirmation of bulk-operation performance at scale.

   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they’re logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Topics automatically analyze and classify your logs without manual review.”
   • [claimed-docs] “Datasets are versioned collections of test cases that you use to run evaluations and track improvements over time. Build datasets from produ…”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to LangSmith
   LangSmith~partialclaimed6/10

   LangSmith documents rule-based automation via threshold alerts (run count, cost, errors, feedback score, latency) that route to Slack, PagerDuty, Dynatrace, or webhooks, and separately mentions 'rules, webhooks, and online evaluations' as automation primitives. This covers automatic action-on-event but is scoped mainly to monitoring/alerting metrics rather than a general-purpose rule engine for arbitrary events. Missing for 10: detailed documentation of the 'rules' feature itself (beyond the one-line mention), broader event types beyond the five alert metrics, and independent/hands-on confirmation that rule-triggered actions work reliably in practice.

   • [claimed-docs] “Automate workflows with rules, webhooks, and online evaluations.”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”
   • [claimed-docs] “Alerts can route to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics:”
   • [claimed-docs] “Alerts can [route](#step-4-configure-notification-channel) to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust supports several automatic, event-driven behaviors — online scoring runs automatically on every new production trace, evals run automatically in CI/CD on pull requests, and Patterns runs Loop against traces on a schedule — but these are fixed built-in automations rather than a general user-defined 'if event then action' rules engine (e.g., no evidence of custom triggers/webhooks/alerts tied to arbitrary conditions). Missing for 10: a documented rules/alerting framework letting users define arbitrary trigger conditions and custom actions, and independent confirmation of this automation depth.

   • [claimed-docs] “Online scoring evaluates production traces automatically as they’re logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they're logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Automate in CI/CD — Run evals on every pull request to catch regressions”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Braintrust
   LangSmith—none0/10

   LangSmith documents automation via rules, webhooks, and online evaluations triggered on production traces, but there is no evidence of a scheduler or cron-like capability for recurring jobs/workflows (e.g., scheduled dataset evaluations or periodic report runs). Since automation is otherwise a supported theme for this platform, the absence of scheduling evidence makes this 'none' rather than 'na'.

   • [claimed-docs] “Automate workflows with rules, webhooks, and online evaluations.”
   • [claimed-docs] “Set up evaluators to run automatically on production traces: safety checks, format validation, quality heuristics, and reference-free LLM-as…”
   • [claimed-docs] “Evaluate real user interactions in real-time to detect issues and measure quality on live traffic.”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust documents 'Patterns,' which runs Loop on the trace backlog 'on a schedule' to find recurring issues, and separately supports triggering evals via CI/CD — both are forms of recurring automation. However, there's no evidence of general-purpose, user-configurable recurring job/workflow scheduling (e.g., cron-like scheduling for arbitrary evals, datasets, or pipelines) beyond this specific built-in feature. Missing for 10: user-defined scheduling API/UI for arbitrary evals or workflows, documentation of schedule configuration options, and independent confirmation of reliability.

   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Automate in CI/CD — Run evals on every pull request to catch regressions”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Braintrust
   LangSmith—none0/10

   LangSmith documents automation rules, webhooks, and dashboards but no evidence describes versioning, review workflows, or rollback capabilities for these automations. Missing for 10: version history for rules/automations, review/approval workflow, rollback mechanism, and any documentation or community confirmation of these features.

   • [claimed-docs] “Automate workflows with rules, webhooks, and online evaluations.”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”
   • [claimed-docs] “Alerts can route to Slack, PagerDuty, Dynatrace, or any HTTP endpoint via webhook.”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust documents versioned datasets and immutable, comparable experiment records, plus CLI/API management of prompts, scorers, and functions, which gives some version/review capability for its automation artifacts (evals, scorers, prompts). However, there is no explicit documentation of a rollback mechanism for automations (e.g., reverting a prompt, scorer, or online-scoring rule to a prior version) or a review/approval workflow before rollback. Missing for 10: explicit rollback functionality, version history UI/CLI commands, and independent confirmation that rollback works in practice.

   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [claimed-docs] “Datasets are versioned collections of test cases that you use to run evaluations and track improvements over time. Build datasets from produ…”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”

   proof ↗⚑ flag

Cost tracking

1. developerAttribute cost and usage to users, sessions, and features via custom metadata

   weight 2 · round to LangSmith
   LangSmith✓fullclaimed7/10

   LangSmith docs show custom metadata/tags can be attached to traces and used to group dashboard metrics (including token usage) by attribute, and alerts can be set on cost, enabling attribution of cost/usage to arbitrary dimensions like user, session, or feature via metadata. Missing for 10: a concrete worked example of per-user/session/feature cost breakdown and independent/hands-on corroboration that metadata-based cost attribution works well in practice.

   • [claimed-docs] “You can use group by run tag or metadata to split data over attributes that are important to your application.”
   • [claimed-docs] “You can use group by [run tag or metadata](/langsmith/add-metadata-tags) to split data over attributes that are important to your applicatio…”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”
   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics:”
   • [claimed-docs] “Prebuilt dashboards are created automatically for each project and cover essential metrics, such as trace count, error rates, token usage, a…”
   • [claimed-docs] “Custom dashboards: Collections of charts you can configure to your needs.”

   proof ↗⚑ flag

   Braintrust~partialclaimed4/10

   Braintrust's tracing captures token usage and custom metadata for every request, which is the raw ingredient for cost attribution, but no evidence describes dashboards, filters, or reports that actually roll up cost/usage by user, session, or feature tags. missing for 10: explicit cost-attribution UI/reporting by custom metadata dimensions, user/session/feature breakdown examples, and independent confirmation this works in practice.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Add tracing to your AI application to capture LLM calls, application logic, and user feedback — the foundation for observability and evaluat…”

   proof ↗⚑ flag

2. developerSee cost and token usage per request, model, and time period in dashboards

   weight 3 · round to LangSmith
   LangSmith✓fullclaimed8/10

   LangSmith documents prebuilt per-project dashboards covering token usage and cost, threshold-based cost alerting, and custom dashboards with group-by tag/metadata to slice metrics by model or time period, directly matching the story. missing for 10: independent/hands-on confirmation of the cost-per-model breakdown specifically and no third-party validation of dashboard accuracy.

   • [claimed-docs] “LangSmith provides threshold-based alerting on the following metrics: Run Count, Cost, Errors, Feedback Score, Latency”
   • [claimed-docs] “Prebuilt dashboards are created automatically for each project and cover essential metrics, such as trace count, error rates, token usage, a…”
   • [claimed-docs] “Create tailored collections of charts for tracking metrics that matter most for your application.”
   • [claimed-docs] “You can use group by run tag or metadata to split data over attributes that are important to your application.”
   • [claimed-docs] “Custom dashboards: Collections of charts you can configure to your needs.”
   • [claimed-docs] “You can use group by [run tag or metadata](/langsmith/add-metadata-tags) to split data over attributes that are important to your applicatio…”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust's tracing explicitly captures token usage per request (braintrust-docs-1) and traces/spans can be browsed in the UI or terminal (braintrust-docs-14/19/35), which supports basic usage visibility, but the evidence never mentions a cost metric, cost calculation, or a dedicated dashboard aggregating cost/tokens by model or time period. Missing for 10: explicit cost tracking/computation, dashboard views aggregating usage by model, dashboard views aggregating usage by time period, and any independent confirmation of these dashboard features.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with [`bt view logs`](/docs/reference/cli/view).”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with [`bt view logs`]”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”

   proof ↗⚑ flag

Data export

1. developerBulk-export traces and datasets to blob storage or my data warehouse

   weight 2 · round to Braintrust
   LangSmith~partialclaimed3/10

   Docs mention the ability to 'export' traces via UI or API, but there is no evidence of bulk export tooling, blob storage integration (S3/GCS), or data warehouse connectors (BigQuery/Snowflake) specifically designed for large-scale export. missing for 10: dedicated bulk-export API/CLI docs, blob storage integration, data warehouse connector documentation, and any hands-on confirmation of large-scale export workflows.

   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust supports exporting logs/traces via CLI (`bt sync pull`, download as CSV/JSON) and a full API for programmatic access to traces, datasets, and experiments, which developers could pipe into blob storage or a warehouse themselves. However, there is no documented native connector or bulk-export feature specifically targeting blob storage (S3/GCS) or data warehouses (Snowflake/BigQuery) — missing for 10: dedicated warehouse/blob-storage export integrations, scheduled/automated bulk export pipelines, and independent confirmation of large-scale export performance.

   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”

   proof ↗⚑ flag

Ai eval ops

1. ai-native userHave an agent create a dataset, trigger an eval run programmatically, and read back the results

   weight 2 · round to Braintrust
   LangSmith✓fullprobed7/10

   LangSmith docs and SDK show programmatic dataset creation (from curated data, traces, or synthetic generation), programmatic evaluator/experiment execution (`Execute your application on the dataset to create an experiment`), and API/SDK access to trace/experiment results, all reachable from Python/TS/Go/Java SDKs, and an official MCP server exists so an agent can invoke these operations as tools. Missing for 10: a concrete end-to-end code sample showing an agent creating a dataset, kicking off an eval, and parsing results back, plus independent hands-on confirmation of the MCP server workflow.

   • [claimed-docs] “Create a dataset with examples from manually curated test cases, historical production traces, or synthetic data generation.”
   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”
   • [claimed-docs] “Create evaluators to score performance: Human review, Code rules, LLM-as-judge, Pairwise comparison”
   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”
   • [github] “client = wrap_openai(openai.Client())”
   • [probe] “official MCP server documented at https://github.com/langchain-ai/langsmith-mcp-server”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Braintrust provides programmatic APIs and MCP/CLI tooling that let an agent create datasets, trigger evals, and read back results: the API supports creating/managing datasets and experiments, the SDK's Eval() function runs evals programmatically, and the MCP server/CLI explicitly let agents like Claude Code/Cursor 'run evals' and 'query logs' from within their workflow. missing for 10: a concrete end-to-end example showing an agent specifically creating a dataset via API/MCP and then reading back eval results in one flow, and independent (non-vendor) confirmation of this specific workflow.

   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”
   • [claimed-docs] “Connect Claude Code, Cursor, Codex, and other MCP clients to Braintrust. Query logs, author scorers, configure Topics, and run evals from yo…”
   • [claimed-docs] “It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, sync data, and manage functions without leaving you…”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “Datasets are versioned collections of test cases that you use to run evaluations and track improvements over time. Build datasets from produ…”
   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”

   proof ↗⚑ flag

Human review

1. ml engineerRoute outputs to human annotation queues for review and labeling

   weight 2 · round to LangSmith
   LangSmith✓fullclaimed8/10

   LangSmith explicitly supports 'Annotate outputs and gather user feedback using queues or inline annotation' and lists 'Human review' as a first-class evaluator type, directly matching the routing-to-annotation-queue story. missing for 10: no independent/hands-on corroboration of the annotation queue workflow beyond first-party docs, and no detail on queue assignment/collaboration features.

   • [claimed-docs] “Annotate outputs and gather user feedback using queues or inline annotation.”
   • [claimed-docs] “Create evaluators to score performance: Human review, Code rules, LLM-as-judge, Pairwise comparison”
   • [claimed-docs] “Human review * Code rules * LLM-as-judge * Pairwise comparison”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust supports building custom annotation interfaces for human review and labeling (docs-12) and datasets can be built/curated from production logs and manual curation (docs-5, docs-31), implying human review workflows, but there's no explicit evidence of a dedicated 'routing' mechanism, queue assignment, reviewer task distribution, or workflow status tracking for human annotators. missing for 10: explicit queue/routing mechanism to assign outputs to specific human reviewers, task assignment/status tracking, and independent corroboration of the annotation workflow in practice.

   • [claimed-docs] “Build annotation interfaces that match your team's workflow. Review support conversations differently than co”
   • [claimed-docs] “Build datasets from production logs, user feedback, manual curation, or generate them with Loop.”
   • [claimed-docs] “Datasets are versioned collections of test cases that you use to run evaluations and track improvements over time. Build datasets from produ…”

   proof ↗⚑ flag

Offline evals

1. developerRun evals in CI and gate deployments on their results

   weight 2 · round to Braintrust
   LangSmith~partialclaimed5/10

   LangSmith supports running evaluations on datasets to compare versions and catch regressions, and can execute experiments programmatically, which could be invoked from a CI pipeline, but there is no documented CI integration, GitHub Actions example, exit-code/pass-fail gating mechanism, or deployment-gating workflow in the evidence pack. missing for 10: explicit CI/CD integration docs, pass/fail threshold gating mechanism, deployment-blocking example, independent confirmation of CI usage.

   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”
   • [claimed-docs] “Run evaluations on curated datasets during development to compare versions, benchmark performance, and catch regressions.”
   • [claimed-docs] “Execute your application on the dataset to create an [experiment](/langsmith/evaluation-concepts#experiment). Configure [repetitions, concur…”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Docs explicitly describe running evals via code/CLI, integrating into CI/CD to catch regressions, and gating on experiment results ('Automate in CI/CD — Run evals on every pull request to catch regressions'; 'integrate into CI/CD to catch regressions before they reach production'), backed by SDK eval code examples. Missing for 10: independent/hands-on confirmation of actual CI gating in production and details on failure-threshold/gate configuration.

   • [claimed-docs] “Automate in CI/CD — Run evals on every pull request to catch regressions”
   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”

   proof ↗⚑ flag

2. ml engineerWrite custom code-based scorers and metrics for my evaluations

   weight 2 · round drawn
   LangSmith✓fullclaimed8/10

   LangSmith docs explicitly list 'Code rules' as an evaluator type alongside LLM-as-judge, human review, and pairwise comparison, confirming support for custom code-based scorers/metrics in evaluations. Missing for 10: no concrete code example of writing a custom Python scorer function and no independent/hands-on corroboration of code-based evaluator usage.

   • [claimed-docs] “Create evaluators to score performance: Human review, Code rules, LLM-as-judge, Pairwise comparison”
   • [claimed-docs] “Human review * Code rules * LLM-as-judge * Pairwise comparison”
   • [claimed-docs] “Create [evaluators](/langsmith/evaluation-concepts#evaluators) to score performance:”
   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Braintrust's SDK examples show Eval() calls with custom `scores` arrays (e.g. LevenshteinScorer), demonstrating code-based custom scorers, and docs describe managing/authoring scorers via API, CLI, and playgrounds. Missing for 10: independent hands-on validation of writing a fully custom scorer function beyond the built-in Levenshtein example, and more detail on scorer authoring API/signature.

   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”

   proof ↗⚑ flag

3. ml engineerCompare eval runs side by side to catch regressions between prompt or model versions

   weight 3 · round to Braintrust
   LangSmith✓fullclaimed8/10

   LangSmith's evaluation docs explicitly describe running evaluations on curated datasets to 'compare versions, benchmark performance, and catch regressions,' with experiments generated per run and pairwise comparison evaluators supported, directly matching the story. Missing for 10: independent/hands-on confirmation of the side-by-side comparison UI experience and any community validation specific to regression-catching workflows.

   • [claimed-docs] “Run evaluations on curated datasets during development to compare versions, benchmark performance, and catch regressions.”
   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”
   • [claimed-docs] “Create evaluators to score performance: Human review, Code rules, LLM-as-judge, Pairwise comparison”
   • [claimed-docs] “Human review * Code rules * LLM-as-judge * Pairwise comparison”
   • [claimed-docs] “Execute your application on the dataset to create an [experiment](/langsmith/evaluation-concepts#experiment). Configure [repetitions, concur…”

   proof ↗⚑ flag

   Braintrust✓fullclaimed9/10

   Braintrust's Experiments feature is explicitly described as an immutable, comparable record of eval runs that tracks progress over time and integrates into CI/CD to catch regressions, and Playgrounds let users run full evaluations and compare results side-by-side across prompt/model configurations. This directly matches the story of comparing eval runs to catch regressions between versions. Missing for 10: independent/hands-on corroboration of the side-by-side comparison UI beyond first-party docs.

   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Automate in CI/CD — Run evals on every pull request to catch regressions”

   proof ↗⚑ flag

4. ml engineerScore outputs with configurable LLM-as-a-judge evaluators

   weight 3 · round drawn
   LangSmith✓fullclaimed8/10

   LangSmith's docs explicitly document creating LLM-as-judge evaluators (alongside human review, code rules, pairwise comparison) for both offline dataset experiments and online production traces, with configurable filters/sampling for cost control. Missing for 10: independent hands-on validation of LLM-as-judge accuracy/configurability and no first-party code snippet showing evaluator configuration in this pack.

   • [claimed-docs] “Create evaluators to score performance: Human review, Code rules, LLM-as-judge, Pairwise comparison”
   • [claimed-docs] “Set up evaluators to run automatically on production traces: safety checks, format validation, quality heuristics, and reference-free LLM-as…”
   • [claimed-docs] “Run evaluations on curated datasets during development to compare versions, benchmark performance, and catch regressions.”
   • [claimed-docs] “Evaluate real user interactions in real-time to detect issues and measure quality on live traffic.”
   • [claimed-docs] “Human review * Code rules * LLM-as-judge * Pairwise comparison”
   • [claimed-docs] “Set up [evaluators](/langsmith/online-evaluations-llm-as-judge) to run automatically on production traces: safety checks, format validation,…”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Braintrust's docs describe configurable scorers used within evals and playgrounds (LLM-as-a-judge style scorers), online scoring of production traces, and code examples show custom scorer configuration (e.g., LevenshteinScorer swapped in evals). Docs explicitly mention 'author scorers' via CLI/MCP and building scorers with Loop, supporting configurability. Missing for 10: explicit documentation naming 'LLM-as-a-judge' scorer templates/library and independent hands-on validation of judge configurability beyond vendor docs.

   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they’re logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they're logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Connect Claude Code, Cursor, Codex, and other MCP clients to Braintrust. Query logs, author scorers, configure Topics, and run evals from yo…”
   • [claimed-docs] “Ask Braintrust’s AI agent to investigate your data and build scorers, datasets, and dashboards”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”

   proof ↗⚑ flag

5. ml engineerCurate datasets from production traces and run offline evaluations against them

   weight 3 · round to Braintrust
   LangSmith✓fullclaimed8/10

   Docs explicitly describe creating datasets from historical production traces and running offline experiments/evaluations with configurable evaluators (human review, code rules, LLM-as-judge, pairwise comparison) to compare versions and catch regressions. Missing for 10: independent/hands-on corroboration of the dataset-curation-from-traces workflow specifically (community comments focus on tracing/observability, not dataset curation).

   • [claimed-docs] “Create a dataset with examples from manually curated test cases, historical production traces, or synthetic data generation.”
   • [claimed-docs] “Run evaluations on curated datasets during development to compare versions, benchmark performance, and catch regressions.”
   • [claimed-docs] “Create evaluators to score performance: Human review, Code rules, LLM-as-judge, Pairwise comparison”
   • [claimed-docs] “Execute your application on the dataset to create an experiment. Configure repetitions, concurrency, and caching to optimize runs.”
   • [claimed-docs] “Traces are the record of what your agents did in production. Use them to debug failures, monitor quality, and build the datasets you evaluat…”

   proof ↗⚑ flag

   Braintrust✓fullclaimed9/10

   Docs explicitly describe building versioned datasets from production logs/traces (docs-5, docs-31) and running offline evaluations against them via Experiments, code, or Playgrounds (docs-27, docs-23, gh-1/gh-2 SDK examples), with CI/CD integration for regression testing (docs-2). Missing for 10: independent/hands-on third-party validation of the end-to-end curate-from-production-to-offline-eval workflow beyond first-party docs.

   • [claimed-docs] “Build datasets from production logs, user feedback, manual curation, or generate them with Loop.”
   • [claimed-docs] “Datasets are versioned collections of test cases that you use to run evaluations and track improvements over time. Build datasets from produ…”
   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Automate in CI/CD — Run evals on every pull request to catch regressions”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”

   proof ↗⚑ flag

Online evals

1. ml engineerRun evaluators continuously on live production traffic, not just offline datasets

   weight 2 · round drawn
   LangSmith✓fullclaimed8/10

   Docs explicitly describe online evaluators that run automatically on production traces (safety checks, format validation, quality heuristics, reference-free LLM-as-judge) with filters/sampling to control cost, and separately describe real-time evaluation of live traffic distinct from offline dataset evals. This directly matches the story. Missing for 10: independent/hands-on confirmation of continuous online evaluators in practice (community evidence only covers tracing, not online eval specifically).

   • [claimed-docs] “Set up evaluators to run automatically on production traces: safety checks, format validation, quality heuristics, and reference-free LLM-as…”
   • [claimed-docs] “Evaluate real user interactions in real-time to detect issues and measure quality on live traffic.”
   • [claimed-docs] “Set up [evaluators](/langsmith/online-evaluations-llm-as-judge) to run automatically on production traces: safety checks, format validation,…”
   • [claimed-docs] “Automate workflows with rules, webhooks, and online evaluations.”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Braintrust explicitly supports 'online scoring' that evaluates production traces automatically as they're logged asynchronously with no latency impact, plus continuous background analysis via Patterns/Topics scanning trace backlogs on a schedule for issues no scorer already catches. This directly matches continuous evaluation on live traffic beyond offline datasets. Missing for 10: independent/hands-on verification of online scoring behavior in production and more detail on configuring which evaluators run continuously.

   • [claimed-docs] “Online scoring evaluates production traces automatically as they’re logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Online scoring evaluates production traces automatically as they're logged, running asynchronously with no impact on latency.”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Patterns puts Loop to work on your trace backlog on a schedule. It searches for recurring problems and trends that no scorer already measure…”
   • [claimed-docs] “Topics automatically analyze and classify your logs without manual review.”
   • [claimed-docs] “Define the dimensions that matter to your business, like use case, customer segment, compliance, or tone. Topics continuously clusters every…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Braintrust
   LangSmith~partialprobed5/10

   Docs explicitly state traces can be filtered, exported, shared, and compared 'via the UI or API', and SDKs (Python/TS/Go/Java) support tracing, dataset creation, and evaluation programmatically, suggesting real API parity for core workflows. However, there's no evidence of a full OpenAPI spec (probe for openapi.json returned 404s) or explicit API support for dashboard/alert creation, and community notes describe friction (e.g., needing a cloud account just to view your own traces) suggesting the API surface isn't fully self-serve/parity for all UI actions. missing for 10: published OpenAPI/API reference showing full UI-equivalent endpoints, explicit API methods for dashboards/alerts management, independent confirmation that all UI actions are scriptable.

   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”
   • [claimed-docs] “Trace your preferred framework or integrate LangSmith with any agent stack using our Python, Typescript, Go, or Java SDKs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.langchain.com/openapi.json, https://docs.langchain.com/swagger.json, https://docs.langc…”
   • [community] “I built this because LangSmith needs a cloud account to see my own traces.”

   proof ↗⚑ flag

   Braintrust~partialprobed7/10

   Braintrust offers a comprehensive API/SDK ('interact with all aspects of the Braintrust platform programmatically'), a full-featured CLI (bt) for auth, tracing, evals, log queries, and function management, and an MCP server letting agents query logs, author scorers, configure monitoring, and run evals — covering most UI functionality outside the terminal. However, some UI-only features like Playgrounds (explicitly 'no-code workspace') and annotation-interface building appear UI-centric without clear API/CLI parity, and no public OpenAPI spec was found to confirm full API coverage. missing for 10: confirmed OpenAPI/spec proving 1:1 API-UI parity, explicit API/CLI equivalent for Playgrounds and custom annotation UI workflows, independent verification of completeness.

   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, sync data, and manage functions without leaving you…”
   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”
   • [claimed-docs] “Connect Claude Code, Cursor, Codex, and other MCP clients to Braintrust. Query logs, author scorers, configure Topics, and run evals from yo…”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.braintrust.dev/openapi.json, https://www.braintrust.dev/swagger.json, https://www.braint…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Braintrust
   LangSmith~partialcommunity4/10

   LangSmith allows exporting traces via UI/API (langsmith-docs-2) and self-hosting your own instance (langsmith-docs-17), which gives some data portability, but there's no documented bulk-export tool, no explicit open-format guarantee (e.g., standard OTLP export of full trace history), and community comments note traces require a cloud account and lock-in concerns (langsmith-comm-5, langsmith-comm-1). missing for 10: a documented full-account data export/dump feature, explicit open-format (e.g., JSON/OTLP) export guarantees, and independent confirmation that exported data is complete and portable without vendor lock-in.

   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”
   • [community] “I built this because LangSmith needs a cloud account to see my own traces.”
   • [community] “LangSmith is excellent, but my usage is quite minimal, and I would prefer a locally hosted version that is easy to customize.”

   proof ↗⚑ flag

   Braintrust~partialclaimed5/10

   Braintrust provides data export via `bt sync pull`, `bt view logs` downloads as CSV/JSON, and a full API to programmatically extract projects, experiments, datasets, traces, and prompts, plus a self-hosting option for data control. However, there's no explicit documentation of full-account export/portability guarantees, no mention of open/standard interchange formats beyond CSV/JSON logs, and no independent confirmation of a clean 'leave' workflow. Missing for 10: comprehensive account-level export documentation, open-format guarantees for all entity types (prompts, scorers, configs), and third-party validation of export completeness.

   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”
   • [claimed-docs] “`bt` is the command-line interface for Braintrust. It lets you authenticate, trace coding-agent sessions, run evals, browse and query logs, …”
   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   LangSmith—none0/10

   Evidence shows an open-source client SDK (langsmith-sdk) and MCP server, but no indication that the core LangSmith platform/product itself is released under an open license — self-hosting docs describe running LangSmith in your own infra, not viewing or auditing its source code.

   • [github] “client = wrap_openai(openai.Client())”
   • [probe] “official MCP server documented at https://github.com/langchain-ai/langsmith-mcp-server”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”

   proof ↗⚑ flag

   Braintrust—none0/10

   Evidence shows only client SDK repos on GitHub (braintrust-sdk-javascript) and self-hosted deployment of infrastructure, but the core platform/UI is explicitly described as Braintrust-managed and not released under an open license; no evidence of the product's full source being open-licensed.

   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management. You deploy and control the infrastru…”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   LangSmith~partialcommunity6/10

   LangSmith explicitly documents self-hosting the core platform in your own infrastructure for observability, evaluation, and prompt engineering (with optional deployment management), which directly matches the story. However, community evidence shows at least one user built a workaround specifically because default LangSmith usage requires a cloud account to view traces, suggesting self-hosting is not the default/easy path and likely gated behind enterprise tiers rather than freely available like a fully open-source self-host. Missing for 10: independent hands-on confirmation of a successful self-hosted deployment, and clarity on licensing/tier restrictions for self-hosting.

   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering.”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for [observability](/langsmith/observability), [evaluation](/langsmith/evaluation),…”
   • [community] “I built this because LangSmith needs a cloud account to see my own traces.”

   proof ↗⚑ flag

   Braintrust~partialclaimed6/10

   Braintrust documents an official self-hosted deployment option, but it explicitly separates data storage (self-hosted) from platform management (Braintrust-managed UI, auth, updates), meaning it's not a fully self-hostable core product. Missing for 10: evidence of fully self-hosting the entire platform (UI, control plane, auth) independent of Braintrust's managed services, and independent/community confirmation of self-hosting experience.

   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management. You deploy and control the infrastru…”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management.”
   • [claimed-docs] “Self-hosting is designed for organizations with specific requirements: Data residency and compliance: Meet regulatory or contractual obligat…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Braintrust
   LangSmith~partialclaimed4/10

   LangSmith supports self-hosting your own instance in your own infrastructure (docs-17/23/32), which lets an organization control where data physically resides, but there is no documented cloud region-selection or data-residency feature (e.g., EU vs US region choice) for the hosted SaaS offering. missing for 10: explicit cloud data-residency/region selection options, documentation of supported regions, and any compliance certifications tied to residency.

   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering.”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for [observability](/langsmith/observability), [evaluation](/langsmith/evaluation),…”

   proof ↗⚑ flag

   Braintrust~partialclaimed6/10

   Braintrust's self-hosting docs explicitly state it's designed to meet data residency requirements by keeping customer data within your own cloud account and region, giving users region/residency control — but only via full self-hosted deployment, not a simple region-selection toggle in the managed cloud offering. Missing for 10: evidence of region choice within the standard hosted/SaaS plan, list of specific supported regions, and compliance certifications tied to residency.

   • [claimed-docs] “Self-hosting is designed for organizations with specific requirements: Data residency and compliance: Meet regulatory or contractual obligat…”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management. You deploy and control the infrastru…”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   LangSmith—none0/10

   The evidence pack contains no mention of a data-training opt-out, privacy policy, or commitment regarding use of customer trace data for model training; all evidence is about tracing, evaluation, dashboards, and self-hosting features, not privacy/training-data posture.

   ⚑ flag

   Braintrust—none0/10

   No evidence pack item addresses data-training opt-out, a no-training policy, or any statement about whether customer data is used to train AI models. Self-hosting docs address data residency/compliance but do not mention model training use. missing for 10: any explicit no-training-on-customer-data policy, opt-out controls, or terms-of-service statement about AI training use.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Braintrust
   LangSmith—none0/10

   The evidence pack contains no mention of data retention windows, deletion APIs, or user-controlled data lifecycle settings for traces/datasets in LangSmith. Self-hosting (langsmith-docs-17/23/32) offers indirect infrastructure control but is not evidence of an explicit retention/deletion feature.

   ⚑ flag

   Braintrust~partialclaimed4/10

   Braintrust's self-hosted deployment option lets customers keep all data within their own cloud account/region for compliance and residency, giving some control over where data lives, and the API/CLI allow programmatic management of logs and datasets. However, there is no explicit documentation of a retention policy, TTL settings, or a delete/purge API for logs, traces, or datasets on the managed (non-self-hosted) offering. Missing for 10: explicit retention window configuration, an in-platform delete/purge mechanism for traces or datasets, and confirmation that these controls exist outside of self-hosting.

   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management. You deploy and control the infrastru…”
   • [claimed-docs] “Braintrust offers a self-hosted deployment option that separates data storage from platform management.”
   • [claimed-docs] “Self-hosting is designed for organizations with specific requirements: Data residency and compliance: Meet regulatory or contractual obligat…”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   LangSmith—none0/10

   No evidence in the pack of any telemetry/usage-tracking opt-out setting for LangSmith itself; self-hosting (langsmith-docs-17/23/32) addresses data locality but doesn't address opting out of product telemetry, and community comments (langsmith-comm-1, langsmith-comm-5) actually highlight lack of control, needing a cloud account to view one's own traces.

   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”
   • [community] “LangSmith is excellent, but my usage is quite minimal, and I would prefer a locally hosted version that is easy to customize.”
   • [community] “I built this because LangSmith needs a cloud account to see my own traces.”

   proof ↗⚑ flag

   Braintrust—none0/10

   No evidence of any telemetry opt-out or usage-tracking control setting for Braintrust itself as a tool; the evidence covers Braintrust's own tracing/observability product features (for user's AI apps), not the vendor's own telemetry collection practices or an opt-out mechanism. Self-hosting controls where customer AI data resides but says nothing about product telemetry/usage tracking opt-out.

   ⚑ flag

Prompt workflow

1. developerIterate on prompts in a playground against real models and variables

   weight 2 · round to Braintrust
   LangSmith—none0/10

   The evidence pack mentions 'prompt engineering' and a 'prompt-context-hub#prompts' link in passing (langsmith-docs-17/23/32) but contains no description of a playground UI, testing against real models, or variable substitution for prompt iteration. Without concrete documentation of this specific capability, it cannot be credited as delivered.

   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering.”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for [observability](/langsmith/observability), [evaluation](/langsmith/evaluation),…”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Docs explicitly describe Playgrounds as a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets, running full evaluations in real-time against real models with variable inputs, and comparing results side-by-side (braintrust-docs-3, braintrust-docs-23, braintrust-docs-17). This directly matches the story of iterating on prompts in a playground against real models and variables. Missing for 10: independent/hands-on user corroboration of the playground experience specifically (community evidence is generic/mixed) and no detail on variable-substitution mechanics beyond the general description.

   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Measure and improve AI application quality with playgrounds and evals”

   proof ↗⚑ flag

2. developerVersion prompts and deploy changes to production without shipping code

   weight 3 · round to Braintrust
   LangSmith~partialclaimed4/10

   The evidence only references 'prompt engineering' and a 'prompt-context-hub#prompts' link within self-hosted/observability docs, implying a prompt management feature exists, but there is no detail on versioning, promotion workflows, or deploying prompt changes to production without code changes. Missing for 10: explicit docs on prompt version history, tagging/promotion to production, and evidence that apps pull prompts at runtime without redeploy.

   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable La…”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering.”
   • [claimed-docs] “Host an instance of LangSmith in your own infrastructure for [observability](/langsmith/observability), [evaluation](/langsmith/evaluation),…”

   proof ↗⚑ flag

   Braintrust~partialclaimed6/10

   Braintrust supports managing prompts via playgrounds, API, and CLI ("Manage prompts, tools, and scorers"), and datasets/experiments are versioned, suggesting prompt versioning is possible; however, there's no explicit evidence of a distinct 'deploy to production without code' workflow (e.g., prompt promotion/publish/rollback mechanism) separate from logging or evals. missing for 10: explicit prompt versioning/history UI, a documented deploy/publish/rollback mechanism for prompts, and independent confirmation that production apps can swap prompts without redeploying code.

   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [claimed-docs] “Playgrounds provide a no-code workspace for rapidly iterating on prompts, models, scorers, and datasets. Run full evaluations in real-time, …”
   • [claimed-docs] “Datasets are versioned collections of test cases that you use to run evaluations and track improvements over time. Build datasets from produ…”
   • [claimed-docs] “Experiments are the immutable, comparable record of your eval runs. Run them from code or in the UI, track progress over time, and integrate…”

   proof ↗⚑ flag

Ai observability

1. ai-native userHave an agent query my traces, metrics, and eval results through an API or MCP server to debug my app

   weight 3 · round to Braintrust
   LangSmith~partialprobed6/10

   LangSmith exposes traces via a documented API (filter/export via API) and has an official MCP server repo (langsmith-mcp-server) confirming agent-queryable access, but the evidence pack lacks detail on whether the MCP server or API surfaces metrics and eval results specifically, and no OpenAPI spec was found. Missing for 10: documented API/MCP coverage of metrics dashboards and eval-result querying, and independent confirmation the MCP server works well in practice.

   • [probe] “official MCP server documented at https://github.com/langchain-ai/langsmith-mcp-server”
   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”
   • [claimed-docs] “Trace your preferred framework or integrate LangSmith with any agent stack using our Python, Typescript, Go, or Java SDKs.”

   proof ↗⚑ flag

   Braintrust✓fullprobed9/10

   Braintrust documents a first-party MCP server enabling MCP-compatible agents (Claude Code, Cursor, Codex, etc.) to query logs, run evals, author scorers, and configure monitoring, plus a full programmatic API for traces/experiments/datasets, and Loop, Braintrust's own AI agent, for natural-language investigation of logs and eval data. This directly matches the story of an agent querying traces, metrics, and eval results via API or MCP to debug an app. Missing for 10: independent hands-on corroboration of the MCP server working end-to-end (only vendor docs/probe confirm existence, no third-party review of actual debugging workflow).

   • [claimed-docs] “Query production logs, author prompts and scorers, configure monitoring, and run evals from Claude Code, Cursor, Codex, VS Code, and any oth…”
   • [claimed-docs] “Connect Claude Code, Cursor, Codex, and other MCP clients to Braintrust. Query logs, author scorers, configure Topics, and run evals from yo…”
   • [claimed-docs] “Loop is Braintrust’s AI agent. It understands your data structure, so you can investigate your logs through natural language instead of writ…”
   • [claimed-docs] “Ask Braintrust’s AI agent to investigate your data and build scorers, datasets, and dashboards”
   • [claimed-docs] “The Braintrust API allows you to interact with all aspects of the Braintrust platform programmatically.”
   • [claimed-docs] “You can use it to: Create and manage projects, experiments, and datasets; Log traces and metrics; Manage prompts, tools, and scorers”
   • [probe] “official MCP server documented at https://www.braintrust.dev/docs/integrations/developer-tools/mcp”

   proof ↗⚑ flag

Data controls

1. developerMask or redact sensitive data before it is stored in traces

   weight 2 · round drawn
   LangSmith—none0/10

   No evidence in the pack mentions PII masking, redaction, or data filtering before trace storage; the docs cover tracing, evaluation, dashboards, alerts, and self-hosting but nothing about redacting sensitive data in traces.

   ⚑ flag

   Braintrust—none0/10

   No evidence in the pack describes any PII masking, redaction, or scrubbing feature for traces before storage; documentation covers instrumentation, tracing, evals, and observability but never mentions data masking or redaction capabilities. This is a plausible and common axis for a tracing/observability platform, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

Sdk coverage

1. developerInstrument apps in both Python and JS/TS with officially supported SDKs

   weight 2 · round to LangSmith
   LangSmith✓fullcommunity8/10

   Docs and GitHub SDK repo confirm official Python and TypeScript SDKs (plus Go/Java) for instrumenting apps, with wrap_openai example and OpenTelemetry-based tracing support as alternatives. missing for 10: independent hands-on corroboration of JS/TS SDK parity and depth beyond docs, and community feedback is mixed on framework compatibility outside core LangChain use cases.

   • [claimed-docs] “Trace your preferred framework or integrate LangSmith with any agent stack using our Python, Typescript, Go, or Java SDKs.”
   • [github] “client = wrap_openai(openai.Client())”
   • [claimed-docs] “LangSmith supports OpenTelemetry-based tracing, allowing you to send traces from any OpenTelemetry-compatible application.”
   • [community] “Langsmith only shows the llm inferences. Also it hardly works with other frameworks like crewai for instance.”
   • [community] “This is primarily based on the LangChain framework so it's fairly turnkey, but has no integration with the rest of your application... It's …”

   proof ↗⚑ flag

   Braintrust~partialclaimed6/10

   Docs confirm instrumentation/tracing is central to Braintrust and JS SDK usage is shown in GitHub examples (Eval function calls), with docs referencing SDK-based tracing and instrumentation broadly, but the evidence pack never explicitly confirms an officially supported Python SDK alongside JS/TS — only JS/TS SDK code is shown. Missing for 10: explicit Python SDK documentation/examples, side-by-side confirmation of parity between Python and JS/TS SDKs, and independent corroboration of both SDKs in production use.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Add tracing to your AI application to capture LLM calls, application logic, and user feedback — the foundation for observability and evaluat…”
   • [claimed-docs] “Integrate with AI providers and frameworks to send traces to Braintrust”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, { input: "Bar", expected: "Hello Bar" }, ], task: (in…”

   proof ↗⚑ flag

Trace capture

1. developerTrace multi-step agent runs as nested spans grouped into sessions or threads

   weight 2 · round drawn
   LangSmith~partialcommunity6/10

   Docs and community comments confirm LangSmith traces multi-step agent runs and lets you inspect each step in a graph/execution ('full traces of moving through the graph ... inputs and outputs for each step'), and OpenTelemetry-based tracing implies nested span semantics. However, the evidence pack never explicitly documents grouping into 'sessions' or 'threads' as a first-class concept, and one hands-on report claims tracing is limited to LLM inferences and works poorly with non-LangChain frameworks like CrewAI, undercutting universal multi-step nested tracing. missing for 10: explicit docs on session/thread grouping of traces, and stronger cross-framework corroboration of full nested-span coverage beyond LLM calls.

   • [claimed-docs] “Traces are the record of what your agents did in production. Use them to debug failures, monitor quality, and build the datasets you evaluat…”
   • [claimed-docs] “LangSmith supports OpenTelemetry-based tracing, allowing you to send traces from any OpenTelemetry-compatible application.”
   • [github] “client = wrap_openai(openai.Client())”
   • [community] “The power of langsmith is seeing full traces of moving through the graph and being able to inspect the inputs and outputs for each step... l…”
   • [community] “Langsmith only shows the llm inferences. Also it hardly works with other frameworks like crewai for instance.”

   proof ↗⚑ flag

   Braintrust~partialclaimed6/10

   Braintrust documents tracing that captures spans, logs, and full request detail, and lets users browse traces and individual spans via UI or CLI, supporting general span-based tracing. However, the evidence never explicitly describes nested multi-step spans grouped into sessions/threads for agent runs (no mention of parent-child span hierarchies or session/thread grouping semantics). Missing for 10: explicit documentation of nested span hierarchies for multi-step agent runs, explicit session/thread grouping constructs, and independent/hands-on confirmation of this specific structure.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Add tracing to your AI application to capture LLM calls, application logic, and user feedback — the foundation for observability and evaluat…”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with [`bt view logs`](/docs/reference/cli/view).”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”
   • [claimed-docs] “Integrate with AI providers and frameworks to send traces to Braintrust”

   proof ↗⚑ flag

2. developerInstrument my app through existing integrations for frameworks like LangChain, the OpenAI SDK, or the Vercel AI SDK

   weight 2 · round to LangSmith
   LangSmith~partialcommunity6/10

   LangSmith is built natively for LangChain and has an explicit OpenAI SDK wrapper (wrap_openai) plus OTel-based tracing and generic SDKs (Python/TS/Go/Java) for other stacks, but no evidence names a Vercel AI SDK integration specifically, and community feedback notes friction integrating non-LangChain frameworks (e.g. 'hardly works with other frameworks like crewai', 'no integration with the rest of your application'). missing for 10: explicit Vercel AI SDK integration documentation, broader evidence that non-LangChain framework instrumentation works smoothly.

   • [github] “client = wrap_openai(openai.Client())”
   • [claimed-docs] “LangSmith supports OpenTelemetry-based tracing, allowing you to send traces from any OpenTelemetry-compatible application.”
   • [claimed-docs] “Trace your preferred framework or integrate LangSmith with any agent stack using our Python, Typescript, Go, or Java SDKs.”
   • [community] “Langsmith only shows the llm inferences. Also it hardly works with other frameworks like crewai for instance.”
   • [community] “This is primarily based on the LangChain framework so it's fairly turnkey, but has no integration with the rest of your application... It's …”

   proof ↗⚑ flag

   Braintrust~partialcommunity4/10

   Docs confirm a general instrumentation capability and state you can 'integrate with AI providers and frameworks to send traces to Braintrust,' but no evidence explicitly names LangChain, the OpenAI SDK, or the Vercel AI SDK as supported integrations. A community comment even calls integration options 'limited.' Missing for 10: explicit documentation or hands-on confirmation of dedicated LangChain, OpenAI SDK, and Vercel AI SDK integrations.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Add tracing to your AI application to capture LLM calls, application logic, and user feedback — the foundation for observability and evaluat…”
   • [claimed-docs] “Integrate with AI providers and frameworks to send traces to Braintrust”
   • [community] “Braintrust: Interesting approach to evaluation but feels like an early-stage product. Documentation is sparse and integration options are li…”

   proof ↗⚑ flag

3. developerCapture multimodal payloads (images, audio, files) inside my traces

   weight 1 · round drawn
   LangSmith—none0/10

   No evidence in the pack mentions multimodal payload capture (images, audio, files) within traces; documentation covers general tracing, evaluation, dashboards, alerts, and SDK integrations but never addresses multimodal content in traces. Missing for 10: any mention of image/audio/file attachment support in trace payloads, UI rendering of multimodal content, or SDK helpers for multimodal logging.

   ⚑ flag

   Braintrust—none0/10

   The evidence pack describes tracing capturing inputs, outputs, model parameters, latency, token usage, and metadata, but there is no explicit mention of multimodal payload support (images, audio, files) within traces. Missing for 10: explicit documentation or examples showing image/audio/file capture in traces, SDK support for multimodal attachments, or any UI rendering of multimodal content in trace spans.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Add tracing to your AI application to capture LLM calls, application logic, and user feedback — the foundation for observability and evaluat…”

   proof ↗⚑ flag

4. developerSend and receive traces over OpenTelemetry (OTLP) instead of a proprietary format

   weight 3 · round to LangSmith
   LangSmith✓fullclaimed7/10

   LangSmith's docs explicitly state OpenTelemetry-based tracing support, letting any OTel-compatible app send traces to LangSmith instead of using a proprietary SDK format. However, evidence is limited to a single doc page with no independent/hands-on corroboration or detail on receiving/exporting via OTLP endpoints. Missing for 10: independent verification of OTLP ingestion working in practice, and documentation on OTLP export/interop beyond a single sentence.

   • [claimed-docs] “LangSmith supports OpenTelemetry-based tracing, allowing you to send traces from any OpenTelemetry-compatible application.”

   proof ↗⚑ flag

   Braintrust—none0/10

   No evidence pack item mentions OpenTelemetry or OTLP support; Braintrust's docs describe its own SDK/instrumentation and integrations but never reference OTLP-based trace ingestion/export. Missing for 10: any mention of OTLP endpoint, OpenTelemetry SDK compatibility, or OTel collector integration.

   ⚑ flag

5. developerCapture traces of my LLM calls with inputs, outputs, latency, and token usage

   weight 3 · round drawn
   LangSmith✓fullcommunity8/10

   Docs and SDK examples (wrap_openai) confirm capturing full traces with inputs/outputs, and dashboards explicitly track token usage, latency, and error rates; OpenTelemetry support extends this beyond native SDKs. Community feedback corroborates seeing full input/output traces per step, though one user notes it mainly captures LLM inferences and integration with non-LangChain frameworks (e.g., CrewAI) is weaker. missing for 10: independent benchmark of latency/token accuracy, broader non-LangChain framework validation.

   • [claimed-docs] “Traces are the record of what your agents did in production. Use them to debug failures, monitor quality, and build the datasets you evaluat…”
   • [claimed-docs] “Filter, export, share, and compare traces via the UI or API.”
   • [claimed-docs] “LangSmith supports OpenTelemetry-based tracing, allowing you to send traces from any OpenTelemetry-compatible application.”
   • [claimed-docs] “Prebuilt dashboards are created automatically for each project and cover essential metrics, such as trace count, error rates, token usage, a…”
   • [github] “client = wrap_openai(openai.Client())”
   • [community] “The power of langsmith is seeing full traces of moving through the graph and being able to inspect the inputs and outputs for each step... l…”
   • [community] “Langsmith only shows the llm inferences. Also it hardly works with other frameworks like crewai for instance.”

   proof ↗⚑ flag

   Braintrust✓fullclaimed8/10

   Braintrust docs explicitly state instrumentation captures inputs, outputs, model parameters, latency, token usage, and metadata for every LLM call, with SDK examples and CLI/UI browsing of traces and spans. missing for 10: independent hands-on verification of exact captured fields and no third-party benchmark of tracing accuracy/performance overhead.

   • [claimed-docs] “Instrumentation captures detailed traces from your AI application, recording inputs, outputs, model parameters, latency, token usage, and me…”
   • [claimed-docs] “Add tracing to your AI application to capture LLM calls, application logic, and user feedback — the foundation for observability and evaluat…”
   • [claimed-docs] “Integrate with AI providers and frameworks to send traces to Braintrust”
   • [claimed-docs] “Browse traces and individual spans, in the UI or from the terminal with `bt view logs`. ... Download logs as CSV or JSON, or pull them local…”
   • [github] “Eval("Say Hi Bot", { data: () => [ { input: "Foo", expected: "Hi Foo" }, ], task: (input) => "Hi " + input, scores: [Levenshtein…”

   proof ↗⚑ flag