# Paseo vs Verdent (slim)

> Paseo scores 62.1 (B) 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/paseo-vs-verdent.md (~5,200 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/compare/paseo-vs-verdent.json · canonical https://www.anchorterminal.com/compare/paseo-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)

Paseo scores 62.1 (B) on agent readiness against Verdent's 39.7 (E), and leads in every scored category. Both do agent harnesses.

- Paseo: B 62.1, rank #575 of 1486 · https://www.anchorterminal.com/tools/paseo.min.md
- Verdent: E 39.7, rank #1317 of 1486 · https://www.anchorterminal.com/tools/verdent.min.md
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Reliability, 50 against 43; Schema & documentation, 65 against 55; Agent ergonomics, 70 against 35; Security & auth, 58 against 33; Payments & pricing, 60 against 20; Maintenance & community, 75 against 61; Transparency & trust, 68 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 | Paseo | Verdent |
| --- | --- | --- |
| Reliability (16%) | 50 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 55 |
| Agent ergonomics (13%) | 70 | 35 |
| Security & auth (14%) | 58 | 33 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 61 |
| Transparency & trust (7%) | 68 | 55 |

| Fact (where they differ) | Paseo | Verdent |
| --- | --- | --- |
| Vendor | Mohamed Boudra | Verdent AI, Inc. |
| Auth | None | OAuth or key |
| Pricing | Free | Paid |
| Licence | Apache-2.0 | 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 |
| Last release | 2026-11-07 | 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 |

Why the edge:
- Payments & pricing, Paseo +40: Paseo 60 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.); 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, Paseo +35: Paseo 70 (Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).); 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, Paseo +25: Paseo 58 (Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.); 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.)
- Maintenance & community, Paseo +14: Paseo 75 (v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 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.)
- Transparency & trust, Paseo +13: Paseo 68 (Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.); 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.)
- Schema & documentation, Paseo +10: Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).); 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.)