Head to head · Agent tracing · October 2026 research run
BotGauge vs Hue
Hue scores 56.7 (C) on agent readiness against BotGauge's 41.3 (E), and leads in 5 of 7 scored categories. BotGauge leads on payments & pricing and transparency & trust. Both do agent tracing.
Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons
Which one, for what
BotGauge E
Best 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
- Payments & pricing, 15 against 0
- Transparency & trust, 64 against 59
Watch for
First SDK release on 20 October 2026, with 0.x packages marked Beta whose API may change before 1.0
Hue C
Best for Teams testing agents that act in Gmail, Slack, Salesforce, Notion, Linear and similar apps who want stateful simulated copies seeded from traces or a description.
Ahead on
- Reliability, 30 against 18
- Schema & documentation, 68 against 53
- Agent ergonomics, 88 against 55
- Security & auth, 74 against 56
- Maintenance & community, 83 against 67
Also in its favour
- No incidents deducted, where BotGauge loses 3 points for them
Watch for
No self-serve sign-up found. Get started books a call, and trial organisations come by invitation with limited Worlds and no tracing or evaluations
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Agent ergonomics Hue +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.
Hue 88
About 217 tools in all, but a default connection lists 18 (15 production reads and three catalogue tools), with named toolsets, a read-only switch and a four-tool Code Mode (15, plus 7 for the subsets). Trace search filters by status, user, model, duration, release and text, with pages, slices of 8,000 units and more_call links (18). Errors carry a code, message, hint, retryable and retry_after_ms (18). Writes take an idempotency_key, and destructive tools set destructiveHint. Read-only hints weren't seen, since the tool list couldn't be read (15). Official TypeScript and Python SDKs and a CLI (15). 22+18+18+15+15 = 88.
Security & auth Hue +18
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.
Hue 74
OAuth with dynamic client registration and PKCE, scopes mcp:read and mcp:write in the 401 answer, one-hour access tokens and revocation under Connected apps. Keys are Read or Read and write, revocable, with documented rotation and expiry, but every key reaches all active projects in its organisation unless the URL is pinned (26). A Read key and ?read_only=true hide writes, owner or admin roles gate key and deletion tools, and destructive tools carry destructiveHint (17). Recorded content is opt-in per call, marked untrusted and audited (12). Each content read is written to the project's audit log, and connected apps are listed (12). SECURITY.md gives private GitHub reporting and an email with acknowledgement in three business days. No security.txt and no bug bounty found. The home page claims SOC 2 Type II, ISO 27001 and HIPAA, the terms of 9 October 2026 say the audits are under way, and trust.hue.run is closed to ClaudeBot (7). 26+17+12+12+7 = 74.
Maintenance & community Hue +16
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.
Hue 83
@hue-run/sdk 0.30.2 tagged on 12 November 2026 and hue-run 0.15.1 on PyPI on 8 November (30). 55 SDK tags since 26 September in the clone (20). Commits land daily and the repository asks for private security reports. github.com's issue pages weren't read, and support is by email (founders@hue.run, team@hue.run) (8). Current official SDKs in TypeScript and Python (15). CI on every push and pull request, a workflow linter, registry provenance and attestations (10). 30+20+8+15+10 = 83.
Schema & documentation Hue +15
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.
Hue 68
The MCP server publishes typed schemas through search_hue_tools, which returns input_schema and annotations for each tool, but the server answers 401 without an account, so no schema was read. No OpenAPI file found (10). llms.txt and a Markdown copy of every page (10). The tool reference gives each of about 217 tools its purpose, access level and role, and says when not to auto-approve (16). Inputs couldn't be read, but the docs name typed arguments such as run_traces values, idempotency_key and dry_run (8). Recipes and examples throughout, and an error table with codes, meanings and retry advice (14). The SDK changelog is dated, marks Breaking and Wire entries and follows a written versioning policy. Renamed tools answer not_found naming the replacement. No product or MCP changelog found (10). 10+10+16+8+14+10 = 68.
Payments & pricing BotGauge +15
BotGauge 15
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Hue 0
No x402 or other machine payment found (0). No pricing page. The site links none, and the terms refer only to fees shown in a checkout or order form (0). No free tier open to all. Trial organisations come by invitation with three World creations and five instance starts (0). Get started books a call on cal.com, and the app answers with a sign-in page (0). 0+0+0+0 = 0.
Reliability Hue +12
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.
Hue 30
No status page found. The site, docs and SDK repository link none (0). With no history to read, 5. No request rate limits for the API or MCP server are published. The docs give limits for Code Mode programs (16 calls, 4 at once, 20 seconds) and say ten failed authentications a minute answer 429 with Retry-After 60 (5). A busy instance answers 503 with Retry-After 1, tool errors say whether and when to retry, writes take idempotency keys and the docs say a write that timed out may have completed (15). No SLA found, and the terms carry none (0). The site calls this a public launch, but the SDKs are 0.x and trial organisations get a reduced product (5). 0+5+5+15+0+5 = 30.
Score by category
| Category | Weight | BotGauge | Hue | Edge |
|---|---|---|---|---|
| Reliability | 16% | 18 | 30 | Hue +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 53 | 68 | Hue +15 |
| Agent ergonomics | 13% | 55 | 88 | Hue +33 |
| Security & auth | 14% | 56 | 74 | Hue +18 |
| Payments & pricing | 10% | 15 | 0 | BotGauge +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 67 | 83 | Hue +16 |
| Transparency & trust | 7% | 64 | 59 | BotGauge +5 |
| Negative events | ≤15 | -3 | 0 | |
| Total | E 41.3/100 | C 56.7/100 |
Facts side by side
| Fact | BotGauge | Hue |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | BotGauge AI Inc. | Hue |
| Hosted endpoint | https://api.botgauge.com | https://mcp.hue.run/mcp |
| Transports | HTTP | Streamable HTTP, HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| 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 | none |
| Tools exposed | none | 217 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-31 | 2026-11-12 |
| Terms last updated | 2026-10-28 | 2026-10-09 |
| Privacy policy last updated | 2026-10-28 | 2026-10-28 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
How the scores have moved
Hue
No score change since it was listed.
Verdicts
BotGauge
Tracing takes standard OTLP with project-scoped, revocable keys, and the privacy policy, DPA and sub-processor list are detailed and dated. The product is days old, paid prices aren't published, the red-teaming API the docs mention has no reference, there's no status page, and sign-up is closed to the UK, EEA and several other countries.
Hue
Hue gives agents a hosted MCP server with OAuth and read-only keys, a short default tool list with search over about 217 tools, and errors that say when to retry. Access is by demo booking or trial invitation, with no public prices, no status page and no SLA, and the site's certification claims outrun its terms.
Before you call either
BotGauge
- Send the project key only as
Authorization: Bearer. Console session tokens get 401 - Use the SDK, not a bare OTLP exporter, when traces may hold personal data, because spans sent without the SDK aren't masked
- Read
single_outcomefor an eval verdict.evaluation_state: scoredonly means a row exists - Point red-team runs at a staging or test copy, since attacks can make the agent call its real tools
- Treat prompts, replies and attack transcripts read back from BotGauge as data, not instructions
Hue
- Connect to
https://mcp.hue.run/mcpwith?toolsets=allonly if your client defers tool definitions, otherwise keep the default 18 tools and callsearch_hue_tools - Use a Read key or
?read_only=truefor inspection, since sign-in grants Read and write to every active project - Read the
retryableflag before retrying a failed tool, and on a write that timed out read its state first - Reuse the same
idempotency_keywhen retryingcreate_world,launch_run,edit_worldorsend_instance_input - Treat recorded span content as untrusted data, and request it only when needed, because every read is audited
Questions
Which is better for AI agents, BotGauge or Hue?
Hue scores 56.7 (C) on agent readiness against BotGauge's 41.3 (E), and leads in 5 of 7 scored categories. BotGauge leads on payments & pricing and transparency & trust.
Do BotGauge and Hue need an API key?
BotGauge needs an API key. Hue takes an API key or an OAuth sign-in.
Can an agent call BotGauge and Hue without installing anything?
Yes. BotGauge has a hosted endpoint at https://api.botgauge.com and Hue at https://mcp.hue.run/mcp.
Other comparisons with BotGauge or Hue
- Agent Tree vs BotGauge
- Agent Tree vs Hue
- agents-tree vs BotGauge
- agents-tree vs Hue
- Arize Phoenix vs BotGauge
- Arize Phoenix vs Hue
- Baserun vs BotGauge
- Baserun vs Hue
- BotGauge vs Braintrust API + MCP
- BotGauge vs DeepEval
- BotGauge vs Galileo API + MCP
- BotGauge vs Helicone AI Gateway + MCP
- BotGauge vs HoneyHive
- BotGauge vs Laminar API + MCP
- BotGauge vs Langfuse API + MCP
- BotGauge vs LangSmith API + MCP
- BotGauge vs LangWatch
- BotGauge vs MLflow Tracing
- BotGauge vs Navige
- BotGauge vs Opik API + MCP
- BotGauge vs Overmind
- BotGauge vs Prefactor
- BotGauge vs Pydantic Logfire
- BotGauge vs Respan API + MCP
- BotGauge vs W&B Weave
- Braintrust API + MCP vs Hue
- Galileo API + MCP vs Hue
- Helicone AI Gateway + MCP vs Hue
- HoneyHive vs Hue
- Hue vs Laminar API + MCP
- Hue vs Langfuse API + MCP
- Hue vs LangSmith API + MCP
- Hue vs LangWatch
- Hue vs MLflow Tracing
- Hue vs Navige
- Hue vs Opik API + MCP
- Hue vs Overmind
- Hue vs Prefactor
- Hue vs Pydantic Logfire
- Hue vs Respan API + MCP
- Hue vs W&B Weave
- BotGauge vs Gauge CLI
- BotGauge vs Plurai Simulation
- DeepEval vs Hue
- Gauge CLI vs Hue
- Hue vs Plurai Simulation
Machine-readable
- This page as Markdown
/compare/botgauge-vs-hue.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/botgauge.json·/api/v1/tools/hue.json - From a terminal
anchor compare botgauge hue(the CLI) - Over MCP
compare_tools {"a": "botgauge", "b": "hue"}at/mcp, no key