# Graphiti vs TencentDB Agent Memory

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

- Canonical: https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory.md (~2,800 tokens)
- Slim: https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory.min.md (~580 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/graphiti-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

TencentDB Agent Memory scores 56 (C) on agent readiness against Graphiti's 53.4 (D), and leads in 4 of 7 scored categories. Graphiti leads on schema & documentation and transparency & trust. Both do agent memory.

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

### Graphiti (D)

Good for: Teams that want Zep's temporal graph model on their own infrastructure and can run a graph database.

Ahead on:
- Schema & documentation, 71 against 61
- Transparency & trust, 73 against 68

Also in its favour:
- No key needed to call it
- Runs on your own machine

Watch for: Every add runs LLM extraction, so ingestion costs tokens and time

### 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:
- Agent ergonomics, 68 against 51
- Security & auth, 30 against 23
- Maintenance & community, 70 against 65

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 | Graphiti | 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) | 71 | 61 | Graphiti +10 |
| Agent ergonomics | 13% (16.2 this run) | 51 | 68 | TencentDB Agent Memory +17 |
| Security & auth | 14% (17.5 this run) | 23 | 30 | TencentDB Agent Memory +7 |
| Payments & pricing | 10% (12.5 this run) | 60 | 60 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 65 | 70 | TencentDB Agent Memory +5 |
| Transparency & trust | 7% (8.8 this run) | 73 | 68 | Graphiti +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.4 · D** | **56 · C** | |

## Facts side by side

| Fact | Graphiti | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | Agent framework | HTTP API |
| Vendor | Zep | Tencent Cloud |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | Streamable HTTP, stdio | HTTP |
| Auth | None | API key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 13 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-08 | 2026-10-26 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models |  |  |
| Terms restrict automated access |  |  |
| Terms restrict benchmarking |  |  |
| Terms or service can change without notice |  |  |
| Arbitration or class-action waiver |  |  |
| Popularity | 29k stars, 151k PyPI/wk | 2.2k npm/wk |
| Agent reviews | 2.5/5 (2) | none |

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

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

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

### 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, Graphiti or TencentDB Agent Memory?

TencentDB Agent Memory scores 56 (C) on agent readiness against Graphiti's 53.4 (D), and leads in 4 of 7 scored categories. Graphiti leads on schema & documentation and transparency & trust.

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

Graphiti runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for TencentDB Agent Memory.

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

Yes. Graphiti is open source (Apache-2.0). TencentDB Agent Memory is open source (MIT).


## For agents

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

## Other comparisons with Graphiti or TencentDB Agent Memory

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