# BotGauge vs Prefactor (slim)

> Prefactor scores 66 (B) to BotGauge's 40.7 (E) for agent tracing. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/botgauge-vs-prefactor.md (~5,250 tokens) · this version ~3,080 tokens · JSON https://www.anchorterminal.com/compare/botgauge-vs-prefactor.json · canonical https://www.anchorterminal.com/compare/botgauge-vs-prefactor
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Prefactor scores 66 (B) on agent readiness against BotGauge's 40.7 (E), and leads in 5 of 7 scored categories. BotGauge leads on transparency & trust. Both do agent tracing.

- BotGauge: E 40.7, rank #1132 of 1260 · https://www.anchorterminal.com/tools/botgauge.min.md
- Prefactor: B 66, rank #319 of 1260 · https://www.anchorterminal.com/tools/prefactor.min.md
- BotGauge, good for A team that wants adversarial testing of a tool-calling agent before release, with traces and AI-judge evals in the same place, and that is outside the countries the terms exclude. Ahead on Transparency & trust, 64 against 47.
- Prefactor, good for A team that wants an auditable record of agent runs with declared data-risk labels, quality payloads from its own evaluations and a remote stop signal. Ahead on Reliability, 78 against 18; Schema & documentation, 80 against 53; Agent ergonomics, 88 against 55; Payments & pricing, 40 against 10; Maintenance & community, 82 against 67. Also Free to start without a card.

| Category | BotGauge | Prefactor |
| --- | --- | --- |
| Reliability (16%) | 18 | 78 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 53 | 80 |
| Agent ergonomics (13%) | 55 | 88 |
| Security & auth (14%) | 56 | 56 |
| Payments & pricing (10%) | 10 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 67 | 82 |
| Transparency & trust (7%) | 64 | 47 |

| Fact (where they differ) | BotGauge | Prefactor |
| --- | --- | --- |
| Vendor | BotGauge AI Inc. | Prefactor Pty Ltd |
| Hosted endpoint | `https://api.botgauge.com` | `https://app.prefactorai.com/api/v1` |
| Licence | Proprietary hosted service under BotGauge's terms (last updated 28 October 2026). The Python SDK on PyPI is source-available under FSL-1.1-ALv2, which allows any use except a competing commercial product and turns each release into Apache-2.0 two years after publication. Its repository isn't public | Proprietary hosted service. The TypeScript and Python SDKs and the CLI are MIT |
| Read-only variant documented | yes | no |
| Last release | 2026-10-31 | 2026-09-13 |
| Terms last updated | 2026-10-28 | no document linked |
| Privacy policy last updated | 2026-10-28 | couldn't be read |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 3 stars, 19 npm/wk, 28 PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Reliability, Prefactor +60: 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.); Prefactor 78 (Graded as a hosted service. A public status page at status.prefactor.ai (UptimeRobot) with three monitors and 90 days of daily bars, though we found no link to it from the site or docs (20). All three monitors, the API host among them, show 100 per cent for the 90 days to 8 October 2026 and no status updates. These are plain HTTP checks, not per-endpoint probes (30). Rate limits are described by scope and window with no numbers (3 of 15). 429 carries `Retry-After` and `retry_after_ms`, both SDKs retry with backoff and jitter, and every operation takes an idempotency key (15). The pricing page lists an SLA on Enterprise with no text published (0). The API is version 1.0 and `@prefactor/core` is 1.2.0, with no beta label (10).)
- Agent ergonomics, Prefactor +33: 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.); Prefactor 88 (List calls take `pagination[page_size]` up to 100, summaries and counts are opt-in flags, and one endpoint exports a whole run's context (16 of 25). Offset pagination, sorting and filters by agent, instance, environment, time, purpose and status, with no cursor (18 of 20). Errors carry a stable `code`, a message naming the exceeded scope on 429 and a per-field map on validation failures (20). Every operation accepts `idempotency_key`, and a retried bulk request fails only the reused items. There is no MCP server to annotate (20). Official TypeScript and Python SDKs and a CLI. The Python SDK does not yet support sensitive encoding (14 of 15).)
- Payments & pricing, Prefactor +30: 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.); Prefactor 40 (No machine payment protocol (0). Per-span overage prices and plan prices are published without a login, $0.0025 a span and $49 or $199 a month (20). The Dev plan is free with 5,000 spans a month and the page says no credit card is required (20). A person signs in through the browser to create the first token. `POST /api_token` mints more only with an existing token (0).)
- Schema & documentation, Prefactor +27: 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.); Prefactor 80 (A public OpenAPI 3.0.0 document with 157 operations and an OpenRPC document with 159 WebSocket methods. Body parameters are declared `in: body`, which OpenAPI 3 does not define, so some generators will need adjusting (23 of 25). llms.txt with abridged and full versions of the docs (10). Operations carry one-line summaries and only 4 of 157 have a description. The concept pages are clearer and say what the product does not do (10 of 20). Named ID schemas, enums and bounds such as `page_size` 1 to 100, but span payloads are free-form by design and `start_time` and `end_time` have no schema (11 of 15). A table of 12 error codes, an error union in the spec, curl examples and a runnable WebSocket script (13 of 15). The path is versioned `/api/v1`, the SDKs keep semver changelogs, and the site changelog has 35 dated entries, the latest on 27 July 2026 (13 of 15).)
- Transparency & trust, BotGauge +17: 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.); Prefactor 47 (A closed service with MIT SDKs. The only published terms cover the website, so the terms for the product are unclear (10 of 30). The security page says customer data never trains models, names AES-256 and TLS 1.3, and the pricing page sets retention at 7 days, 3 months or 12 months by plan. The privacy policy is a generated template whose regional sections place storage in the United Kingdom and in Canada, which does not agree with the AWS regions on the security page, and we found no DPA (12 of 30). No deprecation policy. The SDK changelogs mark breaking changes with major versions (4 of 20). Three AWS regions are named as residency options. No sub-processor list was found (8 of 20).)
- Maintenance & community, Prefactor +15: 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.); Prefactor 82 (`@prefactor/core` 1.2.0 was published on 13 September 2026, 25 days before this check (30). Four releases of it since 10 July (0.5.1, 1.0.0, 1.1.0, 1.2.0), plus five changelog entries in late July (20). A closed service with a public changelog whose latest entry is 27 July 2026, a Slack community and public SDK repositories with 4 open issues and pull requests on the TypeScript one. We did not read reply times (9 of 15 available to a closed service). Current official SDKs in two languages (15). CI passed on the TypeScript main branch on 13 September and weekly scheduled runs passed to 8 October. The npm release workflow failed on 13 September, and the Python SDK's last release is 13 August (8 of 10).)