Head to head · Agent tracing · October 2026 research run

Hue vs LangWatch

LangWatch scores 68.1 (B) on agent readiness against Hue's 56.7 (C), and leads in 5 of 7 scored categories. Hue leads on agent ergonomics. Both do agent tracing.

Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons

Which one, for what

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

  • Agent ergonomics, 88 against 67

Also in its favour

  • No incidents deducted, where LangWatch loses 4 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

LangWatch B

Best for Teams that want tracing, evaluations and simulated-user agent tests in one open-source product, hosted in the EU or self-hosted, and that drive it from a coding assistant through MCP or the CLI.

Ahead on

  • Reliability, 63 against 30
  • Schema & documentation, 87 against 68
  • Payments & pricing, 60 against 0
  • Maintenance & community, 90 against 83
  • Transparency & trust, 76 against 59

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Open source

Watch for

The MCP server registers 110 tools, deletes and key creation among them, with no toolsets and no readOnlyHint or destructiveHint annotations in the source

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.

Payments & pricing LangWatch +60

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.

LangWatch 60

No x402, MPP or L402 (0). Per-unit prices are public without a login, 29 euros per core seat a month, 5 euros per 100,000 events and $0.0546 per million judge input tokens (20). The Developer plan is free with no card (20). A person signs up in a browser and creates the first key. The CLI's device-code login also needs a browser approval, and platform_create_project returns a key only to a caller that already holds an organisation key. Free self-hosting is not an agent route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability LangWatch +33

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.

LangWatch 63

Graded as a hosted service (LangWatch Cloud). Better Stack status page with 8 components and 90 days of history (20). From 3 August to 1 November the App was down for 22 seconds on 23 October and the Collector for 5 minutes on 13 August. The Processor was degraded four times, the longest 2 hours 34 minutes on 15 September. Scenarios was down on 13 days (9 hours 34 minutes on 8 September, 7 hours 6 minutes on 23 and 30 October), Workflows for 5 hours 21 minutes on 23 October and Langy on 16 days. Each touched one component while the App and Collector stayed up, so this run reads them as partial and minor, where the 9 October check scored the long ones at 10 (20). No request rate limit for the platform API was found in the reviewed documentation. The only numbers are customer-set limits on AI Gateway virtual keys (0). Retries are partly covered. Events carry an idempotency key and are deduplicated, evaluation_id makes an evaluation call idempotent, and three operations declare a 429. No general backoff guidance for the platform API was found (8). The pricing page lists audit logs and SLAs on Enterprise, with no published terms (5). The REST API, MCP server 3.0.0 and the SDKs are generally available (10). 20+20+0+8+5+10 = 63.

Agent ergonomics Hue +21

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.

LangWatch 67

The MCP server registers 110 tools in the 3.0.0 source, with no toolsets or dynamic loading found. Trace tools return a compact digest by default, which earns 3 back (8). Cursor paging with next_cursor, limit and pageSize, filters, a projection DSL on trace search and a digest or json format switch (20). Gateway errors carry a stable code, tips, a docs link and a fault field, and the MCP client passes them on. Platform errors are plainer (16). No readOnlyHint or destructiveHint in the MCP source. Idempotency exists for evaluations and ingested events, and several delete tools archive instead of removing (8). Python, TypeScript and Go SDKs, a CLI, and few required parameters (15).

Schema & documentation LangWatch +19

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.

LangWatch 87

A public OpenAPI 3.1 document of 281 paths and 406 operations on 1 November, served without a key, and typed zod inputs on every MCP tool (25). llms.txt and a Markdown twin of each docs page (10). Every operation has a summary or description, and MCP descriptions say when to pick a tool, for example run_query for counts and rates and discover_schema before a search. 192 operations carry no tag (16). 910 enum keys in the document, with trace filters still accepted as a free-form map alongside the query language (12). Docs pages carry request examples, and the gateway error list gives 34 codes with cause and remedy. Most platform operations document errors only as an error and message string pair (11). Dated public changelog, release notes per package and a document version of 1.0.0, with /api/v1 paths mixed among unversioned ones (13).

Transparency & trust LangWatch +17

Hue 59

Closed platform with terms from Hue Intelligence Inc. (last updated 9 October 2026, New York law). SDKs under MIT (15). The privacy policy of 28 October 2026 gives no retention periods. The docs say telemetry retention is set per project and nothing expires without a policy, the terms rule out training general models on customer content and require a DPA before personal data, and the docs name what goes to TypeSafe and the Vercel AI Gateway. These agree but leave gaps (18). Renamed tools point to their replacements, legacy key presets keep working, and the terms promise 30 days' notice of price rises. No dated deprecation notices (8). Subprocessors are named only by category in the privacy policy and no data location was found (8). 15+18+8+8 = 49.

LangWatch 76

