# Agent Zero vs Orca (slim)

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

- Full: https://www.anchorterminal.com/compare/agent-zero-vs-orca.md (~5,200 tokens) · this version ~1,780 tokens · JSON https://www.anchorterminal.com/compare/agent-zero-vs-orca.json · canonical https://www.anchorterminal.com/compare/agent-zero-vs-orca
- 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)

Orca scores 57.4 (C) on agent readiness against Agent Zero's 46 (D), and leads in 3 of 7 scored categories. Agent Zero leads on security & auth, payments & pricing and transparency & trust. Both do agent harnesses.

- Agent Zero: D 46, rank #1184 of 1510 · https://www.anchorterminal.com/tools/agent-zero.min.md
- Orca: C 57.4, rank #795 of 1510 · https://www.anchorterminal.com/tools/orca.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 Security & auth, 54 against 43; Payments & pricing, 60 against 40; Transparency & trust, 64 against 54.
- Orca, good for Developers who want an orchestrator agent to split work across parallel coding agents, on desktop or mobile. Ahead on Agent ergonomics, 70 against 62. Also No incidents deducted, where Agent Zero loses 15 points for them.

| Category | Agent Zero | Orca |
| --- | --- | --- |
| Reliability (16%) | 57 | 58 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 65 |
| Agent ergonomics (13%) | 62 | 70 |
| Security & auth (14%) | 54 | 43 |
| Payments & pricing (10%) | 60 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 75 |
| Transparency & trust (7%) | 64 | 54 |

| Fact (where they differ) | Agent Zero | Orca |
| --- | --- | --- |
| Vendor | Agent Zero, s.r.o. | Lovecast Inc. |
| llms.txt | yes | no |
| Last release | 2026-11-01 | 2026-11-06 |
| Popularity | 19k stars | none |

Why the edge:
- Payments & pricing, Agent Zero +20: 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.); Orca 40 (Scored on the cloud option. No protocol (0). The cloud price wasn't found on the pages read (0). The desktop app is free and MIT with no card (20). The local app needs no sign-up that we found (20). 0 + 0 + 20 + 20 = 40.)
- Security & auth, Agent Zero +11: 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).); Orca 43 (Harness reading. Anonymous usage data with an opt-out, per the README's link to its telemetry docs (15 of 30). Worktrees per agent and a sandboxed Linux build (12 of 20). No prompt-injection guidance (5). No audit log (5). A dependency-security workflow (6 of 20). 15 + 12 + 5 + 5 + 6 = 43.)
- Transparency & trust, Agent Zero +10: Agent Zero 64 (MIT, copyright Agent Zero, s.r.o. (30). No privacy policy for the software was found. The site's cookie notice covers the website, and its terms (14 May 2026) cover the community platform. The docs say where data lives (chats, memory, secrets and settings under `/a0/usr`) and warn that model providers see what is sent to them only in general terms, with no retention statement (8 of 30). Release notes list breaking changes and removals with the release date, and one deprecated alias is named. No deprecation policy or notice period was found (8 of 20, a partial kept). No usage telemetry was found in the source. The update check is described on its settings page, which says it sends only a randomised, hashed install ID and the version number, and the same page turns it off. The ID is a hash of a random per-install token, a pseudonym under this run's reading, so the statement holds (20). 30 + 8 + 8 + 20 = 66.); Orca 54 (MIT (30). Privacy and telemetry docs on the site (not read) (18 of 30). No deprecation policy (5). Disclosed with an opt-out (15 of 20). 30 + 18 + 5 + 15 = 68.)
- Agent ergonomics, Orca +8: 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).); Orca 70 (Harness reading. An orchestrator agent that splits work across workers in their own workspaces, chat or raw CLI, a browser and a CLI in one app (70).)