BotGauge vs Navige

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.

Navige 35

No machine payment protocol (0). The pricing page publishes Watchtower at $0 and paid use at the greater of $9 a month or 20 per cent of measured savings, without a login. The Terms still list exact prices, payment terms, taxes and refunds as TBD (15 of 20). Watchtower is free with no card and no time limit, per the pricing page and the Terms (20). A person signs up in a browser and confirms an email, and the Terms forbid creating accounts by automation (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.

Navige 51

No dated changelog. The latest release found is navige 3.0.0 on npm on 7 September 2026, 40 days before this check (20). navige 2.0.0 (26 July), 2.0.1 (12 August) and 3.0.0 (7 September) fall within 90 days, as do three releases of n8n-nodes-navige (20). A closed service with no public changelog. Support is hello@navige.ai, with a note on each docs page that a person reads reports. The SDK repository's issues weren't readable through the GitHub API from this session (3 of 15). Not in the official MCP registry under either name. The npm SDK covers intercept() and approval status only, with 15 methods that now throw, and the Python SDK couldn't be checked (5 of 15). The SDK has no dependencies, and its repository has no CI or tests (3 of 10).

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.

Navige 50

A closed service with MIT SDKs. The Terms (version 1.0, 13 October 2026) leave prices, liability, warranties, service levels, notice periods and governing law marked TBD (5 of 30). DPA 1.2 (14 October 2026) is specific and corrects version 1.1 in public, stating that no automatic deletion runs, that prompt text through the proxy is not stored and that production data is in the United States. The privacy policy (6 October 2026) contradicts it with per-plan retention of 7 days to 1 year on plans the DPA says no longer exist, and speaks of storing masked prompts (12 of 30). No deprecation policy. The SDK 3.0.0 README lists what was removed, and the DPA promises 30 days' notice of material changes and new deletion schedules, while the Terms leave notice periods TBD (4 of 20). DPA Schedule 2 names Railway (United States), Resend, Stripe and Framer (Netherlands), with transfer safeguards. Google, whose analytics tag the website loads, isn't listed, and locations aren't given for Resend or Stripe (14 of 20).

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.

Navige 42

No OpenAPI or other machine-readable contract. /openapi.json and /openapi return 404 and the docs link none. The MCP endpoint forwards tools from servers the customer registers and defines none of its own (0). No llms.txt on navige.ai or app.navige.ai and no Markdown versions of the docs (0). The docs say what each route does and does not do, for example that /usage gates nothing, that Watchtower changes no traffic and that error is not deny (15 of 20). /enforce and /usage have field tables with types, a required tool, a classification enum and 200-character bounds that reject rather than truncate. arguments is a free-form object (10 of 15). curl, Python and TypeScript examples on every route, the seven decision shapes, an HTTP status table, five degraded-decision cause codes and a troubleshooting table (14 of 15). No changelog, and /enforce, /usage and /mcp are unversioned paths beside /v1/transactions (3 of 15).

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.

Navige 28

Graded as a hosted service. A public Better Stack page at status.navige.ai exists, but its one monitor is api.trustloop.live/health, the host of the product's former name, and not api.navige.ai (5 of 20). That monitor shows downtime every day from 26 July to 17 October 2026 (7.221 per cent uptime) under a header saying all services are online, so there is no readable history for the current API (5). No rate-limit numbers in the docs, onboarding guide or terms (0). The docs separate a 503 outage from a 400 bug, state fail-open and fail-closed defaults per action class, return 429 for a blocking budget, pass provider errors through for the client's own retry logic, and make retries count once under x-navige-transaction. No Retry-After or backoff guidance (8 of 15). The Terms leave service levels as TBD (0). No beta or preview label on the gateway (10).

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.

Navige 61

The proxy returns the provider's response unmodified, decision responses are a few fields, and result capping, tool scoping and context trimming exist to shrink what reaches the agent's context, though all are off by default and paid only (15 of 25). The public API has no list endpoints, since logs and rules moved to the dashboard, and the output ceiling and result caps are the only size controls (8 of 20). Errors are distinct and recoverable, with four 401 reasons, 403 for an inactive or expired agent or the kill switch, 404 for an unknown provider, 429 for a budget and unavailable: true on outages (18 of 20). x-navige-transaction makes retried model calls count once and wait: false avoids a five-minute hold, but /enforce and /usage take no idempotency key. Navige adds no MCP tools of its own to annotate (10 of 20). One base URL and one header, with only tool required on /enforce. One official SDK, for Node.js, and the Python SDK named on the security page couldn't be checked (10 of 15).