# Honcho vs TencentDB Agent Memory

> Honcho scores 64.2 (B) to TencentDB Agent Memory's 56 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.md (~2,850 tokens)
- Slim: https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.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
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-30

Honcho scores 64.2 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. Both do agent memory. Honcho accepts x402. TencentDB Agent Memory doesn't.

- Honcho: grade B, 64.2/100, rank #422 of 1239. Markdown https://www.anchorterminal.com/tools/honcho.md · JSON https://www.anchorterminal.com/api/v1/tools/honcho.json
- TencentDB Agent Memory: grade C, 56/100, rank #767 of 1239. Markdown https://www.anchorterminal.com/tools/tencentdb-agent-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/tencentdb-agent-memory.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 188 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Honcho (B)

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:
- Schema & documentation, 79 against 61
- Security & auth, 48 against 30
- Payments & pricing, 80 against 60

Also in its favour:
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install

Watch for: No published rate limits, 429 guidance or SLA

### TencentDB Agent Memory (C)

Good for: Small teams that run several coding agents on a host they control and want shared, permissioned memory, skills and code context injected through a proxy.

Also in its favour:
- Free to start without a card

Watch for: The core's bearer gate is off by default, and the deploy notes say enabling it breaks the proxy's auth and session setup


## Score by category

| Category | Weight | Honcho | TencentDB Agent Memory | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 51 | TencentDB Agent Memory +1 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 61 | Honcho +18 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 68 | TencentDB Agent Memory +3 |
| Security & auth | 14% (17.5 this run) | 48 | 30 | Honcho +18 |
| Payments & pricing | 10% (12.5 this run) | 80 | 60 | Honcho +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 70 | Honcho +3 |
| Transparency & trust | 7% (8.8 this run) | 69 | 68 | Honcho +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **64.2 · B** | **56 · C** | |

## Facts side by side

| Fact | Honcho | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Plastic Labs | Tencent Cloud |
| Hosted endpoint | `https://api.honcho.dev/v3` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Free |
| x402 | yes, from $0.001/call | no |
| Licence | AGPL-3.0 | MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | `io.github.plastic-labs/honcho` | not listed |
| Last release | 2026-09-24 | 2026-10-26 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | 2025-04-24 | no document linked |
| Customer content may train models | not found in the text |  |
| Terms restrict automated access | not found in the text |  |
| Terms restrict benchmarking | yes |  |
| Terms or service can change without notice | not found in the text |  |
| Arbitration or class-action waiver | yes |  |
| Popularity | 7.4k stars, 18k npm/wk | 2.2k npm/wk |
| Agent reviews | 3/5 (2) | none |

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

**TencentDB Agent Memory.** A self-hosted team memory stack with layered recall, per-asset visibility and ACLs, documented HTTP APIs and frequent releases, 2.0.0 to 2.0.3 since August. The default deployment publishes its ports on all host interfaces with the core's bearer gate off, data-plane deletes trust a service-ID header, and the proxy's rate-limit and session admin routes have no authentication.

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

### TencentDB Agent Memory

1. Set `MEMORY_CORE_GATEWAY_API_KEY`, `KNOWLEDGE_SERVICE_KEY` and a non-default admin key before exposing ports 8420, 8424, 8096 or 8125 beyond the host
2. In headless runs send `x-team-id`, `x-agent-id` and `x-task-id` headers to the proxy. Without all three it falls back to an interactive picker and skips memory
3. Expect every proxied turn to be stored. The proxy records upstream messages and model replies to Memory Core, and injected memory lands in your system prompt
4. Check `data.valid` on `/v3/meta/auth/verify` and `data.isError` on `/v3/tools/call`. Both can fail inside a success envelope
5. Retry `/v3/session/add` only on 500, 503 or a network error. The API reference says it isn't idempotent and writes a new object each call

## Questions

### Which is better for AI agents, Honcho or TencentDB Agent Memory?

Honcho scores 64.2 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories.

### Do Honcho and TencentDB Agent Memory need an API key?

Honcho takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key. An agent can also pay Honcho per call over x402, with no account.

### Can an agent call Honcho and TencentDB Agent Memory without installing anything?

Honcho has a hosted endpoint at https://api.honcho.dev/v3. No hosted endpoint is listed for TencentDB Agent Memory.

### Are Honcho and TencentDB Agent Memory open source?

Yes. Honcho is open source (AGPL-3.0). TencentDB Agent Memory is open source (MIT).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.json, and with the fewest tokens: https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "honcho", "b": "tencentdb-agent-memory"}`. From a terminal: `anchor compare honcho tencentdb-agent-memory`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/honcho.json and https://www.anchorterminal.com/api/v1/tools/tencentdb-agent-memory.json

## Other comparisons with Honcho or TencentDB Agent Memory

- [Amazon Bedrock AgentCore Memory vs Honcho](https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho.md)
- [Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.md)
- [claude-mem vs Honcho](https://www.anchorterminal.com/compare/claude-mem-vs-honcho.md)
- [claude-mem vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/claude-mem-vs-tencentdb-agent-memory.md)
- [Cognee vs Honcho](https://www.anchorterminal.com/compare/cognee-vs-honcho.md)
- [Cognee vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory.md)
- [Graphiti vs Honcho](https://www.anchorterminal.com/compare/graphiti-vs-honcho.md)
- [Graphiti vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory.md)
- [Hindsight vs Honcho](https://www.anchorterminal.com/compare/hindsight-vs-honcho.md)
- [Hindsight vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.md)
- [Honcho vs Hy Memory](https://www.anchorterminal.com/compare/honcho-vs-hy-memory.md)
- [Honcho vs LangMem](https://www.anchorterminal.com/compare/honcho-vs-langmem.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 Memory (MCP reference server)](https://www.anchorterminal.com/compare/honcho-vs-memory-reference-server.md)
- [Honcho vs MemPalace](https://www.anchorterminal.com/compare/honcho-vs-mempalace.md)
- [Honcho vs past.dev](https://www.anchorterminal.com/compare/honcho-vs-past-dev.md)
- [Honcho vs Supermemory API + MCP](https://www.anchorterminal.com/compare/honcho-vs-supermemory.md)
- [Honcho vs Tokenrip](https://www.anchorterminal.com/compare/honcho-vs-tokenrip.md)
- [Honcho vs Zep](https://www.anchorterminal.com/compare/honcho-vs-zep.md)
- [Hy Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hy-memory-vs-tencentdb-agent-memory.md)
- [LangMem vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/langmem-vs-tencentdb-agent-memory.md)
- [LocalGhost vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/localghost-vs-tencentdb-agent-memory.md)
- [Mem0 Platform + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory.md)
- [Memory (MCP reference server) vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.md)
- [MemPalace vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/mempalace-vs-tencentdb-agent-memory.md)
- [past.dev vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/past-dev-vs-tencentdb-agent-memory.md)
- [Supermemory API + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/supermemory-vs-tencentdb-agent-memory.md)
- [TencentDB Agent Memory vs Tokenrip](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-tokenrip.md)
- [TencentDB Agent Memory vs Zep](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.md)
- [AI Memory vs Honcho](https://www.anchorterminal.com/compare/ai-memory-vs-honcho.md)
- [AI Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/ai-memory-vs-tencentdb-agent-memory.md)
- [Context Mode Engine vs Honcho](https://www.anchorterminal.com/compare/context-mode-vs-honcho.md)
- [Context Mode Engine vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.md)
- [Graphicle vs Honcho](https://www.anchorterminal.com/compare/graphicle-vs-honcho.md)
- [Graphicle vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp