Braintrust API + MCP vs Overmind

Braintrust API + MCP 61

Statuspage at status.braintrust.dev with component history and 25 incidents since February 2026 (20). The last 90 days hold several majors. A critical run of 504s on the EU data plane on 16 July (about 30 minutes), gateway 5xx incidents on 3 August and 27 to 28 August, control plane 5xxs on 4 September, a 40-minute data-loading failure in the US on 9 September and 78 minutes of elevated errors across the US data plane API on 30 September. Most were short and the gateway is a side product, so 5 rather than 0. The only published limit is about 20 BTQL queries a minute on Starter and Pro. Ingestion and REST limits have no numbers (8). The OpenAPI spec documents 429 with a Retry-After header on 154 operations and recommends exponential backoff, the SDKs retry 408, 429 and 5xx, and events written with the same id overwrite rather than duplicate (15). Enterprise lists SLAs and guaranteed response times with no published terms (3). API and MCP are GA (10).

Overmind 23

No status page. status.overmindlab.ai doesn't resolve, /status returns 404 and neither the site nor the docs link one (0). With no history to read, 5. No request rate limits for the REST API, MCP or OTLP ingest were found in the docs. The only pacing settings, JEV_REQUESTS_PER_MINUTE and JEV_TOKENS_PER_SECOND, are self-hosting configuration for the scoring model (0). No 429 or Retry-After guidance, but the docs give safe-retry rules in detail. Launches, uploads, pipeline runs and inference take a stable request_key, identical retries return the existing receipt, changed payloads conflict, and run_evaluation is named as not idempotent (8). The terms promise commercially reasonable efforts toward 99.5 per cent availability a month, with remedies only in an order form or separate SLA, so half (5). The site doesn't call the service beta, but the SDK is classed "3 - Alpha" on its package metadata and the public repository is seven weeks old (5). 0+5+0+8+5+5 = 23.

Braintrust API + MCP 58

User API keys and service tokens as Bearer tokens. Service tokens attach to permission groups that can be scoped to single projects on any plan, keys can be deleted through /v1/api_key and /v1/service_token, and the MCP server also takes OAuth 2.0 with dynamic client registration (25). Viewer groups exist, but the MCP server gained write tools in August with no server-side read-only mode, and the docs leave confirmation to the client (12). Traces hold whatever the application logged, and we found no prompt-injection guidance for agents reading them (3). The October changelog mentions audit logging, and a knowledge-base page says org-wide API key auditing is in the UI only (8). SOC 2 Type II is claimed on the pricing page. The Vanta trust centre at trust.braintrust.dev rendered nothing readable to us, there's no security.txt and no SECURITY.md in either SDK repository, and the two credential-capture fixes below were explained in knowledge-base pages rather than advisories (10).

Overmind 70

