# Honcho vs Supermemory API + MCP

> Honcho has a score of 64.2 (B) against Supermemory API + MCP's 63.6 (B). Both do memory store. The largest gap is payments & pricing, 50 points. Honcho accepts x402. Supermemory API + MCP doesn't. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/honcho-vs-supermemory
- Markdown: https://www.anchorterminal.com/compare/honcho-vs-supermemory.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/compare/honcho-vs-supermemory.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/honcho-vs-supermemory.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

Honcho has a score of 64.2 (B) against Supermemory API + MCP's 63.6 (B). Both do memory store. The largest gap is payments & pricing, 50 points. Honcho accepts x402. Supermemory API + MCP doesn't.

- Honcho: grade B, 64.2/100, rank #188 of 452. Markdown https://www.anchorterminal.com/tools/honcho.md · JSON https://www.anchorterminal.com/api/v1/tools/honcho.json
- Supermemory API + MCP: grade B, 63.6/100, rank #201 of 452. Markdown https://www.anchorterminal.com/tools/supermemory.md · JSON https://www.anchorterminal.com/api/v1/tools/supermemory.json

## Which one, for what

Pick Honcho for payments & pricing (+50), transparency & trust (+20).

Pick Supermemory API + MCP for reliability (+15), schema & documentation (+6), agent ergonomics (+8), security & auth (+6), maintenance & community (+12).

## Score by category

| Category | Weight | Honcho | Supermemory API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 65 | Supermemory API + MCP +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 85 | Supermemory API + MCP +6 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 73 | Supermemory API + MCP +8 |
| Security & auth | 14% (17.5 this run) | 48 | 54 | Supermemory API + MCP +6 |
| Payments & pricing | 10% (12.5 this run) | 80 | 30 | Honcho +50 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 85 | Supermemory API + MCP +12 |
| Transparency & trust | 7% (8.8 this run) | 69 | 49 | Honcho +20 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **64.2 · B** | **63.6 · B** | |

## 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 | none | 8 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.plastic-labs/honcho` | not listed |
| Last release | 2026-09-24 | 2026-09-21 |
| Popularity | 7.4k stars, 18k npm/wk | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |

## Verdicts

**Honcho.** Pay per call over x402 or MPP at agentcash.honcho.dev, with free read endpoints. No published rate limits, 429 guidance or SLA.

**Supermemory API + MCP.** 8-tool hosted MCP with OAuth and per-space read or write permission. No legal entity named in the terms or privacy policy.

## Before you call either

### Honcho

1. Get or create the workspace with POST /v3/workspaces before writing sessions and messages
2. Batch up to 100 messages per request, each under 25,000 characters
3. Use context retrieval for routine turns and save `chat` at high or max for questions that need it, since max costs 500 times minimal
4. Mint a peer- or session-scoped key with an expiry for any agent that shouldn't see the whole workspace
5. Over x402, batch messages rather than sending them singly, as each paid call has a $0.001 floor

### Supermemory API + MCP

1. Use one stable `containerTag` per user and a `customId` per session
2. Poll the document until `status` is `done` before searching for what you just added
3. Treat a 402 on search or profile as out of credit, not as a bug
4. Run the prompt-based mass forget with `dryRun` first
5. Call who_am_i on the MCP to see which spaces you can write to before adding

## Other comparisons with Honcho or Supermemory API + MCP

- [Cognee vs Honcho](https://www.anchorterminal.com/compare/cognee-vs-honcho.md)
- [Cognee vs Supermemory API + MCP](https://www.anchorterminal.com/compare/cognee-vs-supermemory.md)
- [Graphiti vs Honcho](https://www.anchorterminal.com/compare/graphiti-vs-honcho.md)
- [Graphiti vs Supermemory API + MCP](https://www.anchorterminal.com/compare/graphiti-vs-supermemory.md)
- [Hindsight vs Honcho](https://www.anchorterminal.com/compare/hindsight-vs-honcho.md)
- [Hindsight vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hindsight-vs-supermemory.md)
- [Honcho vs LocalGhost](https://www.anchorterminal.com/compare/honcho-vs-localghost.md)
- [Honcho vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/honcho-vs-mem0.md)
- [Honcho vs Zep](https://www.anchorterminal.com/compare/honcho-vs-zep.md)
- [LocalGhost vs Supermemory API + MCP](https://www.anchorterminal.com/compare/localghost-vs-supermemory.md)
- [Mem0 Platform + MCP vs Supermemory API + MCP](https://www.anchorterminal.com/compare/mem0-vs-supermemory.md)
- [Supermemory API + MCP vs Zep](https://www.anchorterminal.com/compare/supermemory-vs-zep.md)