# Paperclip vs Verdent (slim)

> Paperclip scores 52.6 (D) to Verdent's 39.7 (E) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/paperclip-vs-verdent.md (~6,350 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/paperclip-vs-verdent.json · canonical https://www.anchorterminal.com/compare/paperclip-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)

Paperclip scores 52.6 (D) on agent readiness against Verdent's 39.7 (E), and leads in every scored category. Both do multi-agent orchestration.

- Paperclip: D 52.6, rank #982 of 1510 · https://www.anchorterminal.com/tools/paperclip.min.md
- Verdent: E 39.7, rank #1336 of 1510 · https://www.anchorterminal.com/tools/verdent.min.md
- Paperclip, good for Someone running several coding or operations agents who wants one place for tasks, budgets, approvals and history across harnesses. Ahead on Reliability, 59 against 43; Schema & documentation, 81 against 55; Agent ergonomics, 70 against 35; Security & auth, 64 against 33; Payments & pricing, 60 against 20; Maintenance & community, 78 against 61; Transparency & trust, 66 against 55. Also Free to start without a card; 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 | Paperclip | Verdent |
| --- | --- | --- |
| Reliability (16%) | 59 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 55 |
| Agent ergonomics (13%) | 70 | 35 |
| Security & auth (14%) | 64 | 33 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 61 |
| Transparency & trust (7%) | 66 | 55 |

| Fact (where they differ) | Paperclip | Verdent |
| --- | --- | --- |
| Vendor | Paperclip Labs, Inc. | Verdent AI, Inc. |
| 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-10-23 | 2026-10-29 |
| Terms last updated | 2026-07-23 | 2026-05-25 |
| Privacy policy last updated | 2026-07-23 | 2026-05-26 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 99k stars, 60k npm/wk | none |

Why the edge:
- Payments & pricing, Paperclip +40: Paperclip 60 (No payment protocol (0). Read with the self-hosted rule. The software is free under MIT with nothing to buy (20). No card and no Paperclip account (20). One `npx` command installs and starts it with no signup (20). Paperclip Cloud is a waitlist with no published price, so there is no paid option to score.); 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, Paperclip +35: Paperclip 70 (Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The MCP server lists 44 tools with no toolsets or read-only subset found, offset by compact reads such as `paperclipInboxLite` and the heartbeat context (12). Budgets by company, agent and project with an automatic pause at 100 per cent, though the README says enforcement uses recorded spend and can lag work in flight (16). `onboard --yes`, CLI commands with `--json`, the REST API and routines started by cron, webhook or API (16). Atomic task checkout with a documented 409, `Idempotency-Key` on routine triggers, saved sessions and bounded recovery (17). One command starts a server with embedded PostgreSQL, but it needs Node.js 24.11 and each harness CLI installed and signed in on the host, and we found no client SDK beyond the TypeScript plugin SDK (9).); 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, Paperclip +31: Paperclip 64 (Harness reading of the framework checklist, as used for the other harnesses. 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. Anonymous usage telemetry is on by default and goes to telemetry.paperclip.ing. The README lists what is excluded and four opt-outs, and Sentry and OpenTelemetry stay off until configured. We found no first-run notice in the CLI source (18). Board approvals for hires and strategy, execution policies and per-action connection permissions, but `claude_local` defaults `dangerouslySkipPermissions` to true, `codex_local` defaults to bypassing approvals and the sandbox, local agents run on the host, sandbox providers are optional plugins and the default `local_trusted` mode has no login (10). A documented `low_trust_review` preset contains agents that read untrusted pull requests or tickets. It is opt-in (10). An activity log of mutating actions, run logs, cost events and audited board API keys (14). SECURITY.md with GitHub private reporting and twelve advisories published per the 8 October check, three now with CVEs in OSV. No security.txt, bug bounty or SOC 2 report found (12).); 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.)
- Schema & documentation, Paperclip +26: Paperclip 81 (The running server publishes OpenAPI at `/api/openapi.json` and validates requests with Zod, and the MCP server's tools take Zod schemas. No copy of the spec is published on the docs site, and paperclip.ing/openapi.json describes only the website (22). llms.txt at paperclip.ing, and docs pages answer as Markdown at `.md` (10). An API reference page per resource and task guides, but the MCP tool descriptions are one line each, such as List agents in a company (13). Typed inputs throughout, apart from the `paperclipApiRequest` tool, which takes any path under `/api` and a JSON body (12). cURL, JavaScript and Python examples and a status-code table, with one `{error}` shape and an occasional `details` field (12). A changelog page for every stable release and release notes in the repository, but the API path carries no version (12).); 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.)
- Maintenance & community, Paperclip +17: Paperclip 78 (Version 2026.1023.0, released on 23 October 2026 per its notes and the site banner (30). Ten stable releases from 2026.817.0 (17 August) to 2026.1023.0 in the 90 days to 4 November (20). Per the 8 October check, not re-read on 4 November, 650 pull requests merged in the last 30 days, but 2,849 issues and 3,338 pull requests were open, 1,396 open issues had no comment, and 309 of the 472 still-open issues from the two weeks before had none (8). `paperclipai` and `@paperclipai/mcp-server` publish from the same release workflow. We did not check the MCP registry (12). CI on master, a lockfile refresh workflow and signed image attestations (8). 30 + 20 + 8 + 12 + 8 = 78.); 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.)
- Reliability, Paperclip +16: Paperclip 59 (Read as local software. Official npm package `paperclipai` (Node.js 24.11 or newer) and a Docker image on GHCR (20). Public CI that runs the tests (pr-trusted.yml selects and runs the test shards, and e2e.yml runs the end-to-end suite), with the pass state on master unreadable on 4 November 2026 because GitHub's pages answer 403 here (15). Per the 8 October check, not re-read on 4 November, 2,849 open issues, 125 labelled bug, 1,599 opened before 8 July, and 78 closed in the last 30 days against 686 opened (6). Calendar versions in semver syntax, with a Breaking Changes section and an upgrade guide in release notes, but breaking changes arrive in ordinary releases and 2026.916.0 carried five (10). No 1.0. The npm `latest` tag is called the stable channel and follows a beta soak of at least three days, while the roadmap says the product is still moving quickly, so half credit (8). 20 + 15 + 6 + 10 + 8 = 59.); 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.)