BotGauge vs W&B Weave

BotGauge 18

No status page. status.botgauge.com doesn't resolve and neither the site nor the docs link one (0). With no history to read, 5. No request rate limits for ingest or the eval API. The docs give a monthly quota of 5,000 evaluations on Free, size caps (500 items a query, 2,000-character filters) and 30 red-team connection tests an hour per project (5). No 429 or Retry-After guidance. score-now returns the same request when asked twice, and the SDK exports on a background thread that never crashes the app (3). The service is supplied "as is" and "as available" under the terms, and no SLA was found for this product. The 99.9 per cent SLA on the /ai-agents page belongs to the QA service (0). The service isn't labelled beta, but the SDK is 0.x, marked "4 - Beta" on PyPI, and the docs say API shapes may change before 1.0 (5). 0+5+5+3+0+5 = 18.

W&B Weave 68

Graded as a hosted service on the Service API and OTLP endpoints at trace.wandb.ai. Statuspage site at status.forge.coreweave.com with ten components, a Weave backend component among them, and an incident history API (20). Since 10 July 2026 the history shows an API degradation on 1 September attributed to a Google Cloud incident, with no duration given, a 90 minute media error on 15 July, and metric ingestion and inference incidents outside Weave. None is on the Weave backend component, so minor only (20). No request rate limits for the multi-tenant Service API were found. The one limits page covers run logging on Dedicated Cloud (0). The SDK's retry schedule is documented, from 1 second doubling to 5 minutes with a 36 hour timeout, and the source retries 429 but no other 4xx. No Retry-After or idempotency guidance for direct API callers was found (8). SLA of 99.5 per cent monthly uptime for Enterprise Multi-tenant and Dedicated Cloud (10). Weave carries no preview label, though Agent Lens does (10).

BotGauge 10

No x402 or other machine payment (0). Paid plans for the agent product have no published prices, and botgauge.com/pricing prices the separate QA service (0). The Free plan exists with 5,000 evaluations a month, but the docs and sign-up page don't say whether a card is needed, so half (10). A person signs up in a browser at cloud.botgauge.com and creates keys in the console (0). 0+0+10+0 = 10.

W&B Weave 35

No x402 or other machine payment (0). Plan prices and the ingestion overage, $0.10 per MB on Pro, are published without a login (20). Free includes 1 GB of Weave ingestion a month. The pricing page doesn't say whether a card is needed and the signup page is drawn by script, so 15 of 20. A person signs up in a browser and creates the key in the console (0).

BotGauge 53

No OpenAPI file for the eval or red-team endpoints was found in the docs or llms-full.txt. Ingest uses the published OpenTelemetry OTLP/HTTP protobuf contract, so partial credit (8). llms.txt, llms-full.txt and Markdown for every page on Mintlify (10). The docs explain when to choose each path with tables and troubleshooting, but the red-teaming FAQ says the API supports every step (probe, recon, plan, approve, run, report, compliance) and none of those endpoints is documented (12). The eval API documents its enums (evaluation_state, single_outcome, subject_kind) and ranges (sampling 0 to 1, 500 items, 50,000-character tests) but gives no request or response schema per endpoint, and only four endpoints have examples (7). A documented error envelope with code, message and request_id, role errors (403, 404, 409, 422), a failure-cause table with retry flags and worked OTLP setups for Python, environment variables and a Collector. No list of error codes (11). /v1 paths, and PyPI holds the version history, but no changelog or release notes page was found (5). 8+10+12+7+11+5 = 53.

W&B Weave 74

A live OpenAPI 3.1 document at trace.wandb.ai/openapi.json with 114 paths, 127 operations and 334 schemas (25). llms.txt and a Markdown twin of every docs page (10). 76 of 127 operations carry a description, the document's title is the framework default, and when to use each endpoint is left to the guides (11). Request bodies are typed, with filter and sort objects, though query is a nested expression tree and several fields are marked beta and subject to change (11). The query guide has a curl example. The document lists only 200 and 422 responses (7). Dated SDK release notes per version. The API itself reports version 0.1.0 with a few /v2/ paths and no API changelog of its own (10).

BotGauge 67

