# EverOS vs Honcho (slim)

> EverOS scores 69.4 (B) to Honcho's 61.6 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/everos-vs-honcho.md (~4,500 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/everos-vs-honcho.json · canonical https://www.anchorterminal.com/compare/everos-vs-honcho
- 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)

EverOS scores 69.4 (B) on agent readiness against Honcho's 61.6 (C), and leads in 4 of 7 scored categories. Honcho leads on security & auth and payments & pricing. Both do agent memory. Honcho accepts x402. EverOS doesn't.

- EverOS: B 69.4, rank #247 of 1510 · https://www.anchorterminal.com/tools/everos.min.md
- Honcho: C 61.6, rank #603 of 1510 · https://www.anchorterminal.com/tools/honcho.min.md
- EverOS, good for Self-hosted memory for agents and apps that want Markdown as the source of truth and separate user and agent tracks. Ahead on Reliability, 79 against 50; Schema & documentation, 89 against 84; Agent ergonomics, 78 against 71. Also No key needed to call it; Runs on your own machine; No incidents deducted, where Honcho loses 6 points for them.
- Honcho, good for Products that model the people in a conversation and want to ask questions about them, and for agents that must pay their own way. Ahead on Security & auth, 52 against 47; Payments & pricing, 80 against 40. Also An agent can pay per call over x402, with no account; A hosted endpoint, with nothing to install.

| Category | EverOS | Honcho |
| --- | --- | --- |
| Reliability (16%) | 79 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 84 |
| Agent ergonomics (13%) | 78 | 71 |
| Security & auth (14%) | 47 | 52 |
| Payments & pricing (10%) | 40 | 80 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 83 |
| Transparency & trust (7%) | 71 | 69 |

