# Agent Zero vs Verdent (slim)

> Agent Zero scores 46 (D) to Verdent's 39.7 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/agent-zero-vs-verdent.md (~6,750 tokens) · this version ~3,230 tokens · JSON https://www.anchorterminal.com/compare/agent-zero-vs-verdent.json · canonical https://www.anchorterminal.com/compare/agent-zero-vs-verdent
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Agent Zero scores 46 (D) on agent readiness against Verdent's 39.7 (E), and leads in every scored category. Both do agent harnesses.

- Agent Zero: D 46, rank #1168 of 1486 · https://www.anchorterminal.com/tools/agent-zero.min.md
- Verdent: E 39.7, rank #1317 of 1486 · https://www.anchorterminal.com/tools/verdent.min.md
- Agent Zero, good for A technical owner who wants an agent with its own Linux machine, reachable from Telegram, WhatsApp or email, with scheduled tasks and editable memory. Ahead on Reliability, 57 against 43; Schema & documentation, 64 against 55; Agent ergonomics, 62 against 35; Security & auth, 54 against 33; Payments & pricing, 60 against 20; Maintenance & community, 75 against 61; Transparency & trust, 64 against 55. Also No key needed to call it; Open source.
- Verdent, good 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.

| Category | Agent Zero | Verdent |
| --- | --- | --- |
| Reliability (16%) | 57 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 55 |
| Agent ergonomics (13%) | 62 | 35 |
| Security & auth (14%) | 54 | 33 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 61 |
| Transparency & trust (7%) | 64 | 55 |

| Fact (where they differ) | Agent Zero | Verdent |
| --- | --- | --- |
| Vendor | Agent Zero, s.r.o. | Verdent AI, Inc. |
| Auth | None | OAuth or key |
| Pricing | Free | Paid |
| Licence | MIT | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-11-01 | 2026-10-29 |
| Terms last updated | no document linked | 2026-05-25 |
| Privacy policy last updated | no document linked | 2026-05-26 |
| Customer content may train models | not read yet | yes |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 19k stars | none |

Why the edge:
- Payments & pricing, Agent Zero +40: Agent Zero 60 (Read with the self-hosted rule. No payment protocol in the source (0). Free under MIT with nothing to buy for the software, so 20, 20 and 20 on the last three lines. It starts with one Docker command and no account. Model usage is billed by whichever provider the owner configures, or costs nothing with a local model. The vendor's site also describes a beta LLM API whose daily quota depends on staking its A0T token. That is separate from the software and not scored.); Verdent 20 (Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20.)
- Agent ergonomics, Agent Zero +27: Agent Zero 62 (Harness reading, scored on what a person or program driving it must supply. Skills load on demand, blocked tools are removed from the prompt, chats can be compacted, and the v2.12 notes report Codex input falling from about 16.4K to 11.3K tokens, a vendor figure (18 of 25). An MCP tool timeout of 120 seconds, a limit of five consecutive unusable responses and context-window handling are set by default. No turn or spend limit was found in the reviewed docs (11 of 20). Other programs reach it through `POST /api_message`, an optional MCP server, A2A and an ACP bridge, with request and response shapes left to the source (11 of 20). An error-retry plugin, saved chats, a message queue, backups and Time Travel snapshots with diff and revert (14 of 20). One Docker command starts it and a wizard sets the model, but there is no SDK and the default has no login (8 of 15).); 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.)
- Security & auth, Agent Zero +21: Agent Zero 54 (Harness reading of the framework checklist, the one the Goose calibration dossier uses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. No usage telemetry was found in the source. An update check, on by default, posts the version and a 20-character SHA-256 hash of a random per-install id to api.agent-zero.ai. The Update Checker settings page says only that ID and the version are sent and has an off switch. Something still leaves the machine by default, so the partial is kept (22). The agent works inside a Docker container built on Kali Linux and runs as root there. Tool Access can block tools by project or profile and defaults to allow, host access through the A0 CLI is scoped by read, write and execute permissions, and no approval step was found before a shell command, a file deletion or an outgoing message. The web interface has no login until a username is set (10). Infection Check audits the agent's reasoning with a second model before each tool call and ships disabled. Scanners check plugins, skills and MCP servers before install. The channel allow-lists accept every sender when empty, and the email filter matches the claimed From address only, which the plugin README states (7). Chat logs, visible tool steps and Time Travel snapshots, with no per-call audit log. Per-process log files were removed in v2.5 (9). No SECURITY.md on 4 November, security.txt answered 404 on 12 October, and none of the eight CVEs published from 17 March to 22 October 2026 came from the vendor (VulDB, VulnCheck, MITRE and CISA assigned them). A security-review ledger in the repository records two findings, and the v2.12 notes name both fixes (6, a partial kept).); 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.)
- Reliability, Agent Zero +14: Agent Zero 57 (Read with the local-software lines, as software the owner runs. Installs from the `agent0ai/agent-zero` Docker image, an install script, or a desktop Launcher with builds for macOS, Linux and Windows on x86 and ARM64. The README says it runs wherever Docker runs. The image registry page was not read (17 of 20). The repository holds 245 files under tests/ on 4 November, and its only two workflows still publish Docker images and close inactive issues. The publish workflow runs no tests, so no public CI run shows them passing (5 of 25, a partial kept). 139 open issues and pull requests on 12 October 2026, per that check (GitHub's pages and API weren't read on 4 November). Open reports from September include a crash of `run_ui` after a failed memory consolidation (#1909), a browser worker that hangs the agent turn (#1923) and truncated backups (#1904), each with no reply or one, and a workflow closes anything inactive for 90 days (11 of 25). Release notes for v2.11, v2.12 and v2.13 carry a Breaking Changes section, but breaking changes ship in minor versions, so the numbering is not semver (9 of 15). v2.15, past 1.0 (15).); 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.)
- Maintenance & community, Agent Zero +14: Agent Zero 75 (v2.15 was tagged on 1 November 2026, 3 days before this check (30). Seven releases from 6 August, v2.9 on 12 August to v2.15, read from the clone's tags (20). Of the 40 newest open items read on 12 October, 16 are issues and 14 of those have no comment. Three security reports filed as issues were closed as completed, one in five days and two after three months. GitHub's issue pages weren't read on 4 November, so this is per the 12 October check (10 of 25). The Docker image, the desktop Launcher, the install scripts and the A0 CLI connector come from the same organisation, and the v2.14 notes point the README's Launcher links to v1.9 (10 of 15). A Docker publish workflow builds images from tags, and the v2.14 notes raise dependency security floors for aiohttp, anyio, urllib3, filelock, fsspec and multidict. No public test CI (5 of 10). 30 + 20 + 10 + 10 + 5 = 75.); 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.)
- Schema & documentation, Agent Zero +9: Agent Zero 64 (Harness reading of the lines, as the Goose calibration dossier does. No OpenAPI file. The connectivity page lists five external endpoints and the `X-API-KEY` header, then sends readers to the source or DeepWiki for request and response details. Each API handler and tool has a `.dox.md` contract file in the repository, and the MCP client JSON shape is documented (10 of 25). llms.txt at www.agent-zero.ai, and AGENTS.md contract files across the repository (10). Guides say which path to use for a need, with tables that separate the browser, the host connector, MCP and A2A (14 of 20). The v2.12 notes say 15 bundled tools gained argument descriptions in non-strict schemas, and plugin settings are typed YAML with commented examples (8 of 15). Guides carry worked examples and a troubleshooting page, with no documented error responses for the external API (9 of 15). Dated notes on every GitHub release and a release article for each version on the site, with no version prefix on API routes (13 of 15).); 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.)