API keys are account-scoped or pinned to one project, carry read, write or both, expire after 30 to 365 days or never, are shown once and show last use, and rotation is documented as replace then revoke. MCP also takes OAuth 2.1 from api.overmindlab.ai with PKCE S256, dynamic registration, a revocation endpoint, one-hour access tokens and rotating refresh tokens, with scopes overmind:read and overmind:write, the default being read. A key can only mint keys with the scope and permissions it holds, since 29 October 2026 (30). Read keys see only read tools over MCP, and the REST API refuses writes from a read-only key since the same commit (#263). Only two tools are destructive and lifecycle tools are allowlisted by name in the catalogue. The docs tell agents to confirm the GPU and rate with the user before starting a dedicated deployment, but there's no server-side approval step (15). The MCP prompts tell the agent to treat code, comments and data as untrusted content, and script output is labelled untrusted in resources. We found no guidance for agents reading trace inputs and outputs back (8). The Console's notification list shows what agents and the CLI did in a project, and overmind://activity returns it over MCP. No exportable audit log was found (10). SECURITY.md lists GitHub private vulnerability reporting and an email with acknowledgement within 3 business days. No security.txt on either host and no bug bounty. The terms claim an ISO 27001 certified management system and the site links a Vanta Trust Center, whose robots.txt disallows crawling, so neither was checked (7). 30+15+8+10+7 = 70.

Braintrust API + MCP 66

42 MCP tools load at once, with no toolsets or server-side allowlist found (5). REST lists take limit, starting_after and ending_before, and sql_query truncates field values to 1,024 characters by default and swaps results over 1 MB for a signed overflow_url (20). Error codes are declared per operation, the MCP server returns 413 above 100 MiB, and 429 carries Retry-After. Error bodies are typed as plain text (14). Event inserts upsert on id and ACL batch updates are documented as idempotent. Several MCP tools have a no-write test_* twin. We couldn't see whether the hosted tools carry readOnlyHint or destructiveHint (12). Few required parameters, and SDKs in TypeScript, Python, Go, Java, Ruby and C# (15).

Overmind 76

About 85 MCP tools in the source, all loaded for a read-write connection. A key or OAuth grant without write sees only the read tools (about 22), which is the only subset (5, plus 5 for the read-only filter). Cursor and offset pagination, limits by item count and response bytes, preview_rows bounded 1 to 1,000, query filters on traces by status, duration, tokens, cost and time, and evidence_resource links for paging retained results (20). MCP errors carry a structured code, message, retryability and field details, and authentication failures are kept apart from workflow failures. REST validation errors include details (18). Stable request_key on paid and long-running operations with conflict on a changed payload, and every tool sets readOnlyHint, destructiveHint, idempotentHint and openWorldHint from its catalogue entry. Only two tools are marked destructive (20). Account connections must pass project_id on every project tool. One official SDK, Python, plus OpenTelemetry from any language and the OpenAI client for inference (8). 10+20+18+20+8 = 76.

Braintrust API + MCP 40

No x402 or other machine payment (0). Usage prices published without login, $4 a GB and $2.50 per 1,000 scores on Starter, $3 and $1.50 on Pro (20). Starter is free with no card (20). A person signs up in a browser to create a key. The MCP OAuth flow also needs a browser sign-in (0).

Overmind 30

No x402 or other machine payment. Paid work spends prepaid credits, and 402 is documented only for insufficient credits (0). Plan prices, the credit rate ($0.01) and per-model "from" prices for training and serving are published without login (20). A Free plan with $50 of credits once exists, but neither the pricing page nor the docs say whether a card is needed, so half (10). A person signs up in a browser at console.overmindlab.ai. MCP OAuth with dynamic registration still needs a sign-in, and create_api_key needs an existing connection (0). Self-hosting under AGPL is free but runs on the operator's own Modal, OpenRouter, AWS and Hugging Face accounts, so it isn't scored as the hosted option. 0+20+10+0 = 30.

Braintrust API + MCP 85

TypeScript SDK braintrust 3.36.0 and Python SDK 0.44.0, both on 2026-10-01 (30). 15 TypeScript and 19 Python releases since 16 July (20). The product changelog lists dozens of September entries and both SDK repositories take outside contributions credited in the changelog. We didn't load issue reply times (12). Official SDKs in six languages, current (15). Public CI (checks.yaml), integration tests, Dependabot and a weekly dependency job. We didn't confirm the pass state (8).

Overmind 76

overmind 0.1.115 on PyPI on 2026-10-31, and the last commit on main the same day (30). 41 PyPI releases since 21 September 2026 and 24 git tags from v0.0.15 on 18 September to v0.1.23 on 30 October (20). github.com answered 403 to this session, so issues and pull request replies weren't read. 172 commits on main from eight people since 15 September, a Discord server and a support email (8). One official SDK, Python, current with the platform (10). Public CI workflows for the platform and SDK, Dependabot bumps merged on 28 October and a CI badge. We couldn't see the pass state (8). 30+20+8+10+8 = 76.