# Graphiti vs Honcho

> Honcho has a score of 64.2 (B) against Graphiti's 53.3 (D). Both do memory store. The largest gap is security & auth, 25 points. Honcho accepts x402. Graphiti doesn't. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/graphiti-vs-honcho
- Markdown: https://www.anchorterminal.com/compare/graphiti-vs-honcho.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/compare/graphiti-vs-honcho.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/graphiti-vs-honcho.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 Graphiti's 53.3 (D). Both do memory store. The largest gap is security & auth, 25 points. Honcho accepts x402. Graphiti doesn't.

- Graphiti: grade D, 53.3/100, rank #333 of 452. Markdown https://www.anchorterminal.com/tools/graphiti.md · JSON https://www.anchorterminal.com/api/v1/tools/graphiti.json
- 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

## Which one, for what

Pick Graphiti for nothing in particular (no category where it leads by five points or more).

Pick Honcho for schema & documentation (+8), agent ergonomics (+14), security & auth (+25), payments & pricing (+20), maintenance & community (+8).

## Score by category

| Category | Weight | Graphiti | Honcho | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 50 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 71 | 79 | Honcho +8 |
| Agent ergonomics | 13% (16.2 this run) | 51 | 65 | Honcho +14 |
| Security & auth | 14% (17.5 this run) | 23 | 48 | Honcho +25 |
| Payments & pricing | 10% (12.5 this run) | 60 | 80 | Honcho +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 65 | 73 | Honcho +8 |
| Transparency & trust | 7% (8.8 this run) | 71 | 69 | Graphiti +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.3 · D** | **64.2 · B** | |

## Facts side by side

| Fact | Graphiti | Honcho |
| --- | --- | --- |
| Kind | Agent framework | HTTP API |
| Vendor | Zep | Plastic Labs |
| Hosted endpoint | no (local only) | `https://api.honcho.dev/v3` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Pay per use |
| x402 | no | yes, from $0.001/call |
| Licence | Apache-2.0 | AGPL-3.0 |
| Tools exposed | 13 | none |
| 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 | not listed | `io.github.plastic-labs/honcho` |
| Last release | 2026-09-08 | 2026-09-24 |
| Popularity | 29k stars, 151k PyPI/wk | 7.4k stars, 18k npm/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |

## Verdicts

**Graphiti.** Apache-2.0, with FalkorDB, Neo4j or Amazon Neptune as the store. Every add runs LLM extraction, so ingestion costs tokens and time.

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

## Before you call either

### Graphiti

1. Set OPENAI_API_KEY (or another provider's key) and MODEL_NAME before starting the MCP server
2. Use search_memory_facts for facts and search_nodes for entities instead of reading whole episodes
3. Never call clear_graph to fix one fact. Use delete_episode or delete_entity_edge
4. Pass group_ids on every search and add so one user's graph doesn't leak into another's
5. Call get_status to check the database connection before a long ingest

### 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

## Other comparisons with Graphiti or Honcho

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