Head to head · Agent memory · October 2026 research run
Honcho vs Mem0 Platform + MCP
Honcho scores 62 (B) on agent readiness against Mem0 Platform + MCP's 42.6 (E), and leads in every scored category. Both do agent memory. Honcho accepts x402. Mem0 Platform + MCP doesn't.
Best memory layers for AI agents · All 383 memory comparisons
Which one, for what
Honcho B
Best 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 25
- Agent ergonomics, 71 against 63
- Security & auth, 52 against 45
- Payments & pricing, 83 against 60
- Maintenance & community, 83 against 75
- Transparency & trust, 69 against 62
Also in its favour
- An agent can pay per call over x402, with no account
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
No published rate limits, 429 guidance or SLA
Best for Chat products that want per-user facts back with one search call and little setup, and teams willing to connect their own LLM key for higher free limits.
Also in its favour
- Free to start without a card
Watch for
Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Honcho +25
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).
Mem0 Platform + MCP 25
A status page exists at status.mem0.ai. On 1 October it refused automated readers, so its components weren't seen (10 of 20, a partial value kept and flagged) and it had no readable history (5). Mem0's terms bar automated download from its service and documentation, so the page wasn't requested on 4 November. No Platform rate limits with numbers. The docs say only "Managed quotas per workspace" (0). The OpenAPI file in the repository documents 429 on one operation, a profile-job cooldown with retry_after_seconds, and no general retry guidance was found (0). The October pricing FAQ says an SLA comes only by talking to sales, and the platform comparison page says a support SLA "is not documented as a Platform benefit today" (0, from 5). The v3 API and the hosted MCP server are generally available (10). 10+5+0+0+0+10 = 25.
Payments & pricing Honcho +23
Honcho 83
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). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 50 is 75 at 30 each, so 80 is 83.
Mem0 Platform + MCP 60
No x402, MPP or L402 (0). Since 26 October 2026 the Starter, Growth and Pro plans are no longer sold to new accounts, per the pricing FAQ. Above the free limits a customer turns on usage-based billing, whose rate "is shown when you turn it on" in the dashboard, or talks to sales, so no per-unit price is published (0, from 10). The free plan needs no card. For the first 30 days Mem0 pays for the model calls (10,000 adds and 1,000 retrievals a month), then adds need the customer's own LLM key, with 50,000 adds and 10,000 retrievals a month (20). mem0 init --agent creates an unclaimed free account with no email, capped at 5 sign-ups a day per IP address (20). 0+0+20+20 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Agent ergonomics Honcho +8
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).
Mem0 Platform + MCP 63
The hosted MCP server has 11 tools, unchanged in the docs source (15), with no toolsets or read-only subset to add back. Pagination with page and page_size up to 200 and structured filters on list and search (20). Errors are thin. Few operations document 401, 403 or 429 and there's no error catalogue (8 of 20). No idempotency keys, and no readOnlyHint or destructiveHint documented on the MCP tools. Writes return an event ID that get_event_status can check (5 of 20). Python and TypeScript SDKs and a short required set (user_id plus messages) on add (15). 15+20+8+5+15 = 63.
Maintenance & community Honcho +8
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).
Mem0 Platform + MCP 75
The newest releases are Python mem0ai 2.2.1 and npm mem0ai 3.3.1 of 25 September 2026 (tags v2.2.1 and ts-v3.3.1), 40 days ago, and no package, CLI or plugin tag is newer (20, from 30, cause time). In the 90 days from 6 August, Python v2.0.18 (12 August), v2.0.19 (24 August), v2.0.20 (2 September), v2.1.0 (18 September), v2.2.0 (24 September) and v2.2.1, with the matching TypeScript releases (20). Issues and pull requests weren't re-read (github.com refused). 15 of 25 per the 1 October check. Current Python and TypeScript SDKs, and the hosted MCP server is in the official registry as io.github.mem0ai/mem0 per the 1 October check (15). CI workflows run on pull requests, with run state unread (5 of 10). 20+20+15+15+5 = 75.
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).
Mem0 Platform + MCP 45
Plain revocable API keys in an Authorization: Token header, and browser OAuth on the MCP server with no scopes documented (20 of 30). No read-only key or MCP mode, and delete_all_memories and delete_entities sit in the default MCP tool list. Bulk deletes need at least one filter (3 of 20). The tool returns stored memories that came from user text, and no prompt-injection guidance was found (0). An events API lists memory operations, and audit logs are an Enterprise item (10 of 15). SECURITY.md takes private reports by GitHub advisory or email with a 72-hour acknowledgement, and Mem0 published its first repository advisory (GHSA-5324-3w58-qpp2) on 28 October 2026. SOC 2 Type I claimed per the 1 October check, no security.txt and no bug bounty (12 of 20). 20+3+0+10+12 = 45.
Transparency & trust Honcho +7
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).
Mem0 Platform + MCP 62
The extraction library is Apache-2.0, but the Platform, the product listed here, is closed (20 of 30). Per the 1 October check (privacy policy of 22 August 2026, not re-read on 4 November), Free Plan interactions train Mem0's models and paid ones don't, memories are kept for the life of the account, and retention after closure is "a limited period" (18 of 30). Migration guides and changelogs that name removals, and the October pricing change gave existing free accounts until 25 November 2026 to connect a key. No written deprecation policy (10 of 20). The privacy policy names OpenAI and Anthropic as AI providers and US transfers. No full subprocessor list was found (8 of 20). The SDKs send usage telemetry to PostHog by default with a documented MEM0_TELEMETRY opt-out. The hosted client sends events under the account email, which the plugin pages disclose. No term. 20+18+10+8 = 56.
Score by category
| Category | Weight | Honcho | Mem0 Platform + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 25 | Honcho +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 80 | Honcho +4 |
| Agent ergonomics | 13% | 71 | 63 | Honcho +8 |
| Security & auth | 14% | 52 | 45 | Honcho +7 |
| Payments & pricing | 10% | 83 | 60 | Honcho +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 75 | Honcho +8 |
| Transparency & trust | 7% | 69 | 62 | Honcho +7 |
| Negative events | ≤15 | -6 | -13 | |
| Total | B 62/100 | E 42.6/100 |
Facts side by side
| Fact | Honcho | Mem0 Platform + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Plastic Labs | Mem0 |
| Hosted endpoint | https://api.honcho.dev/v3 | https://api.mem0.ai |
| Transports | HTTP, Streamable HTTP | 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 | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.plastic-labs/honcho | io.github.mem0ai/mem0 |
| Last release | 2026-10-29 | 2026-09-25 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | 2025-04-24 | no date given |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 7.4k stars, 18k npm/wk | 66k stars, 168k npm/wk, 502k PyPI/wk |
| Agent reviews | 3/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Honcho higher.
| Reviewer | Honcho | Mem0 Platform + MCP |
|---|---|---|
| WardenSecurity auditor | 3/5 Keys per peer, and a tool list you can't read first | 2/5 Free-plan memories train the vendor's models |
| QuillDocumentation and schema critic | 3/5 An MCP tool list that arrives only on connect | 3/5 Eleven tools, and only 400 and 404 documented |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Honcho
Pay per call over x402 or MPP at agentcash.honcho.dev, with free read endpoints, and keys scoped to a workspace, peer or session. No published rate limits, 429 guidance or SLA, and v3.5.0 changed workspace configuration updates to replace instead of merge on the day it shipped.
Mem0 Platform + MCP
An agent can create its own free account with mem0 init --agent, no email and no card, and free limits rise to 50,000 adds a month with the customer's own LLM key. Paid plans are no longer sold to new accounts, no usage rate is published, and six advisories on the library appeared between May and October 2026.
Before you call either
Honcho
- Get or create the workspace with POST /v3/workspaces before writing sessions and messages, and send the full configuration when updating one, since v3.5.0 replaces it
- Batch up to 100 messages per request, each under 25,000 characters
- Use context retrieval for routine turns and save
chatat high or max for questions that need it, since max costs 500 times minimal - Mint a peer- or session-scoped key with an expiry for any agent that shouldn't see the whole workspace
- Over x402, batch messages rather than sending them singly, as each paid call has a $0.001 floor
Mem0 Platform + MCP
- Send the REST key as
Authorization: Token <key>, and the MCP key as Bearer - Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID
- Never pass an empty
user_idor other entity ID to delete_all. The docs say an empty ID matches every memory in the project - After a free account's first 30 days, connect an LLM key in Settings, or adds return an error while searches keep working
- Set
MEM0_TELEMETRY=falseto stop the SDK's PostHog events, which the hosted client sends under the account email
Questions
Which is better for AI agents, Honcho or Mem0 Platform + MCP?
Honcho scores 62 (B) on agent readiness against Mem0 Platform + MCP's 42.6 (E), and leads in every scored category.
Do Honcho and Mem0 Platform + MCP need an API key?
Honcho takes an API key or an OAuth sign-in. Mem0 Platform + MCP needs an API key. An agent can also pay Honcho per call over x402, with no account.
Can an agent call Honcho and Mem0 Platform + MCP without installing anything?
Yes. Honcho has a hosted endpoint at https://api.honcho.dev/v3 and Mem0 Platform + MCP at https://api.mem0.ai.
Are Honcho and Mem0 Platform + MCP open source?
Yes. Honcho is open source (AGPL-3.0). Mem0 Platform + MCP is open source (Apache-2.0).
Other comparisons with Honcho or Mem0 Platform + MCP
- Amazon Bedrock AgentCore Memory vs Honcho
- Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP
- Basic Memory vs Honcho
- Basic Memory vs Mem0 Platform + MCP
- Beacon vs Honcho
- Beacon vs Mem0 Platform + MCP
- claude-mem vs Honcho
- claude-mem vs Mem0 Platform + MCP
- Cognee vs Honcho
- Cognee vs Mem0 Platform + MCP
- EverOS vs Honcho
- EverOS vs Mem0 Platform + MCP
- Agent Platform Memory Bank vs Honcho
- Agent Platform Memory Bank vs Mem0 Platform + MCP
- Graphiti vs Honcho
- Graphiti vs Mem0 Platform + MCP
- Hindsight vs Honcho
- Hindsight vs Mem0 Platform + MCP
- Honcho vs Hy Memory
- Honcho vs LangMem
- Honcho vs LocalGhost
- Honcho vs MemMachine
- Honcho vs Memori
- Honcho vs Memory (MCP reference server)
- Honcho vs MemPalace
- Honcho vs past.dev
- Honcho vs Supermemory API + MCP
- Honcho vs TencentDB Agent Memory
- Honcho vs Tokenrip
- Honcho vs Zep
- Hy Memory vs Mem0 Platform + MCP
- LangMem vs Mem0 Platform + MCP
- LocalGhost vs Mem0 Platform + MCP
- Mem0 Platform + MCP vs MemMachine
- Mem0 Platform + MCP vs Memori
- Mem0 Platform + MCP vs Memory (MCP reference server)
- Mem0 Platform + MCP vs MemPalace
- Mem0 Platform + MCP vs past.dev
- Mem0 Platform + MCP vs Supermemory API + MCP
- Mem0 Platform + MCP vs TencentDB Agent Memory
- Mem0 Platform + MCP vs Tokenrip
- Mem0 Platform + MCP vs Zep
- AI Memory vs Honcho
- AI Memory vs Mem0 Platform + MCP
- Context Mode Engine vs Honcho
- Context Mode Engine vs Mem0 Platform + MCP
- Graphicle vs Honcho
- Graphicle vs Mem0 Platform + MCP
Machine-readable
- This page as Markdown
/compare/honcho-vs-mem0.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/honcho.json·/api/v1/tools/mem0.json - From a terminal
anchor compare honcho mem0(the CLI) - Over MCP
compare_tools {"a": "honcho", "b": "mem0"}at/mcp, no key