Head to head · Agent memory · October 2026 research run
Honcho vs Supermemory API + MCP
Honcho and Supermemory API + MCP score within a point of each other on agent readiness, 62 (B) and 61.5 (C). Supermemory API + MCP leads on reliability, agent ergonomics and security & auth. Both do agent memory. Honcho accepts x402. Supermemory API + 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
- Payments & pricing, 83 against 45
- Transparency & trust, 69 against 52
Also in its favour
- An agent can pay per call over x402, with no account
Watch for
No published rate limits, 429 guidance or SLA
Best for Apps that need user memory and document search over the same data, and for multi-tenant products that want a key per user.
Ahead on
- Reliability, 55 against 50
- Agent ergonomics, 76 against 71
- Security & auth, 64 against 52
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No published rate limits or 429 guidance for the API
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.
Payments & pricing Honcho +38
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.
Supermemory API + MCP 45
No x402, MPP or L402. An empty balance returns 402 with no payment payload (0). Per-unit prices without a login, re-read on 2 November, $5 per million SM tokens for plain-text memory, $10 for rich content, $5 per million searches, $100 per million operations (20). Free has $5 of credit renewed monthly, and the pricing page doesn't say whether a card is needed (10 of 20). A person signs up in the console, and the MCP signs in through a browser (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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).
Supermemory API + MCP 52
The SDKs, the hosted MCP and the tools in the public repository are MIT, but since 3 October the docs say the self-hosted server binary is built from a separate, non-public codebase and is free within a lite licence limit, so the hosted service and the engine are closed with clear terms. The 1 October reading of an MIT engine is corrected (15 of 30). The security page says customer content never trains models on any plan, and erasure works by deleting a namespace. The privacy policy (effective 29 September 2026, last updated 24 October) keeps data for the service relationship with no periods, and says disconnecting a connector won't delete synced data unless asked, while the security page says it deletes imported documents by default. The terms (2 June 2025) and privacy policy name no company (15 of 30). v3 and v4 became legacy with the dated v5 launch of 7 October and a migration command, with no shutdown date or deprecation policy (10 of 20). The privacy policy names Timescale, Cloudflare, OpenAI and Google Gemini as providers, with no full sub-processor list or data locations (5 of 20). 15 + 15 + 10 + 5 = 45.
Security & auth Supermemory API + MCP +12
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).
Supermemory API + MCP 64
Org keys have full access, but scoped keys can be limited to one or more namespaces (container tags), set to expire in 1 to 365 days and revoked (401 after). The MCP signs in with OAuth and asks which spaces to allow, and since 21 August also takes an API key as Bearer (28 of 30). Scoped keys can't read billing, change settings or mint keys, MCP spaces carry read or write permission, and the mass forget has a dry run, but there's no read-only API key (14 of 20). Supermemory ingests URLs, PDFs and web pages and returns them to the model, and we found no prompt-injection guidance (0). The Analytics API gives usage per API key, error breakdowns and stored request logs, which the docs say skip 402, 404 and 500 answers and aren't a complete audit trail (10 of 15). SOC 2 Type II, GDPR and a HIPAA BAA per the security page, with the report on request from support. No security.txt (404 on 2 November), disclosure policy, SECURITY.md or bug bounty found (12 of 20). 28 + 14 + 0 + 10 + 12 = 64.
Reliability Supermemory API + MCP +5
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).
Supermemory API + MCP 55
incident.io status page at status.supermemory.ai tracking the API and the Console, with incident pages and a feed (20). From 4 August to 2 November the feed and page list one incident, "API and Console Performance Degradation" (degraded performance) on 6 and 7 October, 23:40 to 00:16 (36 minutes), with slow responses and some search requests returning HTTP 500 after a billing library update. A short degradation reads as minor (20). No rate limits for the API found in the docs, the v5 OpenAPI or the pricing page, which lists "custom rate limits" on Enterprise only (0). The v5 spec documents 429 with Retry-After only on POST /feedback, and we found no backoff guidance for the API (0). Enterprise lists an "Uptime SLA" with no figure (5 of 10). v5 is described as the stable API (10). 20 + 20 + 0 + 0 + 5 + 10 = 55.
Agent ergonomics Supermemory API + MCP +5
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).
Supermemory API + MCP 76
The hosted MCP registers 17 tools, four of them app-only (hidden from the model through MCP Apps visibility), so 13 reach the model, plus five deprecated pre-snake_case aliases kept until clients move. 11 to 30 tools (15). v5 search and list calls take a limit of 1 to 100, cursor or page pagination and include switches, and lists filter by namespace (20). v5 errors return an error message and details, and 402 for an empty balance and 401 for a revoked key are documented, with no machine-readable error codes (10 of 20). Every MCP tool carries readOnlyHint, destructiveHint and idempotentHint annotations (in the source since 30 July 2026, missed on 1 October), forget is a soft delete with a dry run, and the API has no idempotency keys (16 of 20). TypeScript and Python SDKs, and an add needs only content (15). 15 + 20 + 10 + 16 + 15 = 76.
Score by category
| Category | Weight | Honcho | Supermemory API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 55 | Supermemory API + MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 88 | Supermemory API + MCP +4 |
| Agent ergonomics | 13% | 71 | 76 | Supermemory API + MCP +5 |
| Security & auth | 14% | 52 | 64 | Supermemory API + MCP +12 |
| Payments & pricing | 10% | 83 | 45 | Honcho +38 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 85 | Supermemory API + MCP +2 |
| Transparency & trust | 7% | 69 | 52 | Honcho +17 |
| Negative events | ≤15 | -6 | -5 | |
| Total | B 62/100 | C 61.5/100 |
Facts side by side
| Fact | Honcho | Supermemory API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Plastic Labs | Supermemory |
| Hosted endpoint | https://api.honcho.dev/v3 | https://api.supermemory.ai |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | yes, from $0.001/call | no |
| Licence | AGPL-3.0 | MIT |
| Tools exposed | 40 | 17 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | io.github.plastic-labs/honcho | not listed |
| Last release | 2026-10-29 | 2026-10-26 |
| Terms last updated | no date given | 2025-06-02 |
| Privacy policy last updated | 2025-04-24 | 2026-09-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| 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 | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Supermemory API + MCP higher, the other way from the total score.
| Reviewer | Honcho | Supermemory API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 3/5 An MCP tool list that arrives only on connect | 4/5 A who_am_i tool and a short list of errors |
| WardenSecurity auditor | 3/5 Keys per peer, and a tool list you can't read first | 3/5 Read-only spaces, and an intake for any web page |
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.
Supermemory API + MCP
Scoped keys limited to namespaces with expiry, per-unit prices without a login, a v5 OpenAPI and annotated MCP tools. No rate limits or 429 guidance are published, the terms name no company, and two described flaws were fixed in August and October without an advisory.
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
Supermemory API + MCP
- Use one stable namespace per user and a stable document ID per session; reusing the ID appends
- Poll the document until
statusisdonebefore searching for what you just added - Treat a 402 on search or profile as out of credit, not as a bug
- Start new integrations on v5 (namespace in the path); v3 and v4 are legacy
- Call who_am_i on the MCP to see which spaces you can write to before adding
Questions
Which is better for AI agents, Honcho or Supermemory API + MCP?
Honcho and Supermemory API + MCP score within a point of each other on agent readiness, 62 (B) and 61.5 (C). Supermemory API + MCP leads on reliability, agent ergonomics and security & auth.
Do Honcho and Supermemory API + MCP need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Honcho per call over x402, with no account.
Can an agent call Honcho and Supermemory API + MCP without installing anything?
Yes. Honcho has a hosted endpoint at https://api.honcho.dev/v3 and Supermemory API + MCP at https://api.supermemory.ai.
Are Honcho and Supermemory API + MCP open source?
Yes. Honcho is open source (AGPL-3.0). Supermemory API + MCP is open source (MIT).
Other comparisons with Honcho or Supermemory API + MCP
- Amazon Bedrock AgentCore Memory vs Honcho
- Amazon Bedrock AgentCore Memory vs Supermemory API + MCP
- Basic Memory vs Honcho
- Basic Memory vs Supermemory API + MCP
- Beacon vs Honcho
- Beacon vs Supermemory API + MCP
- claude-mem vs Honcho
- claude-mem vs Supermemory API + MCP
- Cognee vs Honcho
- Cognee vs Supermemory API + MCP
- EverOS vs Honcho
- EverOS vs Supermemory API + MCP
- Agent Platform Memory Bank vs Honcho
- Agent Platform Memory Bank vs Supermemory API + MCP
- Graphiti vs Honcho
- Graphiti vs Supermemory API + MCP
- Hindsight vs Honcho
- Hindsight vs Supermemory API + MCP
- Honcho vs Hy Memory
- Honcho vs LangMem
- Honcho vs LocalGhost
- Honcho vs Mem0 Platform + MCP
- Honcho vs MemMachine
- Honcho vs Memori
- Honcho vs Memory (MCP reference server)
- Honcho vs MemPalace
- Honcho vs past.dev
- Honcho vs TencentDB Agent Memory
- Honcho vs Tokenrip
- Honcho vs Zep
- Hy Memory vs Supermemory API + MCP
- LangMem vs Supermemory API + MCP
- LocalGhost vs Supermemory API + MCP
- Mem0 Platform + MCP vs Supermemory API + MCP
- MemMachine vs Supermemory API + MCP
- Memori vs Supermemory API + MCP
- Memory (MCP reference server) vs Supermemory API + MCP
- MemPalace vs Supermemory API + MCP
- past.dev vs Supermemory API + MCP
- Supermemory API + MCP vs TencentDB Agent Memory
- Supermemory API + MCP vs Tokenrip
- Supermemory API + MCP vs Zep
- AI Memory vs Honcho
- AI Memory vs Supermemory API + MCP
- Context Mode Engine vs Honcho
- Context Mode Engine vs Supermemory API + MCP
- Graphicle vs Honcho
- Graphicle vs Supermemory API + MCP
Machine-readable
- This page as Markdown
/compare/honcho-vs-supermemory.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/honcho.json·/api/v1/tools/supermemory.json - From a terminal
anchor compare honcho supermemory(the CLI) - Over MCP
compare_tools {"a": "honcho", "b": "supermemory"}at/mcp, no key