{ "data": { "a": { "slug": "harnessrouter", "name": "HarnessRouter", "vendor": "HarnessRouter (Lumentree Corporation)", "vendorUrl": "https://harnessrouter.ai", "kind": "harness", "category": "agent-harnesses", "summary": "HarnessRouter runs complete agent harnesses such as Codex, Claude Code and Hermes behind one HTTP API, the Unified Harness Protocol, with sessions, streaming, files and artifacts. It comes as a hosted cloud or a self-hosted Community Edition.", "url": "https://www.anchorterminal.com/tools/harnessrouter", "markdownUrl": "https://www.anchorterminal.com/tools/harnessrouter.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/harnessrouter.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/harnessrouter.json", "dns": "harnessrouter.grade.anchorterminal.com", "repo": "https://github.com/HarnessRouter/harnessrouter", "license": "Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides.", "transports": [ "http" ], "remoteUrl": "https://api.harnessrouter.ai", "packages": [ { "registry": "oci", "name": "harnessrouter/harnessrouter" } ], "auth": "api-key", "authNotes": "A Workspace API key (sk-hr-) as a Bearer token from the product's server, never from a browser (https://harnessrouter.ai/docs/authentication). Keys are created in the console after a browser sign-up, can be held to one workspace or reach the whole organisation, and are revoked at once by DELETE /v1/orgs/{org}/keys/{id}. No OAuth or per-endpoint scopes found. The self-hosted Community Edition signs into its console with a username and password and needs no HarnessRouter key.", "pricing": "usage", "pricingNotes": "Free plan at $0 with no card, for the console and configuring agents, with 2 tasks at a time during its 7-day trial. Running tasks draws on top-up credit ($10 minimum, 5.5 per cent fee, minimum $0.80) or a plan, Developer $20, Production $200 or Scale $1,000 a month, each fully included as usage. Agent work is $0.020 an active minute on top-ups and $0.014 to $0.006 on plans, and model calls are at the provider's price or on your own keys (https://harnessrouter.ai/pricing.md, checked 2026-11-04). Self-serve payment is card-only.", "priceSummary": "$20 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, llms-full.txt, the pricing page or the UHP schema (checked 2026-10-17). Payment is by card for top-ups and plans.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 4069, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-04" }, "docsUrl": "https://harnessrouter.ai/docs", "llmsTxt": "https://harnessrouter.ai/llms.txt", "openapi": "https://github.com/HarnessRouter/harnessrouter/blob/main/protocol/schema/uhp-2026-10-04.openapi.yaml", "capabilities": [ "agent.harness", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "hosted", "self-hosted", "open-source", "apache-2.0", "api-key", "usage", "openapi", "llms-txt", "docker", "python", "streaming", "cloud-agent", "agent-skill" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 47.7, "grade": "D", "agentReady": false, "rank": 1144, "ranked": true, "rankOf": 1510, "categoryRank": 46, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 72, "payments": 25, "reliability": 35, "schema": 83, "security": 60, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -11, "negativeNotes": [ "2026-10-06, -5. Privately reported flaws fixed in public commits #416 to #429 on 6 and 7 October 2026. The gateway source names them GHSA-p6cq-54cg-8mpv (a bearer token that failed verification still reached internal routes, so anyone could rewrite any organisation's connections and routing; \"found live on the hosted service and closed there the same way, 2026-10-06\"), GHSA-qrr8-m92f-7vfp (identity headers trusted by default), GHSA-mw9j-m5jf-5r56 and GHSA-c5g7-c47h-f6c3 (server-side request forgery through git imports and upload addresses) and GHSA-rmh9-whjx-gfrc (secrets with quotes or non-ASCII characters left unredacted). A workspace key could also read, change and delete another workspace's harnesses, sessions and responses and mint an organisation-wide key (\"reported privately three times\"). All were fixed within days and described in the source. The advisory pages couldn't be read (GitHub answered 403), so whether they're published is unchecked, and the deduction is lower than an open cross-tenant flaw would get. Source https://github.com/HarnessRouter/harnessrouter/blob/main/gateway/app.py", "2026-10-10, -3. Since 10 October 2026 harness writes carrying a field the harness doesn't have, or a `default_model` its base doesn't run, are refused with 422 (`model_not_available` for the model), where they were accepted with 200 before. UHP's own versioning rules reserve such a tightening for a new version. The first notice was the known-compromises entry added to the versioning page in the same commit on 10 October, the day the hosted service made the change, and the changelog followed on 19 October (same-day term; it applies to the hosted service, so the 0.x reading doesn't reach it). Source https://github.com/HarnessRouter/harnessrouter/blob/main/protocol/VERSIONING.md", "2026-11-03, -3. Release v0.37.16 (3 November) fixes a flaw its commit describes with no advisory identifier. A relay route kept a connection's key usable after its turn ended, even after the operator removed the connection (\"200 on the turn's route after the turn had ended\"). The v0.37.15 fixes of 2 November (credentials and instance secrets readable by agent turns, the published default console password accepted) cite GHSA-m479 and GHSA-r37g in the source, and other v0.37.16 and v0.37.17 fixes cite GHSA-3vf8, GHSA-fx92, GHSA-gf7m-w8pf-6f68, GHSA-mm72-wr37-26pv and GHSA-mx6c-8c42-fw44, so they aren't counted here. None of those advisories could be read (GitHub answered 403). Source https://github.com/HarnessRouter/harnessrouter/commit/430358a" ], "verdict": "A product's server sends a task to a named harness and gets streamed progress, sessions and files back, under a published OpenAPI contract with idempotency keys and a closed set of error codes. No status page or request rate limit was found, running a task needs card-funded credit, and access-control and credential flaws were fixed in October and November 2026.", "bestFor": "A product team that wants to run Codex, Claude Code, Hermes or 27 other harnesses server-side behind one task, session and file contract, and switch between them by changing an ID.", "strengths": [ "UHP is published as OpenAPI 3.1 and JSON Schema 2020-12 under Apache-2.0, with a 101-check conformance suite in the repository", "Every task call takes an Idempotency-Key, and the error envelope has a closed code set, with a retry rule per code", "Per-turn budgets (400 steps, 7,200 seconds and $10 by default) cap what one task can spend", "30 harnesses listed as available, including Codex, Claude Code, Hermes, OpenCode, goose and Qoder, behind one task contract", "245 tagged releases between 15 August and 3 November 2026, and the self-hosted Community Edition runs with no HarnessRouter account" ], "weaknesses": [ "No status page found (status.harnessrouter.ai has no DNS record), and the terms give no service level without a signed Order Form", "No request rate limit is published. Only concurrency (2 tasks at a time in the Free trial) and task length (30 minutes, or 1 hour after a top-up) are stated", "Running a task on the hosted service draws on credit, and top-ups and plans are card-only, so an agent can't start without a person", "Access-control, SSRF and redaction flaws were fixed on 6 and 7 October 2026, and credential exposure to agent turns on 2 and 3 November, with no advisory readable", "Harness writes with unknown fields began failing with 422 on 10 October 2026, announced only that day in the versioning page and on 19 October in the changelog" ], "agentNotes": [ "Name the harness yourself. The task call is POST /{harness_id}/v1/responses, and HarnessRouter doesn't choose a harness for you", "Send a fresh Idempotency-Key with each new task, reuse it only for a retry of the same request, and recover from the session if a stream drops", "Call cancel to stop work. Closing the SSE connection leaves the agent running and billing", "Keep the Workspace API key on the server. The docs forbid calling the API from a browser with it", "Check each tool's enforcement in GET /v1/bases. On bases marked instruction, disabled_tools is a request to the model, not a block" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.7 } ], "editorialScores": { "ergonomics": 73, "maintenance": 72, "payments": 25, "reliability": 35, "schema": 83, "security": 60, "transparency": 79 }, "provenanceScore": 67, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "docker run -d --name harnessrouter -p 127.0.0.1:3000:3000 -v harnessrouter:/data harnessrouter/harnessrouter", "http": "curl -N https://api.harnessrouter.ai/$HARNESS_ID/v1/responses -H \"Authorization: Bearer $HR_API_KEY\" -H \"Idempotency-Key: $(uuidgen)\" -H \"Content-Type: application/json\" -d '{\"input\": \"Review this uploaded agreement and return a checklist.\", \"stream\": true}'" }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/harnessrouter" }, "area": "frameworks", "unitPrices": [ { "item": "Developer plan, all $20 as usage", "unit": "month", "usd": 20, "note": "agent work $0.014 an active minute, one workspace" }, { "item": "Production plan, all $200 as usage", "unit": "month", "usd": 200, "note": "agent work $0.010 an active minute, five workspaces" }, { "item": "Scale plan, all $1,000 as usage", "unit": "month", "usd": 1000, "note": "agent work $0.006 an active minute, tracing included" }, { "item": "Agent work on top-up credit, per hour of active work", "unit": "session-hour", "usd": 1.2, "note": "$0.020 an active minute, billed by the second. Waiting on the model, the user or a queue isn't billed" }, { "item": "Tracing add-on", "unit": "month", "usd": 50, "note": "beta, included with Scale" } ], "provenance": { "legalEntity": "Lumentree Corporation", "domain": "harnessrouter.ai", "domainRegistered": "2026-06-18", "endpointOnVendorDomain": true, "terms": "https://harnessrouter.ai/legal/terms", "privacy": "https://harnessrouter.ai/legal/privacy", "statusPage": "", "changelog": "https://unifiedharnessprotocol.org/changelog", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The terms (v1.1, 31 July 2026) name Lumentree Corporation, a California corporation, as the contracting party, and the disclosure policy names the same company. The YC launch lists the company as Epsilla (Summer 2023), per the 17 October check.", "harnessrouter.ai was registered on 18 June 2026 and unifiedharnessprotocol.org on 12 August 2026, from the registry RDAP readings of 17 October 2026 (not re-read; RDAP is a JSON service).", "No status page. status.harnessrouter.ai has no DNS record (4 November 2026) and no other status page was found.", "harnessrouter.ai/.well-known/security.txt answered 404 on 17 October 2026 (not re-read). A disclosure policy is at /legal/security, and SECURITY.md in the repository names GitHub private reporting and contact@harnessrouter.ai.", "The changelog is the UHP specification's (protocol/CHANGELOG.md in the repository). HarnessRouter itself has 245 tags in the repository and no product changelog page was found.", "The terms (§4.4(c)) forbid scraping or crawling except as allowed by the documentation, an API endpoint, robots.txt or written permission. robots.txt on harnessrouter.ai names ClaudeBot, Claude-User and Claude-SearchBot and allows all paths, and unifiedharnessprotocol.org allows all paths (4 November 2026)." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/harnessrouter.json", "live": { "slug": "harnessrouter", "probe": { "target": "https://api.harnessrouter.ai", "method": "get", "lastAt": "2026-11-07T19:22:10.914710049Z", "lastOk": true, "lastStatus": 404, "lastMs": 345, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 289, "p95ms24h": 384, "samples24h": 238, "samples30d": 5155, "days": [ { "date": "2026-10-17", "probes": 21, "ok": 21 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "github", "name": "HarnessRouter/harnessrouter", "version": "v0.38.2", "released": "2026-11-04", "seenAt": "2026-11-06T23:32:20.439259022Z" } ], "githubStars": 4262, "securityTxt": { "url": "https://harnessrouter.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:32.980927731Z" }, "llmsTxt": { "url": "https://harnessrouter.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:40.598398049Z" }, "domain": { "domain": "harnessrouter.ai", "registered": "2026-06-18", "source": "https://rdap.identitydigital.services/rdap/domain/harnessrouter.ai", "checkedAt": "2026-11-01T14:17:32.25734582Z" }, "pages": [ { "url": "https://unifiedharnessprotocol.org/changelog", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:22:52.813950452Z", "changedAt": "2026-11-04T08:35:29.196603298Z", "fingerprint": "df248ace8f95" }, { "url": "https://harnessrouter.ai/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:10:52.413474371Z", "changedAt": "2026-10-18T23:31:33.798956939Z", "fingerprint": "b31b753df12b" }, { "url": "https://harnessrouter.ai/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:10:48.041658297Z", "changedAt": "2026-11-03T07:51:05.619736871Z", "fingerprint": "3de312eb4d16" }, { "url": "https://harnessrouter.ai/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:10:50.353093961Z", "changedAt": "2026-11-03T07:51:07.897150705Z", "fingerprint": "d25dce7ee92b" } ], "github": { "repo": "harnessrouter/harnessrouter", "checkedAt": "2026-11-02T08:53:53.843359717Z", "stars": 3860, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T02:10:02Z", "openIssues": 16, "openPRs": 5, "issuesOpened90d": 85, "issuesClosed90d": 69, "prsMerged90d": 479, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-01T10:11:08Z" }, "advisories": [ { "ghsa": "GHSA-59mq-hx4p-fw48", "severity": "medium", "published": "2026-10-08T04:42:01Z" }, { "ghsa": "GHSA-c5g7-c47h-f6c3", "severity": "medium", "published": "2026-10-08T01:58:14Z" }, { "ghsa": "GHSA-qrr8-m92f-7vfp", "severity": "high", "published": "2026-10-07T19:55:26Z" }, { "ghsa": "GHSA-mw9j-m5jf-5r56", "severity": "high", "published": "2026-10-07T19:24:34Z" }, { "ghsa": "GHSA-7pwj-vv9r-rh2m", "severity": "medium", "published": "2026-10-07T07:13:59Z" }, { "ghsa": "GHSA-rmh9-whjx-gfrc", "severity": "medium", "published": "2026-10-07T07:13:58Z" }, { "ghsa": "GHSA-4386-3vpq-3xhx", "severity": "high", "published": "2026-10-06T21:59:22Z" }, { "ghsa": "GHSA-p6cq-54cg-8mpv", "severity": "critical", "published": "2026-10-06T21:59:21Z" }, { "ghsa": "GHSA-cgf4-38c9-39vr", "severity": "high", "published": "2026-10-06T21:32:58Z" }, { "ghsa": "GHSA-9pjr-97x3-c4wv", "severity": "high", "published": "2026-10-06T21:32:57Z" }, { "ghsa": "GHSA-5hfm-crcm-5vh7", "severity": "high", "published": "2026-10-06T20:00:17Z" } ], "replies": { "sampled": 25, "unanswered": 6, "medianDays": 0.9 } }, "updatedAt": "2026-11-07T19:22:10.914710049Z" } }, "answer": "HarnessRouter scores 47.7 (D) on agent readiness against Verdent's 39.7 (E), and leads in 6 of 7 scored categories. Verdent leads on reliability.", "b": { "slug": "verdent", "name": "Verdent", "vendor": "Verdent AI, Inc.", "vendorUrl": "https://www.verdent.ai", "kind": "harness", "category": "agent-harnesses", "summary": "Verdent is a coding agent from Verdent AI, Inc., with a desktop app for macOS and Windows, VS Code and JetBrains extensions and a browser edition. It plans tasks, runs parallel workers in git worktrees and uses MCP servers.", "url": "https://www.anchorterminal.com/tools/verdent", "markdownUrl": "https://www.anchorterminal.com/tools/verdent.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/verdent.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/verdent.json", "dns": "verdent.grade.anchorterminal.com", "license": "Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published", "transports": [], "packages": [], "auth": "mixed", "authNotes": "A person signs in to a Verdent account with Google, GitHub or email in a browser. Model use runs on Verdent credits through llm-proxy.verdent.ai, or on the user's own Anthropic, OpenAI or OpenRouter key (BYOK). BYOA runs workers on a local Claude Code or Codex CLI with keys kept on the machine. No API key or token for driving Verdent from another program was found.", "pricing": "paid", "pricingNotes": "From $5 a month (Lite), then $19 Starter, $59 Pro and $179 Max with 320, 1,000 and 3,000 credits a month (doubled by a limited-time bonus). One credit is about $0.059 at provider rates. Top-ups $20 for 340 credits to $200 for 3,400. Free Mode and the free trial ended with v2.18.0 on 29 October 2026.", "priceSummary": "$5 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, pricing page, terms or changelog (checked 2026-11-06). Subscriptions and top-ups go through Stripe.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://www.verdent.ai/docs/verdent-manager/getting-started/overview", "capabilities": [ "agent.harness", "agent.multi-agent", "agent.mcp-client" ], "tags": [ "official", "harness", "coding-agent", "closed-source", "desktop", "vscode", "jetbrains", "mcp", "byok", "paid-plans", "no-sandbox" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 39.7, "grade": "E", "agentReady": false, "rank": 1336, "ranked": true, "rankOf": 1510, "categoryRank": 53, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 35, "maintenance": 61, "payments": 20, "reliability": 43, "schema": 55, "security": 33, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": -2, "negativeNotes": [ "2026-11-06. The changelog says v2.18.0 of 29 October 2026 retired Free Mode, the free trial and the 100 welcome credits, while the pricing page FAQ read on 6 November still says \"Your free trial includes 100 credits\" and the 1.0 docs overview still lists a free trial. A stale claim on the vendor's own pricing page, 2 points. https://www.verdent.ai/pricing, https://www.verdent.ai/changelog" ], "verdict": "A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026.", "bestFor": "A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.", "strengths": [ "Plan Mode is read-only and writes a plan.md for review before Agent Mode makes changes", "Parallel workers each run in their own git worktree, with a review column before work is accepted", "BYOA runs workers on a local Claude Code or Codex CLI, and BYOK takes Anthropic, OpenAI or OpenRouter keys", "Plan, top-up and per-credit prices are public, charged at provider token rates with no markup per the pricing page", "Every current docs page has a Markdown twin, and the changelog is dated by version" ], "weaknesses": [ "No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot", "No sandbox or network restriction documented, and the actions that need approval aren't listed", "Free Mode and the free trial ended on 29 October 2026, while the pricing page FAQ still promises 100 trial credits", "Event logging to log.verdent.ai has no documented opt-out, and the privacy policy gives no retention periods", "SOC 2 and ISO/IEC 42001 are being pursued, not held, and there is no bug bounty or security.txt" ], "agentNotes": [ "Don't plan to drive Verdent headless. Hand the task to the person using the desktop app, or use a harness with a print mode", "Start large changes in Plan Mode and review plan.md before switching to Agent Mode", "Add MCP servers in the project's .mcp.json or ~/.verdent/mcp.json in the mcpServers shape", "Keep work under git, since rollback relies on git and there is no sandbox", "Budget in credits at about $0.059 each, because there is no free allowance since 29 October 2026" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 39.7 } ], "editorialScores": { "ergonomics": 35, "maintenance": 61, "payments": 20, "reliability": 43, "schema": 55, "security": 33, "transparency": 47 }, "provenanceScore": 62, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "config": { "mcpServers": { "github": { "args": [ "-y", "@modelcontextprotocol/server-github" ], "command": "npx", "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}" } } } } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/verdent" }, "area": "frameworks", "unitPrices": [ { "item": "Lite plan", "unit": "month", "usd": 5, "note": "Eco Mode models and light usage" }, { "item": "Starter plan", "unit": "month", "usd": 19, "note": "320 credits a month, 480 with the limited-time bonus" }, { "item": "Pro plan", "unit": "month", "usd": 59, "note": "1,000 credits a month, 1,500 with the bonus" }, { "item": "Max plan", "unit": "month", "usd": 179, "note": "3,000 credits a month, 4,500 with the bonus" }, { "item": "Credit", "unit": "credit", "usd": 0.059, "note": "About $0.059, charged at provider token prices with no markup per the pricing page" } ], "provenance": { "legalEntity": "Verdent AI, Inc.", "domain": "verdent.ai", "domainRegistered": "2025-05-06", "endpointOnVendorDomain": true, "terms": "https://www.verdent.ai/terms", "privacy": "https://www.verdent.ai/privacy", "statusPage": "", "changelog": "https://www.verdent.ai/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The privacy policy names Verdent AI, Inc. as data controller, and the terms choose California law.", "The terms forbid users to crawl, scrape or otherwise harvest data or information from the Services. Public pages were read once each.", "www.verdent.ai/robots.txt allows all crawlers.", "RDAP gives verdent.ai a registration date of 6 May 2025.", "/.well-known/security.txt returns 404, and status.verdent.ai did not answer. No status page found.", "The security page says SOC 2 and ISO/IEC 42001 are being pursued, not held, and takes vulnerability reports at hi@verdent.ai with acknowledgement within five business days." ], "score": 62 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/verdent.json", "live": { "slug": "verdent", "securityTxt": { "url": "https://verdent.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:33.272105482Z" }, "pages": [ { "url": "https://www.verdent.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:36:28.662063151Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bac05e4e426e" }, { "url": "https://www.verdent.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:36:31.354667853Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3ec1d3c07d70" }, { "url": "https://www.verdent.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:36:33.295376926Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "206b6ec23a6a" } ], "updatedAt": "2026-11-07T15:59:33.272105482Z" } }, "edges": [ { "by": 38, "category": "ergonomics", "leads": "harnessrouter", "name": "Agent ergonomics", "reasons": { "a": "API reading. Sessions, turns and files are separate reads, and list endpoints take limit and cursor, but there's no field selection on a response (15 of 25). Cursor paging on session and memory lists with a bounded limit, and few filters found (14 of 20). One error envelope with type, code, param and detail, a closed code set, a retry rule per code and a 422 that lists every failed field without echoing the body (18 of 20). Idempotency-Key on task creation, reuse only for the same request, recover from the session after a drop, and an explicit cancel because closing the stream doesn't stop work (18 of 20). Only input is required to run a task, and budgets default to 400 steps, 7,200 seconds and $10. No official SDK, only the OpenAI Responses shape, clients generated from the OpenAPI file and an Agent Skill (8 of 15). 73 in all.", "b": "Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35." }, "scores": { "a": 73, "b": 35 } }, { "by": 28, "category": "schema", "leads": "harnessrouter", "name": "Schema \u0026 documentation", "reasons": { "a": "API reading. UHP's OpenAPI 3.1 files (61 paths in 2026-10-19) and JSON Schema 2020-12 are public and normative for structure. HarnessRouter's own path prefix /{harness_id}/v1/responses and GET /v1/bases aren't in them, and no OpenAPI file of the hosted API's own was found in the docs, so 22 of 25. llms.txt, llms-full.txt, agents.md, docs.md, pricing.md and harnesses.md (10). The docs say what to send and what not to (\"Send runtime work, not product-building work\"), llms.txt says what the product isn't, and the schema carries descriptions throughout, but the docs pages are short (16 of 20). Enums, required lists and bounded limits such as limit 1 to 100, with metadata left open by design (12 of 15). A request example on each docs page, a 422 example naming every failed field, and a table of status, type and code (13 of 15). Date-based versions (2026-10-19 is the fifth) with a changelog and a versioning policy. Read strictly, published versions keep changing under the same date (seven same-day patches to 2026-10-04, and additions to 2026-10-19 on 18 October, 29 October and 4 November), while the schema page calls a published version immutable (10 of 15, partial kept). The conformance page and the suite's README now agree on 101 checks. 22 + 10 + 16 + 12 + 13 + 10 = 83.", "b": "Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as \"certain tool executions\" and \"destructive operations\" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55." }, "scores": { "a": 83, "b": 55 } }, { "by": 27, "category": "security", "leads": "harnessrouter", "name": "Security \u0026 auth", "reasons": { "a": "Hosted reading. Bearer Workspace API keys, revocable at once through the API, held to one workspace or reaching the organisation, with harness-bound calibration credentials. No OAuth, per-endpoint scopes or expiry found (20 of 30). Least privilege 10 of 20. disabled_tools per configured agent, enforced by the runtime only where GET /v1/bases says hard, and per-turn cost and step caps, with no approval step for actions a harness takes. Prompt injection 10 of 15. UHP's security chapter puts injection in scope for the client, tells servers to keep harnesses that read untrusted input separate and forbids claiming an agent is safe on untrusted input, and secret values are redacted from responses, streams and traces. Operator visibility 10 of 15. A cost breakdown per task on every plan, and the step-by-step trace is beta, included in Scale or $50 a month. Security programme 10 of 20 (was 8). A disclosure policy (v1.0, effective 30 July 2026) with safe harbour and no bounty, SECURITY.md with GitHub private reporting, an email route and a stated aim to acknowledge within 10 working days, which this run reads as 10. GHSA identifiers are cited in public fix commits; no security.txt and no SOC 2 or ISO 27001 found. 20 + 10 + 10 + 10 + 10 = 60.", "b": "Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33." }, "scores": { "a": 60, "b": 33 } }, { "by": 18, "category": "transparency", "leads": "harnessrouter", "name": "Transparency \u0026 trust", "reasons": { "a": "Editorial half. The server, specification, schema and conformance suite are Apache-2.0. The Cloud's own billing and deployment wasn't confirmed to match the open code, and the Agent Skill has a custom licence for some guides (25 of 30). The privacy policy, DPA, subprocessor list and a retention page agree. Customer content isn't used for training without an opt-in, and periods are stated (tasks deleted at once, agents and files after 30 days, backups within 14 days, credentials within 90, free-plan task records 7 days). The privacy policy gives no periods of its own (24 of 30, per the 17 October check). Deprecation 15 of 20 (was 14). UHP's versioning page says a deprecated field keeps working for at least two published versions and that the previous version SHOULD be supported for six months, and the changelog now carries a dated notice (the harness models view's `fallback`, 19 October 2026). The rule is counted in versions, not time, so dated notices give 15. Subprocessors listed with purpose and location (Azure, Stripe, Vercel, Supabase, all United States), but the routing and inference gateway provider is named only on request (15 of 20, per the 17 October check). 25 + 24 + 15 + 15 = 79. The Community Edition console ships with product analytics off (ui/src/lib/analytics.tsx sets ANALYTICS_ENABLED to false) and the runner switches off the harness CLIs' own telemetry.", "b": "Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47." }, "scores": { "a": 73, "b": 55 } }, { "by": 11, "category": "maintenance", "leads": "harnessrouter", "name": "Maintenance \u0026 community", "reasons": { "a": "Open-source reading of the repository behind the hosted service. Last tag v0.38.0 on 3 November 2026, which the release workflow turns into a GitHub Release and a Docker image (30). 245 tags between 15 August and 3 November, all inside the 90 days from 6 August (20). GitHub's issue pages and API refused this session, so open issues and reply times are unchecked. Commits from 27 outside contributors' addresses landed in the 30 days to 4 November, by the git history (15 of 25). No official SDK and no MCP server to register (0). A tests workflow runs every suite on each pull request and push to main, with a release workflow and a Docker image, but whether the default branch passes is unchecked (7 of 10). 30 + 20 + 15 + 0 + 7 = 72.", "b": "Closed service. v2.18.0 on 29 October 2026, eight days before this check (30). More than three dated releases in the 90 days from 8 August, among them 2.10.0 to 2.18.0 (20). A dated public changelog, a support address, Discord and a subreddit, with no public tracker to read reply times (8). No official SDK or MCP server to keep current (0). No public packages or CI to judge (3). 30+20+8+0+3 = 61." }, "scores": { "a": 72, "b": 61 } }, { "by": 8, "category": "reliability", "leads": "verdent", "name": "Reliability", "reasons": { "a": "Hosted reading, for HarnessRouter Cloud at api.harnessrouter.ai, as on 17 October. No status page (status.harnessrouter.ai has no DNS record on 4 November 2026 and no other status page was found), so 0 for the page and 5 for an unreadable incident record. No request rate limit with numbers was found. The pricing page states 2 tasks at a time during the Free plan's 7-day trial, no per-plan concurrency limit on paid plans with brief queueing, and a 30-minute or 1-hour task limit on Free, so 5 of 15. 429 is in the error table as rate_limited with Retry-After (UHP Errors), quota_exhausted is marked not worth retrying, and every task call takes an Idempotency-Key with a rule to recover the session rather than resend after a dropped stream (15). Terms §5.4 still give no service level outside a signed Order Form (0). The task API isn't labelled beta, while tracing and agent memory are (10). 0 + 5 + 5 + 15 + 0 + 10 = 35.", "b": "Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43." }, "scores": { "a": 35, "b": 43 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "HarnessRouter (Lumentree Corporation)", "b": "Verdent AI, Inc.", "name": "Vendor" }, { "a": "https://api.harnessrouter.ai", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides.", "b": "Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-11-03", "b": "2026-10-29", "name": "Last release" }, { "a": "no date given", "b": "2026-05-25", "name": "Terms last updated" }, { "a": "2026-07-30", "b": "2026-05-26", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "4.1k stars", "b": "none", "name": "Popularity" }, { "a": "2.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "HarnessRouter scores 47.7 (D) on agent readiness against Verdent's 39.7 (E), and leads in 6 of 7 scored categories. Verdent leads on reliability.", "question": "Which is better for AI agents, HarnessRouter or Verdent?" }, { "answer": "HarnessRouter is open source (Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides.). No open-source release is listed for Verdent.", "question": "Are HarnessRouter and Verdent open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 83 against 55", "Agent ergonomics, 73 against 35", "Security \u0026 auth, 60 against 33", "Payments \u0026 pricing, 25 against 20", "Maintenance \u0026 community, 72 against 61", "Transparency \u0026 trust, 73 against 55" ], "also": [ "A hosted endpoint, with nothing to install", "Open source" ], "goodFor": "A product team that wants to run Codex, Claude Code, Hermes or 27 other harnesses server-side behind one task, session and file contract, and switch between them by changing an ID.", "slug": "harnessrouter", "watchFor": "No status page found (status.harnessrouter.ai has no DNS record), and the terms give no service level without a signed Order Form" }, { "aheadOn": [ "Reliability, 43 against 35" ], "also": null, "goodFor": "A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.", "slug": "verdent", "watchFor": "No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot" } ], "history": { "harnessrouter": [ { "causes": [ "correction", "event" ], "date": "2026-11-04", "delta": -5.6, "from": 53.3, "fromGrade": "D", "to": 47.7, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.1, "from": 53.4, "fromGrade": "D", "to": 53.3, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 53.2, "fromGrade": "D", "to": 53.4, "toGrade": "D" } ], "verdent": null }, "job": { "capability": "agent.harness", "name": "Agent harnesses" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-harnessrouter.json", "title": "Agent Zero vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-verdent.json", "title": "Agent Zero vs Verdent", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-harnessrouter.json", "title": "Aider vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/aider-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-verdent.json", "title": "Aider vs Verdent", "url": "https://www.anchorterminal.com/compare/aider-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-harnessrouter.json", "title": "Amp vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/amp-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-verdent.json", "title": "Amp vs Verdent", "url": "https://www.anchorterminal.com/compare/amp-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-harnessrouter.json", "title": "Antigravity CLI vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-verdent.json", "title": "Antigravity CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-harnessrouter.json", "title": "Auggie CLI vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/auggie-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-verdent.json", "title": "Auggie CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/auggie-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/axlr-vs-harnessrouter.json", "title": "AXLR vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/axlr-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/axlr-vs-verdent.json", "title": "AXLR vs Verdent", "url": "https://www.anchorterminal.com/compare/axlr-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-harnessrouter.json", "title": "Claude Code vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/claude-code-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-verdent.json", "title": "Claude Code vs Verdent", "url": "https://www.anchorterminal.com/compare/claude-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-harnessrouter.json", "title": "Cline vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/cline-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-verdent.json", "title": "Cline vs Verdent", "url": "https://www.anchorterminal.com/compare/cline-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/conductor-vs-harnessrouter.json", "title": "Conductor vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/conductor-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/conductor-vs-verdent.json", "title": "Conductor vs Verdent", "url": "https://www.anchorterminal.com/compare/conductor-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-harnessrouter.json", "title": "Crush vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/crush-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-verdent.json", "title": "Crush vs Verdent", "url": "https://www.anchorterminal.com/compare/crush-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-harnessrouter.json", "title": "Cursor CLI vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-verdent.json", "title": "Cursor CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-harnessrouter.json", "title": "DeepSeek Harness (dsh) vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-verdent.json", "title": "DeepSeek Harness (dsh) vs Verdent", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harnessrouter.json", "title": "dsh-superagent (DeepSeek) vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-verdent.json", "title": "dsh-superagent (DeepSeek) vs Verdent", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/devin-vs-harnessrouter.json", "title": "Devin vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/devin-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/devin-vs-verdent.json", "title": "Devin vs Verdent", "url": "https://www.anchorterminal.com/compare/devin-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-harnessrouter.json", "title": "Droid CLI vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-verdent.json", "title": "Droid CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-harnessrouter.json", "title": "Pi vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-verdent.json", "title": "Pi vs Verdent", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-harnessrouter.json", "title": "Emdash vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/emdash-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-verdent.json", "title": "Emdash vs Verdent", "url": "https://www.anchorterminal.com/compare/emdash-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-harnessrouter.json", "title": "Gemini CLI vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-verdent.json", "title": "Gemini CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-harnessrouter.json", "title": "GitHub Copilot CLI vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-verdent.json", "title": "GitHub Copilot CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-harnessrouter.json", "title": "goose vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/goose-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-verdent.json", "title": "goose vs Verdent", "url": "https://www.anchorterminal.com/compare/goose-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-harnessrouter.json", "title": "Harness² vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/harness2-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-verdent.json", "title": "Harness² vs Verdent", "url": "https://www.anchorterminal.com/compare/harness2-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-jules.json", "title": "HarnessRouter vs Jules", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-jules" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-junie.json", "title": "HarnessRouter vs Junie CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-junie" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kilo-code-cli.json", "title": "HarnessRouter vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kimi-code-cli.json", "title": "HarnessRouter vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.json", "title": "HarnessRouter vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-letta.json", "title": "HarnessRouter vs Letta", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-letta" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-mini-swe-agent.json", "title": "HarnessRouter vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-minimax-code.json", "title": "HarnessRouter vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-mistral-vibe-cli.json", "title": "HarnessRouter vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-muse-code.json", "title": "HarnessRouter vs Muse Code", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-openai-agents-api.json", "title": "HarnessRouter vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-openai-agents-api" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-openai-codex.json", "title": "HarnessRouter vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-opencode.json", "title": "HarnessRouter vs OpenCode", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-openhands.json", "title": "HarnessRouter vs OpenHands", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-openmausbot.json", "title": "HarnessRouter vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-orca.json", "title": "HarnessRouter vs Orca", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-orca" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-paseo.json", "title": "HarnessRouter vs Paseo", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-paseo" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-prime-agent.json", "title": "HarnessRouter vs Prime Agent", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-qoder-cli.json", "title": "HarnessRouter vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-qwen-code.json", "title": "HarnessRouter vs Qwen Code", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-reflection-mirror.json", "title": "HarnessRouter vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-rovo-dev-cli.json", "title": "HarnessRouter vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-sculptor.json", "title": "HarnessRouter vs Sculptor", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-sculptor" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-t3-code.json", "title": "HarnessRouter vs T3 Code", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-traycer.json", "title": "HarnessRouter vs Traycer", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-traycer" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-unstoppable.json", "title": "HarnessRouter vs Unstoppable", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-vibe-trading.json", "title": "HarnessRouter vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-warp.json", "title": "HarnessRouter vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/jules-vs-verdent.json", "title": "Jules vs Verdent", "url": "https://www.anchorterminal.com/compare/jules-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/junie-vs-verdent.json", "title": "Junie CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/junie-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-verdent.json", "title": "Kilo Code CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-verdent.json", "title": "Kimi Code CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.json", "title": "Kiro CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/letta-vs-verdent.json", "title": "Letta vs Verdent", "url": "https://www.anchorterminal.com/compare/letta-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-verdent.json", "title": "mini-swe-agent vs Verdent", "url": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/minimax-code-vs-verdent.json", "title": "MiniMax Code vs Verdent", "url": "https://www.anchorterminal.com/compare/minimax-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-verdent.json", "title": "Mistral Vibe CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/muse-code-vs-verdent.json", "title": "Muse Code vs Verdent", "url": "https://www.anchorterminal.com/compare/muse-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-verdent.json", "title": "OpenAI Agents API vs Verdent", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/openai-codex-vs-verdent.json", "title": "OpenAI Codex vs Verdent", "url": "https://www.anchorterminal.com/compare/openai-codex-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/opencode-vs-verdent.json", "title": "OpenCode vs Verdent", "url": "https://www.anchorterminal.com/compare/opencode-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/openhands-vs-verdent.json", "title": "OpenHands vs Verdent", "url": "https://www.anchorterminal.com/compare/openhands-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/orca-vs-verdent.json", "title": "Orca vs Verdent", "url": "https://www.anchorterminal.com/compare/orca-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/paseo-vs-verdent.json", "title": "Paseo vs Verdent", "url": "https://www.anchorterminal.com/compare/paseo-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/prime-agent-vs-verdent.json", "title": "Prime Agent vs Verdent", "url": "https://www.anchorterminal.com/compare/prime-agent-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/qoder-cli-vs-verdent.json", "title": "Qoder CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/qoder-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/qwen-code-vs-verdent.json", "title": "Qwen Code vs Verdent", "url": "https://www.anchorterminal.com/compare/qwen-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent.json", "title": "Mirror CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.json", "title": "Rovo Dev CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/sculptor-vs-verdent.json", "title": "Sculptor vs Verdent", "url": "https://www.anchorterminal.com/compare/sculptor-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/t3-code-vs-verdent.json", "title": "T3 Code vs Verdent", "url": "https://www.anchorterminal.com/compare/t3-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/traycer-vs-verdent.json", "title": "Traycer vs Verdent", "url": "https://www.anchorterminal.com/compare/traycer-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/verdent-vs-vibe-trading.json", "title": "Verdent vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/verdent-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/verdent-vs-warp.json", "title": "Verdent vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/verdent-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter.json", "title": "Clawboo vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-verdent.json", "title": "Clawboo vs Verdent", "url": "https://www.anchorterminal.com/compare/clawboo-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-harnessrouter.json", "title": "CLI Manager vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-verdent.json", "title": "CLI Manager vs Verdent", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-harnessrouter.json", "title": "Harness vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-verdent.json", "title": "Harness vs Verdent", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-paperclip.json", "title": "HarnessRouter vs Paperclip", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-parallax-agents.json", "title": "HarnessRouter vs Parallax", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-parallax-agents" }, { "json": "https://www.anchorterminal.com/compare/openmausbot-vs-verdent.json", "title": "OpenMausBot vs Verdent", "url": "https://www.anchorterminal.com/compare/openmausbot-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/paperclip-vs-verdent.json", "title": "Paperclip vs Verdent", "url": "https://www.anchorterminal.com/compare/paperclip-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/parallax-agents-vs-verdent.json", "title": "Parallax vs Verdent", "url": "https://www.anchorterminal.com/compare/parallax-agents-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/unstoppable-vs-verdent.json", "title": "Unstoppable vs Verdent", "url": "https://www.anchorterminal.com/compare/unstoppable-vs-verdent" } ], "panel": null, "scores": [ { "by": 8, "edge": "verdent", "harnessrouter": 35, "key": "reliability", "name": "Reliability", "verdent": 43, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 28, "edge": "harnessrouter", "harnessrouter": 83, "key": "schema", "name": "Schema \u0026 documentation", "verdent": 55, "weight": 13 }, { "by": 38, "edge": "harnessrouter", "harnessrouter": 73, "key": "ergonomics", "name": "Agent ergonomics", "verdent": 35, "weight": 13 }, { "by": 27, "edge": "harnessrouter", "harnessrouter": 60, "key": "security", "name": "Security \u0026 auth", "verdent": 33, "weight": 14 }, { "by": 5, "edge": "harnessrouter", "harnessrouter": 25, "key": "payments", "name": "Payments \u0026 pricing", "verdent": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 11, "edge": "harnessrouter", "harnessrouter": 72, "key": "maintenance", "name": "Maintenance \u0026 community", "verdent": 61, "weight": 7 }, { "by": 18, "edge": "harnessrouter", "harnessrouter": 73, "key": "transparency", "name": "Transparency \u0026 trust", "verdent": 55, "weight": 7 } ], "summary": "HarnessRouter scores 47.7 (D) on agent readiness against Verdent's 39.7 (E), and leads in 6 of 7 scored categories. Verdent leads on reliability. Both do agent harnesses.", "tasks": null, "tutorials": [], "verdicts": { "harnessrouter": "A product's server sends a task to a named harness and gets streamed progress, sessions and files back, under a published OpenAPI contract with idempotency keys and a closed set of error codes. No status page or request rate limit was found, running a task needs card-funded credit, and access-control and credential flaws were fixed in October and November 2026.", "verdent": "A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/harnessrouter-vs-verdent", "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.min.md" }, "markdown": "HarnessRouter scores 47.7 (D) on agent readiness against Verdent's 39.7 (E), and leads in 6 of 7 scored categories. Verdent leads on reliability. Both do agent harnesses.\n\n- HarnessRouter: grade D, 47.7/100, rank #1144 of 1510. Markdown https://www.anchorterminal.com/tools/harnessrouter.md · JSON https://www.anchorterminal.com/api/v1/tools/harnessrouter.json\n- Verdent: grade E, 39.7/100, rank #1336 of 1510. Markdown https://www.anchorterminal.com/tools/verdent.md · JSON https://www.anchorterminal.com/api/v1/tools/verdent.json\n- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md\n- All 1500 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### HarnessRouter (D)\n\nGood for: A product team that wants to run Codex, Claude Code, Hermes or 27 other harnesses server-side behind one task, session and file contract, and switch between them by changing an ID.\n\nAhead on:\n- Schema \u0026 documentation, 83 against 55\n- Agent ergonomics, 73 against 35\n- Security \u0026 auth, 60 against 33\n- Payments \u0026 pricing, 25 against 20\n- Maintenance \u0026 community, 72 against 61\n- Transparency \u0026 trust, 73 against 55\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Open source\n\nWatch for: No status page found (status.harnessrouter.ai has no DNS record), and the terms give no service level without a signed Order Form\n\n### Verdent (E)\n\nGood for: A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.\n\nAhead on:\n- Reliability, 43 against 35\n\nWatch for: No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot\n\n\n## Why the edge\n\n### Agent ergonomics: HarnessRouter +38\n\n- HarnessRouter (73): API reading. Sessions, turns and files are separate reads, and list endpoints take limit and cursor, but there's no field selection on a response (15 of 25). Cursor paging on session and memory lists with a bounded limit, and few filters found (14 of 20). One error envelope with type, code, param and detail, a closed code set, a retry rule per code and a 422 that lists every failed field without echoing the body (18 of 20). Idempotency-Key on task creation, reuse only for the same request, recover from the session after a drop, and an explicit cancel because closing the stream doesn't stop work (18 of 20). Only input is required to run a task, and budgets default to 400 steps, 7,200 seconds and $10. No official SDK, only the OpenAI Responses shape, clients generated from the OpenAPI file and an Agent Skill (8 of 15). 73 in all.\n- Verdent (35): Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.\n\n### Schema \u0026 documentation: HarnessRouter +28\n\n- HarnessRouter (83): API reading. UHP's OpenAPI 3.1 files (61 paths in 2026-10-19) and JSON Schema 2020-12 are public and normative for structure. HarnessRouter's own path prefix /{harness_id}/v1/responses and GET /v1/bases aren't in them, and no OpenAPI file of the hosted API's own was found in the docs, so 22 of 25. llms.txt, llms-full.txt, agents.md, docs.md, pricing.md and harnesses.md (10). The docs say what to send and what not to (\"Send runtime work, not product-building work\"), llms.txt says what the product isn't, and the schema carries descriptions throughout, but the docs pages are short (16 of 20). Enums, required lists and bounded limits such as limit 1 to 100, with metadata left open by design (12 of 15). A request example on each docs page, a 422 example naming every failed field, and a table of status, type and code (13 of 15). Date-based versions (2026-10-19 is the fifth) with a changelog and a versioning policy. Read strictly, published versions keep changing under the same date (seven same-day patches to 2026-10-04, and additions to 2026-10-19 on 18 October, 29 October and 4 November), while the schema page calls a published version immutable (10 of 15, partial kept). The conformance page and the suite's README now agree on 101 checks. 22 + 10 + 16 + 12 + 13 + 10 = 83.\n- Verdent (55): Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as \"certain tool executions\" and \"destructive operations\" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55.\n\n### Security \u0026 auth: HarnessRouter +27\n\n- HarnessRouter (60): Hosted reading. Bearer Workspace API keys, revocable at once through the API, held to one workspace or reaching the organisation, with harness-bound calibration credentials. No OAuth, per-endpoint scopes or expiry found (20 of 30). Least privilege 10 of 20. disabled_tools per configured agent, enforced by the runtime only where GET /v1/bases says hard, and per-turn cost and step caps, with no approval step for actions a harness takes. Prompt injection 10 of 15. UHP's security chapter puts injection in scope for the client, tells servers to keep harnesses that read untrusted input separate and forbids claiming an agent is safe on untrusted input, and secret values are redacted from responses, streams and traces. Operator visibility 10 of 15. A cost breakdown per task on every plan, and the step-by-step trace is beta, included in Scale or $50 a month. Security programme 10 of 20 (was 8). A disclosure policy (v1.0, effective 30 July 2026) with safe harbour and no bounty, SECURITY.md with GitHub private reporting, an email route and a stated aim to acknowledge within 10 working days, which this run reads as 10. GHSA identifiers are cited in public fix commits; no security.txt and no SOC 2 or ISO 27001 found. 20 + 10 + 10 + 10 + 10 = 60.\n- Verdent (33): Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.\n\n### Transparency \u0026 trust: HarnessRouter +18\n\n- HarnessRouter (73): Editorial half. The server, specification, schema and conformance suite are Apache-2.0. The Cloud's own billing and deployment wasn't confirmed to match the open code, and the Agent Skill has a custom licence for some guides (25 of 30). The privacy policy, DPA, subprocessor list and a retention page agree. Customer content isn't used for training without an opt-in, and periods are stated (tasks deleted at once, agents and files after 30 days, backups within 14 days, credentials within 90, free-plan task records 7 days). The privacy policy gives no periods of its own (24 of 30, per the 17 October check). Deprecation 15 of 20 (was 14). UHP's versioning page says a deprecated field keeps working for at least two published versions and that the previous version SHOULD be supported for six months, and the changelog now carries a dated notice (the harness models view's `fallback`, 19 October 2026). The rule is counted in versions, not time, so dated notices give 15. Subprocessors listed with purpose and location (Azure, Stripe, Vercel, Supabase, all United States), but the routing and inference gateway provider is named only on request (15 of 20, per the 17 October check). 25 + 24 + 15 + 15 = 79. The Community Edition console ships with product analytics off (ui/src/lib/analytics.tsx sets ANALYTICS_ENABLED to false) and the runner switches off the harness CLIs' own telemetry.\n- Verdent (55): Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47.\n\n### Maintenance \u0026 community: HarnessRouter +11\n\n- HarnessRouter (72): Open-source reading of the repository behind the hosted service. Last tag v0.38.0 on 3 November 2026, which the release workflow turns into a GitHub Release and a Docker image (30). 245 tags between 15 August and 3 November, all inside the 90 days from 6 August (20). GitHub's issue pages and API refused this session, so open issues and reply times are unchecked. Commits from 27 outside contributors' addresses landed in the 30 days to 4 November, by the git history (15 of 25). No official SDK and no MCP server to register (0). A tests workflow runs every suite on each pull request and push to main, with a release workflow and a Docker image, but whether the default branch passes is unchecked (7 of 10). 30 + 20 + 15 + 0 + 7 = 72.\n- Verdent (61): Closed service. v2.18.0 on 29 October 2026, eight days before this check (30). More than three dated releases in the 90 days from 8 August, among them 2.10.0 to 2.18.0 (20). A dated public changelog, a support address, Discord and a subreddit, with no public tracker to read reply times (8). No official SDK or MCP server to keep current (0). No public packages or CI to judge (3). 30+20+8+0+3 = 61.\n\n### Reliability: Verdent +8\n\n- HarnessRouter (35): Hosted reading, for HarnessRouter Cloud at api.harnessrouter.ai, as on 17 October. No status page (status.harnessrouter.ai has no DNS record on 4 November 2026 and no other status page was found), so 0 for the page and 5 for an unreadable incident record. No request rate limit with numbers was found. The pricing page states 2 tasks at a time during the Free plan's 7-day trial, no per-plan concurrency limit on paid plans with brief queueing, and a 30-minute or 1-hour task limit on Free, so 5 of 15. 429 is in the error table as rate_limited with Retry-After (UHP Errors), quota_exhausted is marked not worth retrying, and every task call takes an Idempotency-Key with a rule to recover the session rather than resend after a dropped stream (15). Terms §5.4 still give no service level outside a signed Order Form (0). The task API isn't labelled beta, while tracing and agent memory are (10). 0 + 5 + 5 + 15 + 0 + 10 = 35.\n- Verdent (43): Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43.\n\n## Score by category\n\n| Category | Weight | HarnessRouter | Verdent | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 43 | Verdent +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 55 | HarnessRouter +28 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 35 | HarnessRouter +38 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 33 | HarnessRouter +27 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 20 | HarnessRouter +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 72 | 61 | HarnessRouter +11 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 55 | HarnessRouter +18 |\n| Negative events | ≤15 | -11 | -2 | |\n| **Total** | | **47.7 · D** | **39.7 · E** | |\n\n## Facts side by side\n\n| Fact | HarnessRouter | Verdent |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | HarnessRouter (Lumentree Corporation) | Verdent AI, Inc. |\n| Hosted endpoint | `https://api.harnessrouter.ai` | no (local only) |\n| Transports | HTTP | |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides. | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-11-03 | 2026-10-29 |\n| Terms last updated | no date given | 2026-05-25 |\n| Privacy policy last updated | 2026-07-30 | 2026-05-26 |\n| Customer content may train models | yes, with an opt-out | yes |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 4.1k stars | none |\n| Agent reviews | 2.5/5 (4) | none |\n\n## How the scores have moved\n\n### HarnessRouter\n\n- -5.6 on 4 November 2026: correction, negative event\n- -0.1 on 30 October 2026: checklist\n- +0.2 on 27 October 2026: checklist\n\n### Verdent\n\nNo score change since it was listed.\n\n## Verdicts\n\n**HarnessRouter.** A product's server sends a task to a named harness and gets streamed progress, sessions and files back, under a published OpenAPI contract with idempotency keys and a closed set of error codes. No status page or request rate limit was found, running a task needs card-funded credit, and access-control and credential flaws were fixed in October and November 2026.\n\n**Verdent.** A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026.\n\n## Before you call either\n\n### HarnessRouter\n\n1. Name the harness yourself. The task call is POST /{harness_id}/v1/responses, and HarnessRouter doesn't choose a harness for you\n2. Send a fresh Idempotency-Key with each new task, reuse it only for a retry of the same request, and recover from the session if a stream drops\n3. Call cancel to stop work. Closing the SSE connection leaves the agent running and billing\n4. Keep the Workspace API key on the server. The docs forbid calling the API from a browser with it\n5. Check each tool's enforcement in GET /v1/bases. On bases marked instruction, disabled_tools is a request to the model, not a block\n\n### Verdent\n\n1. Don't plan to drive Verdent headless. Hand the task to the person using the desktop app, or use a harness with a print mode\n2. Start large changes in Plan Mode and review plan.md before switching to Agent Mode\n3. Add MCP servers in the project's .mcp.json or ~/.verdent/mcp.json in the mcpServers shape\n4. Keep work under git, since rollback relies on git and there is no sandbox\n5. Budget in credits at about $0.059 each, because there is no free allowance since 29 October 2026\n\n## Questions\n\n### Which is better for AI agents, HarnessRouter or Verdent?\n\nHarnessRouter scores 47.7 (D) on agent readiness against Verdent's 39.7 (E), and leads in 6 of 7 scored categories. Verdent leads on reliability.\n\n### Are HarnessRouter and Verdent open source?\n\nHarnessRouter is open source (Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides.). No open-source release is listed for Verdent.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.json, and with the fewest tokens: https://www.anchorterminal.com/compare/harnessrouter-vs-verdent.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"harnessrouter\", \"b\": \"verdent\"}`. From a terminal: `anchor compare harnessrouter verdent`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/harnessrouter.json and https://www.anchorterminal.com/api/v1/tools/verdent.json\n\n## Other comparisons with HarnessRouter or Verdent\n\n- [Agent Zero vs HarnessRouter](https://www.anchorterminal.com/compare/agent-zero-vs-harnessrouter.md)\n- [Agent Zero vs Verdent](https://www.anchorterminal.com/compare/agent-zero-vs-verdent.md)\n- [Aider vs HarnessRouter](https://www.anchorterminal.com/compare/aider-vs-harnessrouter.md)\n- [Aider vs Verdent](https://www.anchorterminal.com/compare/aider-vs-verdent.md)\n- [Amp vs HarnessRouter](https://www.anchorterminal.com/compare/amp-vs-harnessrouter.md)\n- [Amp vs Verdent](https://www.anchorterminal.com/compare/amp-vs-verdent.md)\n- [Antigravity CLI vs HarnessRouter](https://www.anchorterminal.com/compare/antigravity-cli-vs-harnessrouter.md)\n- [Antigravity CLI vs Verdent](https://www.anchorterminal.com/compare/antigravity-cli-vs-verdent.md)\n- [Auggie CLI vs HarnessRouter](https://www.anchorterminal.com/compare/auggie-vs-harnessrouter.md)\n- [Auggie CLI vs Verdent](https://www.anchorterminal.com/compare/auggie-vs-verdent.md)\n- [AXLR vs HarnessRouter](https://www.anchorterminal.com/compare/axlr-vs-harnessrouter.md)\n- [AXLR vs Verdent](https://www.anchorterminal.com/compare/axlr-vs-verdent.md)\n- [Claude Code vs HarnessRouter](https://www.anchorterminal.com/compare/claude-code-vs-harnessrouter.md)\n- [Claude Code vs Verdent](https://www.anchorterminal.com/compare/claude-code-vs-verdent.md)\n- [Cline vs HarnessRouter](https://www.anchorterminal.com/compare/cline-vs-harnessrouter.md)\n- [Cline vs Verdent](https://www.anchorterminal.com/compare/cline-vs-verdent.md)\n- [Conductor vs HarnessRouter](https://www.anchorterminal.com/compare/conductor-vs-harnessrouter.md)\n- [Conductor vs Verdent](https://www.anchorterminal.com/compare/conductor-vs-verdent.md)\n- [Crush vs HarnessRouter](https://www.anchorterminal.com/compare/crush-vs-harnessrouter.md)\n- [Crush vs Verdent](https://www.anchorterminal.com/compare/crush-vs-verdent.md)\n- [Cursor CLI vs HarnessRouter](https://www.anchorterminal.com/compare/cursor-cli-vs-harnessrouter.md)\n- [Cursor CLI vs Verdent](https://www.anchorterminal.com/compare/cursor-cli-vs-verdent.md)\n- [DeepSeek Harness (dsh) vs HarnessRouter](https://www.anchorterminal.com/compare/deepseek-harness-vs-harnessrouter.md)\n- [DeepSeek Harness (dsh) vs Verdent](https://www.anchorterminal.com/compare/deepseek-harness-vs-verdent.md)\n- [dsh-superagent (DeepSeek) vs HarnessRouter](https://www.anchorterminal.com/compare/deepseek-superagent-vs-harnessrouter.md)\n- [dsh-superagent (DeepSeek) vs Verdent](https://www.anchorterminal.com/compare/deepseek-superagent-vs-verdent.md)\n- [Devin vs HarnessRouter](https://www.anchorterminal.com/compare/devin-vs-harnessrouter.md)\n- [Devin vs Verdent](https://www.anchorterminal.com/compare/devin-vs-verdent.md)\n- [Droid CLI vs HarnessRouter](https://www.anchorterminal.com/compare/droid-cli-vs-harnessrouter.md)\n- [Droid CLI vs Verdent](https://www.anchorterminal.com/compare/droid-cli-vs-verdent.md)\n- [Pi vs HarnessRouter](https://www.anchorterminal.com/compare/earendil-pi-vs-harnessrouter.md)\n- [Pi vs Verdent](https://www.anchorterminal.com/compare/earendil-pi-vs-verdent.md)\n- [Emdash vs HarnessRouter](https://www.anchorterminal.com/compare/emdash-vs-harnessrouter.md)\n- [Emdash vs Verdent](https://www.anchorterminal.com/compare/emdash-vs-verdent.md)\n- [Gemini CLI vs HarnessRouter](https://www.anchorterminal.com/compare/gemini-cli-vs-harnessrouter.md)\n- [Gemini CLI vs Verdent](https://www.anchorterminal.com/compare/gemini-cli-vs-verdent.md)\n- [GitHub Copilot CLI vs HarnessRouter](https://www.anchorterminal.com/compare/github-copilot-cli-vs-harnessrouter.md)\n- [GitHub Copilot CLI vs Verdent](https://www.anchorterminal.com/compare/github-copilot-cli-vs-verdent.md)\n- [goose vs HarnessRouter](https://www.anchorterminal.com/compare/goose-vs-harnessrouter.md)\n- [goose vs Verdent](https://www.anchorterminal.com/compare/goose-vs-verdent.md)\n- [Harness² vs HarnessRouter](https://www.anchorterminal.com/compare/harness2-vs-harnessrouter.md)\n- [Harness² vs Verdent](https://www.anchorterminal.com/compare/harness2-vs-verdent.md)\n- [HarnessRouter vs Jules](https://www.anchorterminal.com/compare/harnessrouter-vs-jules.md)\n- [HarnessRouter vs Junie CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-junie.md)\n- [HarnessRouter vs Kilo Code CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kilo-code-cli.md)\n- [HarnessRouter vs Kimi Code CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kimi-code-cli.md)\n- [HarnessRouter vs Kiro CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.md)\n- [HarnessRouter vs Letta](https://www.anchorterminal.com/compare/harnessrouter-vs-letta.md)\n- [HarnessRouter vs mini-swe-agent](https://www.anchorterminal.com/compare/harnessrouter-vs-mini-swe-agent.md)\n- [HarnessRouter vs MiniMax Code](https://www.anchorterminal.com/compare/harnessrouter-vs-minimax-code.md)\n- [HarnessRouter vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-mistral-vibe-cli.md)\n- [HarnessRouter vs Muse Code](https://www.anchorterminal.com/compare/harnessrouter-vs-muse-code.md)\n- [HarnessRouter vs OpenAI Agents API](https://www.anchorterminal.com/compare/harnessrouter-vs-openai-agents-api.md)\n- [HarnessRouter vs OpenAI Codex](https://www.anchorterminal.com/compare/harnessrouter-vs-openai-codex.md)\n- [HarnessRouter vs OpenCode](https://www.anchorterminal.com/compare/harnessrouter-vs-opencode.md)\n- [HarnessRouter vs OpenHands](https://www.anchorterminal.com/compare/harnessrouter-vs-openhands.md)\n- [HarnessRouter vs OpenMausBot](https://www.anchorterminal.com/compare/harnessrouter-vs-openmausbot.md)\n- [HarnessRouter vs Orca](https://www.anchorterminal.com/compare/harnessrouter-vs-orca.md)\n- [HarnessRouter vs Paseo](https://www.anchorterminal.com/compare/harnessrouter-vs-paseo.md)\n- [HarnessRouter vs Prime Agent](https://www.anchorterminal.com/compare/harnessrouter-vs-prime-agent.md)\n- [HarnessRouter vs Qoder CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-qoder-cli.md)\n- [HarnessRouter vs Qwen Code](https://www.anchorterminal.com/compare/harnessrouter-vs-qwen-code.md)\n- [HarnessRouter vs Mirror CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-reflection-mirror.md)\n- [HarnessRouter vs Rovo Dev CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-rovo-dev-cli.md)\n- [HarnessRouter vs Sculptor](https://www.anchorterminal.com/compare/harnessrouter-vs-sculptor.md)\n- [HarnessRouter vs T3 Code](https://www.anchorterminal.com/compare/harnessrouter-vs-t3-code.md)\n- [HarnessRouter vs Traycer](https://www.anchorterminal.com/compare/harnessrouter-vs-traycer.md)\n- [HarnessRouter vs Unstoppable](https://www.anchorterminal.com/compare/harnessrouter-vs-unstoppable.md)\n- [HarnessRouter vs Vibe-Trading](https://www.anchorterminal.com/compare/harnessrouter-vs-vibe-trading.md)\n- [HarnessRouter vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/harnessrouter-vs-warp.md)\n- [Jules vs Verdent](https://www.anchorterminal.com/compare/jules-vs-verdent.md)\n- [Junie CLI vs Verdent](https://www.anchorterminal.com/compare/junie-vs-verdent.md)\n- [Kilo Code CLI vs Verdent](https://www.anchorterminal.com/compare/kilo-code-cli-vs-verdent.md)\n- [Kimi Code CLI vs Verdent](https://www.anchorterminal.com/compare/kimi-code-cli-vs-verdent.md)\n- [Kiro CLI vs Verdent](https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.md)\n- [Letta vs Verdent](https://www.anchorterminal.com/compare/letta-vs-verdent.md)\n- [mini-swe-agent vs Verdent](https://www.anchorterminal.com/compare/mini-swe-agent-vs-verdent.md)\n- [MiniMax Code vs Verdent](https://www.anchorterminal.com/compare/minimax-code-vs-verdent.md)\n- [Mistral Vibe CLI vs Verdent](https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-verdent.md)\n- [Muse Code vs Verdent](https://www.anchorterminal.com/compare/muse-code-vs-verdent.md)\n- [OpenAI Agents API vs Verdent](https://www.anchorterminal.com/compare/openai-agents-api-vs-verdent.md)\n- [OpenAI Codex vs Verdent](https://www.anchorterminal.com/compare/openai-codex-vs-verdent.md)\n- [OpenCode vs Verdent](https://www.anchorterminal.com/compare/opencode-vs-verdent.md)\n- [OpenHands vs Verdent](https://www.anchorterminal.com/compare/openhands-vs-verdent.md)\n- [Orca vs Verdent](https://www.anchorterminal.com/compare/orca-vs-verdent.md)\n- [Paseo vs Verdent](https://www.anchorterminal.com/compare/paseo-vs-verdent.md)\n- [Prime Agent vs Verdent](https://www.anchorterminal.com/compare/prime-agent-vs-verdent.md)\n- [Qoder CLI vs Verdent](https://www.anchorterminal.com/compare/qoder-cli-vs-verdent.md)\n- [Qwen Code vs Verdent](https://www.anchorterminal.com/compare/qwen-code-vs-verdent.md)\n- [Mirror CLI vs Verdent](https://www.anchorterminal.com/compare/reflection-mirror-vs-verdent.md)\n- [Rovo Dev CLI vs Verdent](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-verdent.md)\n- [Sculptor vs Verdent](https://www.anchorterminal.com/compare/sculptor-vs-verdent.md)\n- [T3 Code vs Verdent](https://www.anchorterminal.com/compare/t3-code-vs-verdent.md)\n- [Traycer vs Verdent](https://www.anchorterminal.com/compare/traycer-vs-verdent.md)\n- [Verdent vs Vibe-Trading](https://www.anchorterminal.com/compare/verdent-vs-vibe-trading.md)\n- [Verdent vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/verdent-vs-warp.md)\n- [Clawboo vs HarnessRouter](https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter.md)\n- [Clawboo vs Verdent](https://www.anchorterminal.com/compare/clawboo-vs-verdent.md)\n- [CLI Manager vs HarnessRouter](https://www.anchorterminal.com/compare/cli-manager-vs-harnessrouter.md)\n- [CLI Manager vs Verdent](https://www.anchorterminal.com/compare/cli-manager-vs-verdent.md)\n- [Harness vs HarnessRouter](https://www.anchorterminal.com/compare/harness-autonomous-vs-harnessrouter.md)\n- [Harness vs Verdent](https://www.anchorterminal.com/compare/harness-autonomous-vs-verdent.md)\n- [HarnessRouter vs Paperclip](https://www.anchorterminal.com/compare/harnessrouter-vs-paperclip.md)\n- [HarnessRouter vs Parallax](https://www.anchorterminal.com/compare/harnessrouter-vs-parallax-agents.md)\n- [OpenMausBot vs Verdent](https://www.anchorterminal.com/compare/openmausbot-vs-verdent.md)\n- [Paperclip vs Verdent](https://www.anchorterminal.com/compare/paperclip-vs-verdent.md)\n- [Parallax vs Verdent](https://www.anchorterminal.com/compare/parallax-agents-vs-verdent.md)\n- [Unstoppable vs Verdent](https://www.anchorterminal.com/compare/unstoppable-vs-verdent.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "HarnessRouter vs Verdent", "url": "" } ], "description": "HarnessRouter scores 47.7 (D) to Verdent's 39.7 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HarnessRouter D 47.7", "Verdent E 39.7", "scores" ], "h1": "HarnessRouter vs Verdent", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/harnessrouter-vs-verdent", "published": "2026-10-01", "section": "tools", "title": "HarnessRouter vs Verdent for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-verdent" }, "tokens": { "markdown": 7350, "slim": 3480 }, "version": 1 }