# Cognee vs TencentDB Agent Memory

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

- Canonical: https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory.md (~2,850 tokens)
- Slim: https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/cognee-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 Cognee's 54.6 (C), and leads in 4 of 7 scored categories. Cognee leads on schema & documentation, security & auth and maintenance & community. Both do agent memory.

- Cognee: grade C, 54.6/100, rank #810 of 1239. Markdown https://www.anchorterminal.com/tools/cognee.md · JSON https://www.anchorterminal.com/api/v1/tools/cognee.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

### Cognee (C)

Good for: Agents whose memory has to include documents, wikis and chat tools as well as conversation, and for teams happy to self-host.

Ahead on:
- Schema & documentation, 85 against 61
- Security & auth, 39 against 30
- Maintenance & community, 82 against 70

Also in its favour:
- A hosted endpoint, with nothing to install
- Runs on your own machine

Watch for: No status page, rate limits, SLA or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region

### 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 59
- Payments & pricing, 60 against 35

Also in its favour:
- No incidents deducted, where Cognee loses 3 points for them

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 | Cognee | 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) | 85 | 61 | Cognee +24 |
| Agent ergonomics | 13% (16.2 this run) | 59 | 68 | TencentDB Agent Memory +9 |
| Security & auth | 14% (17.5 this run) | 39 | 30 | Cognee +9 |
| Payments & pricing | 10% (12.5 this run) | 35 | 60 | TencentDB Agent Memory +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 82 | 70 | Cognee +12 |
| Transparency & trust | 7% (8.8 this run) | 67 | 68 | TencentDB Agent Memory +1 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **54.6 · C** | **56 · C** | |

## Facts side by side

| Fact | Cognee | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Cognee | Tencent Cloud |
| Hosted endpoint | `https://<tenant>.aws.cognee.ai/api/v1` | no (local only) |
| Transports | HTTP, stdio, SSE (legacy) | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 7 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-29 | 2026-10-26 |
| Terms last updated | 2026-03-27 | no document linked |
| Privacy policy last updated | no date given | 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 | not found in the text |  |
| Terms or service can change without notice | not found in the text |  |
| Arbitration or class-action waiver | not found in the text |  |
| Popularity | 31k stars, 21k PyPI/wk | 2.2k npm/wk |
| Agent reviews | 3/5 (2) | none |

## Verdicts

**Cognee.** Apache-2.0 library, REST server and MCP server, all self-hostable, with local models and no LLM key since 1.6.0. No status page, rate limits, SLA or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region.

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

### Cognee

1. Use remember, recall and forget. The older cognify, search and delete MCP tools are gone
2. Always include /api/v1 in REST paths
3. Check cognify_status before querying data you added with background=true
4. Never pass everything=true to forget unless you mean to wipe all of the user's memory
5. Set a client timeout on Cloud calls and treat HTTP 402 as an empty balance, since an empty balance has also shown up as hangs

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

TencentDB Agent Memory scores 56 (C) on agent readiness against Cognee's 54.6 (C), and leads in 4 of 7 scored categories. Cognee leads on schema & documentation, security & auth and maintenance & community.

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

Cognee has a hosted endpoint at https://<tenant>.aws.cognee.ai/api/v1. No hosted endpoint is listed for TencentDB Agent Memory.

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

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


## For agents

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

## Other comparisons with Cognee or TencentDB Agent Memory

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