# Honcho vs Memori (slim)

> Honcho scores 61.6 (C) to Memori's 44.2 (E) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

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

Honcho scores 61.6 (C) on agent readiness against Memori's 44.2 (E), and leads in every scored category. Both do agent memory. Honcho accepts x402. Memori doesn't.

- Honcho: C 61.6, rank #603 of 1510 · https://www.anchorterminal.com/tools/honcho.min.md
- Memori: E 44.2, rank #1231 of 1510 · https://www.anchorterminal.com/tools/memori.min.md
- 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 Reliability, 50 against 28; Schema & documentation, 84 against 68; Agent ergonomics, 71 against 65; Security & auth, 52 against 45; Payments & pricing, 80 against 45; Maintenance & community, 83 against 33; Transparency & trust, 69 against 52. Also An agent can pay per call over x402, with no account.
- Memori, good for Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.

| Category | Honcho | Memori |
| --- | --- | --- |
| Reliability (16%) | 50 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 68 |
| Agent ergonomics (13%) | 71 | 65 |
| Security & auth (14%) | 52 | 45 |
| Payments & pricing (10%) | 80 | 45 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 33 |
| Transparency & trust (7%) | 69 | 52 |

| Fact (where they differ) | Honcho | Memori |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Plastic Labs | Memori Labs Inc. |
| Hosted endpoint | `https://api.honcho.dev/v3` | `https://api.memorilabs.ai/mcp/` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| x402 | yes, from $0.001/call | no |
| Licence | AGPL-3.0 | Apache-2.0 |
| Tools exposed | 40 | 7 |
| MCP registry | `io.github.plastic-labs/honcho` | not listed |
| Last release | 2026-10-29 | 2026-05-27 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | 2025-04-24 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 7.4k stars, 18k npm/wk | 17k stars, 130 npm/wk, 3.8k PyPI/wk |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Maintenance & community, Honcho +50: Honcho 83 (Server v3.5.0 and both SDKs at 2.8.0 on 29 October 2026 (30). The repository's tags and dated CHANGELOG.md show 11 server releases from v3.0.12 (10 August) to v3.5.0, and SDK releases 2.3.0 to 2.8.0 (20). A maintainer answered the May outage report (#753) and moved updates to Discord, per the 1 October check; GitHub's pages answered 403 on 2 November (10 of 25). The hosted MCP is in the official registry as io.github.plastic-labs/honcho, and the SDKs are current (15). The TypeScript SDK's only runtime dependency is zod; CI workflows are in the repository but their run state wasn't read (8 of 10).); Memori 33 (SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.)
- Payments & pricing, Honcho +35: 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).); Memori 45 (No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the `memori_signup` MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.)
- Reliability, Honcho +22: 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).); Memori 28 (Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call `memori_quota` on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.)
- Transparency & trust, Honcho +17: Honcho 69 (The server is AGPL-3.0, the same code Honcho hosts, and the TypeScript SDK is Apache-2.0 (30). The terms keep data for 90 days after termination and then delete it, and a deleting-data page says what survives each kind of delete. We didn't re-read the privacy policy this run (18 of 30). Docs for v1, v2 and v3 sit side by side with a compatibility guide, but no dated notices or written policy (8 of 20). No subprocessor list or data-location statement found (0).); Memori 52 (Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46.)
- Schema & documentation, Honcho +16: 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).); Memori 68 (No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid `source` and `signal` pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.)
- Security & auth, Honcho +7: 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).); Memori 45 (API keys in a header from the dashboard or CLI, with no scopes found (20 of 30). No read-only mode or per-tool restrictions (4 of 20). Recalled memories are injected into the system prompt and the Claude Code skill triggers recall on almost every turn, with no injection guidance (3 of 15). A dashboard shows memories, retrieval and usage (8 of 15). SECURITY.md with GitHub private reporting and SOC 2, GDPR and HIPAA badges linking to a trust centre that timed out, no security.txt. Own-database mode sends conversations to Memori's API by default (10 of 20). Total 45.)