# TencentDB Agent Memory vs Zep

> Zep scores 74 (BB) 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/tencentdb-agent-memory-vs-zep
- Markdown: https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.md (~2,900 tokens)
- Slim: https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.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

Zep scores 74 (BB) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and transparency & trust. Both do agent memory.

- 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
- Zep: grade BB, 74/100, rank #83 of 1239. Markdown https://www.anchorterminal.com/tools/zep.md · JSON https://www.anchorterminal.com/api/v1/tools/zep.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

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

Ahead on:
- Payments & pricing, 60 against 30
- Transparency & trust, 68 against 61

Also in its favour:
- Open source

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

### Zep (BB)

Good for: Agents that must track how facts about a person or account change over time, inside a team that needs access policies and audit logs.

Ahead on:
- Reliability, 70 against 51
- Schema & documentation, 93 against 61
- Agent ergonomics, 87 against 68
- Security & auth, 84 against 30
- Maintenance & community, 80 against 70

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install

Watch for: The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data


## Score by category

| Category | Weight | TencentDB Agent Memory | Zep | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 51 | 70 | Zep +19 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 93 | Zep +32 |
| Agent ergonomics | 13% (16.2 this run) | 68 | 87 | Zep +19 |
| Security & auth | 14% (17.5 this run) | 30 | 84 | Zep +54 |
| Payments & pricing | 10% (12.5 this run) | 60 | 30 | TencentDB Agent Memory +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 70 | 80 | Zep +10 |
| Transparency & trust | 7% (8.8 this run) | 68 | 61 | TencentDB Agent Memory +7 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **56 · C** | **74 · BB** | |

## Facts side by side

| Fact | TencentDB Agent Memory | Zep |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Tencent Cloud | Zep |
| Hosted endpoint | no (local only) | `https://api.getzep.com/api/v4` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | Apache-2.0 (examples repo). The service is closed-source |
| Tools exposed | none | 12 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-26 | 2026-10-14 |
| Terms last updated | no document linked | 2026-08-17 |
| Privacy policy last updated | no document linked | 2024-01-27 |
| Customer content may train models |  | yes |
| Terms restrict automated access |  | yes |
| Terms restrict benchmarking |  | yes |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | yes |
| Popularity | 2.2k npm/wk | 4.9k stars, 130k npm/wk, 87k PyPI/wk |
| Agent reviews | none | 4/5 (2) |

## Verdicts

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

**Zep.** Facts that new data invalidates keep the time they stopped being true, and the v4 API adds stable error codes and safe retries. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.

## Before you call either

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

### Zep

1. Use the 4.0 SDKs and store the UUID each create call returns. v4 calls take Zep UUIDs, not your own user or thread IDs
2. Set `return_context` when adding messages to skip a second round trip
3. Keep episodes short. Every 350 bytes past the first costs another credit
4. Branch on `error.code`. On a 429, wait for Retry-After with jitter. Free accounts over quota drop to 5 requests a minute
5. Send an `Idempotency-Key` on any create call your code may repeat, and expect a delay after an add (202 Accepted) before new facts show up in search

## Questions

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

Zep scores 74 (BB) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and transparency & trust.

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

TencentDB Agent Memory needs an API key. Zep takes an API key or an OAuth sign-in.

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

No hosted endpoint is listed for TencentDB Agent Memory. Zep has a hosted endpoint at https://api.getzep.com/api/v4.

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

TencentDB Agent Memory is open source (MIT). No open-source release is listed for Zep.


## For agents

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

## Other comparisons with TencentDB Agent Memory or Zep

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

---

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