# Parallax vs Verdent (slim)

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

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

Verdent scores 39.7 (E) on agent readiness against Parallax's 38.1 (E), and leads in 4 of 7 scored categories. Parallax leads on agent ergonomics, security & auth and payments & pricing. Both do multi-agent orchestration.

- Parallax: E 38.1, rank #1365 of 1510 · https://www.anchorterminal.com/tools/parallax-agents.min.md
- Verdent: E 39.7, rank #1336 of 1510 · https://www.anchorterminal.com/tools/verdent.min.md
- Parallax, good for A developer on a Mac who runs several coding agents across Claude and Codex subscriptions and wants cross-lab review of finished sessions on GitHub. Ahead on Agent ergonomics, 42 against 35; Security & auth, 43 against 33; Payments & pricing, 30 against 20.
- 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. Ahead on Schema & documentation, 55 against 29; Maintenance & community, 61 against 56; Transparency & trust, 55 against 50.

| Category | Parallax | Verdent |
| --- | --- | --- |
| Reliability (16%) | 40 | 43 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 29 | 55 |
| Agent ergonomics (13%) | 42 | 35 |
| Security & auth (14%) | 43 | 33 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 56 | 61 |
| Transparency & trust (7%) | 50 | 55 |

| Fact (where they differ) | Parallax | Verdent |
| --- | --- | --- |
| Vendor | Conifer Solutions, Inc. | Verdent AI, Inc. |
| Transports | HTTP |  |
| Pricing | Freemium | Paid |
| Licence | Proprietary, under Conifer's Terms of Service (Conifer Solutions, Inc.). The GitHub repository holds the README and release binaries, not the source | Proprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published |
| Tools exposed | 0 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-16 | 2026-10-29 |
| Terms last updated | 2026-10-22 | 2026-05-25 |
| Privacy policy last updated | 2026-10-22 | 2026-05-26 |
| Customer content may train models | 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 |
| Agent reviews | 2/5 (4) | none |

Why the edge:
- Schema & documentation, Verdent +26: Parallax 29 (The review API has no OpenAPI or endpoint reference. Endpoints appear only in curl examples, and the base URL `$PARALLAX_URL` is not published (0). conifer.build/llms.txt covers the gateway in detail and Parallax in two lines that point to the docs (5). The docs explain sessions, sweeps, evidence states, memory and retention at length, but nothing documents the app, Captain, fallback or fast merge (8). parallax.yml keys are listed with allowed values (`deliver: proven-only`, `review: off`, severity floors, sweep modes), but request and response shapes for the API are not (5). curl examples, sample sweep lines and a table of skip reasons with the fix for each (8). Paths sit under `/v1`, with no changelog for Parallax (3).); 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.)
- Security & auth, Parallax +10: Parallax 43 (Harness reading of the framework checklist, as 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. Once installed, capture uploads transcripts, tool calls with results and source snapshots from every repository on the machine unless a local allowlist is set first, and the app updates itself by default. Uploads stop with `PARALLAX_STORE_UPLOAD=off` and the token is revocable (8). Proofs run in a throwaway cloud copy, automatic PR review is off by default and Parallax never merges its own fix PR. What Captain may do to a running agent is not documented (10). Reviewers read untrusted transcripts and code with no documented mitigation. Lessons injected into the agent come only from verified outcomes and maintainer replies, never bots, and the brief labels everything else as cited fact (8). Recall receipts, per-injection records, sweep lines, the review ledger and `GET /v1/calibration` (12). No security.txt, bug bounty, SOC 2 or advisories. The privacy policy names a contact for security reports with a two-business-day reply and lists encryption and row-level security (5).); 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.)
- Payments & pricing, Parallax +10: Parallax 30 (No x402, MPP or L402 (0). Parallax episode credit prices are read from the account after sign-in. Gateway token prices are public at `GET /v1/catalog` with no key, which covers Conifer credit spent by agents (10). $50 of Conifer credit and 5 free episodes on GitHub sign-up, with no card mentioned, and agents can run on the owner's own Claude and Codex subscriptions (20). A person has to download the app, sign in and install the GitHub App, so no autonomous onboarding (0).); 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, Parallax +7: Parallax 42 (Scored on the review API and the hooks, the only parts an agent touches. The session-start brief is cut at 6,000 characters, memory per review call at 12,000, and `lesson_cap` sets 1 to 20 lessons per person (8). `repo` filters on recall and brief, `brain=true` on the ledger, no documented pagination (4). Skip reasons such as `capture_commit_missing` and `test_configuration_missing` each come with a fix, but HTTP error codes for the API are not documented (12). A session is swept once per capture mark, retries use no extra credit, and a fix PR is reused and never reopened or merged by Parallax (14). No SDK for Parallax, and capture of every repository is the default (4).); 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.)
- Maintenance & community, Verdent +5: Parallax 56 (v1.0.2 on 16 October 2026 (30). Three releases, v1.0.0 to v1.0.2, on 15 and 16 October 2026 (20). Closed service. No public changelog. Support through a GitHub issues link, a Discord server and email, none of which we could check for replies (3). No Parallax SDK and nothing in the MCP registry. Conifer's SDK is for the gateway (0). Signed builds with checksums and a self-updater, with no CI to inspect (3).); 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, Verdent +5: Parallax 50 (Closed source under Conifer's terms, which name the company, a Delaware corporation, and Delaware law (15). The privacy policy and docs agree on 30-day session retention, consent by installing capture, the upload opt-out and deletion by request. The policy predates the app and names only Claude Code and Codex for capture, while the docs also name Cursor, Cline and Prime (18). No deprecation policy. Conifer dated the retirement of its earlier desktop download page (1 September 2026), but nothing for Parallax (3). Fly.io is named as the Parallax subprocessor with US processing. Whether the Parallax app sends telemetry is not stated, and the self-updater's off switch is documented in the README (12).); 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.)