| Fact (where they differ) | EverOS | Honcho |
| --- | --- | --- |
| Vendor | Evermind AI, Inc. | Plastic Labs |
| Hosted endpoint | no (local only) | `https://api.honcho.dev/v3` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | yes, from $0.001/call |
| Licence | Apache-2.0 | AGPL-3.0 |
| Tools exposed | 7 | 40 |
| MCP registry | not listed | `io.github.plastic-labs/honcho` |
| Last release | 2026-10-22 | 2026-10-29 |
| Terms last updated | 2026-01-20 | no date given |
| Privacy policy last updated | 2026-01-20 | 2025-04-24 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 14k stars, 4k PyPI/wk | 7.4k stars, 18k npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Payments & pricing, Honcho +40: EverOS 40 (Self-hosted rule, with the price lines read for EverOS Cloud. No x402, MPP or L402 (0 of 40). No cloud price or plan found on evermind.ai, its FAQ, terms or docs (0). The open-source runtime is free with no card (20). An agent can install it from PyPI and run it with no account (20). Total 40.); Honcho 80 (x402 and Tempo MPP on 16 endpoints at agentcash.honcho.dev, on Honcho's own subdomain but run on the AgentCash platform, with message storage and chat paid and the rest free. api.honcho.dev itself takes only keys (30 of 40). Ingestion at $2 per million tokens and chat at $0.001 to $0.50 a call are published (20). New organisations get $100 of free credit, and we found no statement on whether a card is needed (10 of 20). An agent can pay per call over x402 with no account (20).)
- Reliability, EverOS +29: EverOS 79 (Local-software lines, as a library and server the owner runs. `everos` on PyPI with Python 3.12 or newer stated, plus a Windows guide (20). ci.yml runs on pushes and pull requests and the repository has a tests tree, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 43 open issues and pull requests against 82 commits in 90 days; several outside bug reports, including a silent capture failure in the DSH plugin, have no reply (14 of 25). Keep a Changelog with semantic versioning declared and a 1.0 migration guide (15). Version 1.5.1 (15). Total 79.); Honcho 50 (Rootly status page at status.honcho.dev with Honcho API and Web Dashboard components and history (20). Per the 1 October check, the window holds slow provisioning of new instances on 17 August (about 7 hours, existing instances unaffected) and 36 minutes of migration downtime on 17 September, minor only (20). status.honcho.dev answered a Cloudflare bot check on 2 November, so 2 October to 2 November is unread and isn't credited. No published rate limits found; a Gmail import guide mentions Honcho's rate limits without numbers (0). No 429 or retry guidance found (0). No SLA found (0). The v3 API is generally available (10).)
- Agent ergonomics, EverOS +7: EverOS 78 (Read for the API, with seven MCP tools on top. Searches take `top_k` and a method, and responses can be scoped by five ids (20 of 25). Filters nest with AND and OR, and `/get` pages results (18 of 20). Errors carry typed codes and say which are retryable (16 of 20). `add` is queued and returns 202, a busy session refuses deletion with nothing deleted, and the cloud purge needs a nonce confirmed within five minutes (12 of 20). A demo runs with no key and the minimal setup needs one OpenRouter key, with a Python library and the MCP server, one language (12 of 15). Total 78.); Honcho 71 (The API's context call returns a ready block for the next prompt (15 of 25). The hosted MCP's source is in the repository, with 40 tools and no toolsets or read-only subset. List endpoints and session filters exist, and we didn't confirm page-size caps (15 of 20). 422 responses name the failing field (12 of 20). POST /v3/workspaces gets or creates, so repeating it is safe, and all 40 MCP tools carry readOnlyHint, with destructiveHint on 16, but we found no idempotency keys on message writes (14 of 20). Python and TypeScript SDKs and few required fields (15).)
- Schema & documentation, EverOS +5: EverOS 89 (OpenAPI document in the repository with 40 operations, every one with a description (25). llms.txt and llms-full.txt on docs.evermind.ai (10). Operation descriptions state purpose; when-not-to-use guidance appears in the docs, such as flush after add, rather than per operation (15 of 20). Typed request models with filter operators eq, ne, gt, gte, lt, lte and in, and 422 on malformed ids (12 of 15). curl examples for add, flush and search, and typed error codes such as SESSION_BUSY and EXTERNAL_SERVICE_UNAVAILABLE (12 of 15). `/api/v2` with `/api/v1` kept as a legacy alias, a changelog and release notes (15). Total 89.); Honcho 84 (OpenAPI specs for v1, v2 and v3 linked from llms.txt, at honcho.dev/docs/v3/openapi.json for the current version (25). llms.txt (10). Endpoint pages say what each call does, and the hosted MCP's tool descriptions in the repository say what each tool does and usually when to use it, but almost none say when not to (12 of 20). Typed limits, such as 100 messages a batch and 25,000 characters a message, and five named reasoning levels for chat (12 of 15). Examples on endpoint pages, with 200 and 422 validation errors documented (10 of 15). Versioned docs, a compatibility guide and a CHANGELOG.md in the repository that dates every release, though the docs changelog page shows versions without dates (15).)
- Security & auth, Honcho +5: EverOS 47 (Framework reading for software the owner runs. The local server has no authentication and no security scheme in the OpenAPI document, relying on a 127.0.0.1 bind by default (15 of 30). No read-only mode; the cloud purge is two-step (8 of 20). Memories are extracted from conversations and returned into prompts, and everos-mcp tells hosts to save facts unprompted, with no injection guidance found (4 of 15). Structured logs and lock metrics, no audit log (6 of 15). SECURITY.md with a reporting address, five-day acknowledgement, supported versions and a published-advisories section, plus a valid security.txt (14 of 20). Total 47.); Honcho 52 (Keys can be minted through the API scoped to a workspace, a peer or a session, with an optional expires_at, and are revocable from the API Keys page. The MCP takes a Bearer key or OAuth (30). Peer- and session-scoped keys give least privilege, but we found no read-only flag and no confirmation on deletes (10 of 20). Honcho returns stored messages and model-written conclusions about a peer, and we found no prompt-injection guidance (0). No audit log or per-call log found (0). SECURITY.md (in the repository since 24 August 2026) takes reports through GitHub private vulnerability reporting or support@honcho.dev, and the site carried a SOC 2 Type I badge per the 1 October check. No security.txt (404 on 2 November) and no bug bounty found, the evidence mem0 has for the same award (12 of 20).)