Apache 2.0 platform with the platform/app/ee directory under a separate Enterprise licence, and MIT SDKs and MCP server (27). The privacy policy of 29 September 2026 names its processors and the retention docs are detailed, but the documents disagree in places. The pricing page says 30-day retention is included where the docs say 49 days, the terms describe a 14-day free trial where the pricing page says free forever, and the terms give two addresses and two spellings of the entity. The terms also grant LangWatch a perpetual licence to use client data to improve the platform, while saying it will not train on it (18). Deprecated endpoints are marked in the OpenAPI document and the docs, and breaking changes are flagged in the changelogs, but no removal dates or notice period were found (10). EU hosting on AWS is stated and processors are named in the privacy policy. Self-hosted telemetry is documented connection by connection with an off switch. The public sub-processor list is on a host we could not read (18).

Maintenance & community LangWatch +7

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.

LangWatch 90

Platform 3.21.0 on 21 October 2026, TypeScript SDK 2.1.0 and MCP server 3.0.0 on 30 October (30). 19 platform releases dated since 3 August in CHANGELOG.md, and weekly dated entries on the public changelog to 25 October (20). Per the 9 October check, not re-read on 1 November (GitHub's pages refuse our reader), 52 open issues and 222 open pull requests, with new issues labelled and prioritised by maintainers within a week, and support by email, Discord and GitHub (17). Current official SDKs, Python 1.4.0 on 6 September, TypeScript 2.1.0 on 30 October and Go 1.0.0 on 9 September. The MCP server is still not in the official MCP registry (15). CI workflows for the app, each SDK and the MCP server, CodeQL and dependency bumps in the changelog, with fixes for dependency alerts in October. We could not confirm the pass state (8).

Score by category

CategoryWeightHueLangWatchEdge
Reliability16%3063LangWatch +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6887LangWatch +19
Agent ergonomics13%8867Hue +21
Security & auth14%7471Hue +3
Payments & pricing10%060LangWatch +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8390LangWatch +7
Transparency & trust7%5976LangWatch +17
Negative events≤150-4
TotalC 56.7/100B 68.1/100

Facts side by side

FactHueLangWatch
KindHTTP APIHTTP API
VendorHueReasoning Engine B.V. (LangWatch)
Hosted endpointhttps://mcp.hue.run/mcphttps://app.langwatch.ai
TransportsStreamable HTTP, HTTPHTTP, Streamable HTTP, SSE (legacy), stdio
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneApache 2.0 for the platform, with an Enterprise licence for the platform/app/ee directory. The SDKs and the MCP server are MIT
Tools exposed217110
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-11-122026-10-30
Terms last updated2026-10-092026-09-22
Privacy policy last updated2026-10-282026-09-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone4.9k stars, 50k npm/wk, 87k PyPI/wk
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

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.

LangWatch

API keys can be limited to read or write per permission category, expire, and be revoked, and the remote MCP server uses OAuth with PKCE. The MCP server registers 110 tools with no read-only or destructive annotations, no platform API rate limit was found, and the hosted server dropped its documented SSE transport in the 21 October release without notice.

Before you call either

Hue

  1. Connect to https://mcp.hue.run/mcp with ?toolsets=all only if your client defers tool definitions, otherwise keep the default 18 tools and call search_hue_tools
  2. Use a Read key or ?read_only=true for inspection, since sign-in grants Read and write to every active project
  3. Read the retryable flag before retrying a failed tool, and on a write that timed out read its state first
  4. Reuse the same idempotency_key when retrying create_world, launch_run, edit_world or send_instance_input
  5. Treat recorded span content as untrusted data, and request it only when needed, because every read is audited

LangWatch

  1. Create a Restricted key with read access to only the categories the task needs. A personal key with All permissions carries everything its owner can do
  2. Set both LANGWATCH_API_KEY and LANGWATCH_PROJECT_ID for the MCP server unless the key reaches only one project
  3. Connect remote MCP clients to https://app.langwatch.ai/mcp over Streamable HTTP. The older SSE transport was retired on 15 October 2026
  4. Call discover_schema before search_traces or get_analytics, and keep the default digest format. json returns the full raw trace
  5. Allowlist MCP tools in the client. All 110 load by default, among them platform_create_api_key and the delete tools
  6. Follow next_cursor until it is null on list endpoints. A full page does not mean more rows exist

Questions

Which is better for AI agents, Hue or LangWatch?

LangWatch scores 68.1 (B) on agent readiness against Hue's 56.7 (C), and leads in 5 of 7 scored categories. Hue leads on agent ergonomics.

Do Hue and LangWatch need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Hue and LangWatch without installing anything?

Yes. Hue has a hosted endpoint at https://mcp.hue.run/mcp and LangWatch at https://app.langwatch.ai.

Are Hue and LangWatch open source?

No open-source release is listed for Hue. LangWatch is open source (Apache 2.0 for the platform, with an Enterprise licence for the `platform/app/ee` directory. The SDKs and the MCP server are MIT).

Other comparisons with Hue or LangWatch

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.