BotGauge vs Respan API + MCP

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.

Respan API + MCP 73

Better Stack page at status.respan.ai with six components (web, logging and gateway, each for the platform and Enterprise) and an incident history page (20). The last 90 days show two incidents, both in late September. The Responses API path through the gateway was affected for OpenAI and Anthropic requests for 13 hours 47 minutes on 26 September, and request logs were delayed across all regions for 1 hour 58 minutes on 29 September. The uptime bars still read 100 per cent for every component (10, one major). Gateway and ingestion limits published per plan, 412 a minute on Free and 8,400 and 4,200 on Team (15). The OpenAPI spec declares 429 on several operations. We found no Retry-After or backoff guidance (10). The pricing page lists a 99.99 per cent uptime SLA on Enterprise, with terms not published (8). Gateway, logging and MCP are GA (10).

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.

Respan API + MCP 89

OpenAPI 3.1 at respan.ai/docs/openapi.json with 40 or more paths, and every MCP tool takes a zod schema (25). llms.txt, per-section llms.txt and .md for every page (10). MCP descriptions say when to use a tool and when not to. list_logs tells the model to filter server-side rather than fetch everything and to call get_log_detail for full data, and delete_dataset says it can't be undone (17). Typed inputs with operator enums, but page_size bounds sit in the description rather than the schema and filter values are any (11). Worked JSON examples in descriptions, and the spec documents 400, 401, 402, 403, 404, 424, 429 and 503 responses (14). Weekly dated changelog. API paths mix /api/ and /api/v1/ with no version policy (12).

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.

Respan API + MCP 30

No x402 or other machine payment (0). Overage prices published without login, $8 per 100,000 logs and $1 per 1,000 scores on Team (20). The Free plan has 100,000 logs and unlimited seats. The pricing page doesn't say whether a card is needed, so half (10). Keys can be minted by API, but only with an existing Admin key, so a person still signs up in a browser first (0).

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.

Respan API + MCP 85

Packages published from the Apache-2.0 monorepo on 2026-09-30 (30). 195 commits and well over three package publishes since 3 July, and 13 dated changelog entries since 7 July (20). The MCP repository last changed on 15 September. We didn't load issue reply times. Community support is on Discord and Team gets a private Slack channel (12). Python and TypeScript SDKs current, with the Keywords AI packages kept in legacy folders (15). CI and an OpenAI Python compatibility workflow run in public (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.

Respan API + MCP 66

The platform MCP server registers 67 tools in its source, about 24,000 characters of descriptions before schemas (5). The Respan-Enabled-Tools header trims the list server-side (8 back). list_logs pages 1 to 50 rows (default 20), returns summary fields unless include_fields asks for more, and defaults to the last hour (20). API errors pass through with status and body, and invalid filters return a typed validation_error naming the field (15). No readOnlyHint or destructiveHint on any tool, although delete_dataset, delete_evaluator, delete_experiment, delete_workflow and remove_dataset_logs are among them, and no idempotency keys found (3). Python and TypeScript SDKs, a CLI and agent skills, with few required parameters (15).

BotGauge 56

Project API keys reach one project, are shown once, stored in a form that can't be read back per the DPA, show their last-used time and revoke immediately, with documented rotation steps. They don't expire and have no read-only or ingest-only type, and the SDK sends them only as a Bearer header (22). Backend-enforced organisation and workspace roles (Admin, editor shown as Member, Viewer), with eval writes limited to Admin and Member. Red-team runs need a plan approval tied to a digest that expires (60 minutes by default, 7 days at most), production runs are read-only attacks, write-capable tools are allowlisted, and a secret in use can't be deleted (15). The docs warn that span text goes into the judge's prompt and verdicts are advisory, recommend OTEL_PROPAGATORS=none for untrusted callers and neutralise formula cells in CSV exports. No guidance for agents reading traces or transcripts back (8). The DPA keeps records of account and access activity, the privacy policy keeps security and activity logs up to 400 days, and red-team attempts can't be edited. No customer-facing audit log is documented (5). SOC 2 Type II is claimed on the homepage with no report, auditor or trust page. No security.txt, disclosure policy or bug bounty found. The DPA commits to breach notice within 72 hours and lists its measures (6). 22+15+8+5+6 = 56.

Respan API + MCP 66

API keys carry Read, Write, Gateway and Admin scopes since 25 September, can have an expiry and spend caps, are bound to one project and stop working at once when revoked. The MCP server also takes OAuth (30). A Read-only key plus the tool allowlist gives a read-only agent, but the write and delete tools have no confirmation step of their own (15). Logs hold whatever the application sent, and we found no prompt-injection guidance for agents reading them (3). Every gateway call is logged against its key. The compliance page mentions audit logging without saying what customers can see (8). SOC 2 Type II (report under NDA), HIPAA BAAs and GDPR per the compliance page, and a trust centre at trustcenter.respan.ai that we didn't load. No security.txt or SECURITY.md, and security fixes appear in the changelog as one-liners (10).