botgauge, botgauge-tracing and botgauge-cli 0.1.3 on 2026-10-31 (30). Four releases of each since 20 October 2026, 0.1.0, 0.1.1, 0.1.2 and 0.1.3 (20). Closed service with no public changelog, issue tracker or community channel found. Support by email at support@botgauge.com (4). One official SDK, Python, current (10). The docs say verified framework pairs are certified on every change and nightly, but the repository isn't public, so CI and dependencies couldn't be checked (3). 30+20+4+10+3 = 67. The product is 12 days old by its first package release.

W&B Weave 87

Python SDK 0.53.11 released on 25 September 2026, 13 days before the check (30). Seven tagged releases between 31 July and 25 September (20). The repository's default branch had a commit on 8 October and 200 commits since 27 July. GitHub's API refused our reader, so issue reply times went unseen (14 of 25). Current Python and TypeScript SDKs, though the npm package is at 0.16.9 against 0.53.11 on PyPI (15). CI workflows for tests, nightly tests and Node tests, with lock files. 0.53.11 had to pin an OpenTelemetry exporter below 1.45 after weave.init() broke (8).

BotGauge 55

API responses can be narrowed by subject_ids and subject_kind, a results query takes up to 500 items, and judges read at most 20,000 characters, but no field selection or summaries are documented (12). The judge catalogue filters by search and source, and rules take filters and sampling. No pagination is documented on any list endpoint (10). Errors carry a code, a message and a request id. Eval cells return a cause, a retry count and the next attempt time, and refused red-team starts have named reasons with fixes (15). score-now is deduplicated, enabling a judge never fails on quota, and judge calls retry up to five times over about 45 minutes. No idempotency keys on other writes (8). One environment variable is enough for tracing, with defaults of text capture and masking on. Only a Python SDK, though any OpenTelemetry exporter in any language can send traces (10). 12+10+15+8+10 = 55.

W&B Weave 71

/calls/stream_query takes a columns list, and the MCP server's trace tool has schema, summary and full detail levels with a 30,000 token response budget (20 of 25). limit, offset, filter, query and sort_by on call queries, plus count and stats endpoints (18). Errors are documented as 422 validation bodies only. A release note of 24 September says illegal query arguments now return 400 and not 403 (8). The SDK retries and has a write-ahead log, and batch upserts exist, but no idempotency keys are documented and the MCP source has no readOnlyHint or destructiveHint annotations (10). Python and TypeScript SDKs, and tracing starts with weave.init and one decorator (15).

BotGauge 64

Closed platform under terms dated 28 October 2026 that name BotGauge AI Inc. The SDK is source-available under FSL-1.1-ALv2, not an OSI licence, with each release becoming Apache-2.0 after two years, and its repository isn't public (16). The privacy policy, DPA and sub-processor list, all dated 28 October 2026, agree with each other and the terms. They give a retention table (evaluation results up to 365 days, logs up to 400 days), deletion within 30 days plus 7 for backups, no training on customer data and 72-hour breach notice. Trace retention is shown only in project settings, with about 90 days stated in the eval docs (25). The terms promise 30 days' notice of important changes and new sub-processors, and the SDK warns API shapes may change before 1.0. No deprecation policy for the API (5). Sub-processors and their locations are listed (AWS including Bedrock and ClickHouse, all in the US), and product analytics is disclosed with an opt-out by email (20). 16+25+5+20 = 66.

W&B Weave 75

The SDKs and the trace server source are Apache-2.0 on GitHub. The hosted service is proprietary under the Master Service Agreement, and self-managed deployment goes through an account representative (24 of 30). MSA, DPA, privacy policy and sub-processor list are all public. The MSA lets W&B use Customer Data to improve its services, develop new products and run AI functions, no retention period for trace data was found, and the documents name three entities, Weights and Biases, LLC, CoreWeave, Inc. and the Forge brand (18 of 30). SDK release notes flag deprecated methods. No dated deprecation policy for the Service API, and no end date for Weave now that Agent Lens is named its successor (8 of 20). Nine sub-processors and one affiliate are listed with locations and 10 days' notice of changes (18 of 20).