Sign in

Head to head · Agent memory · October 2026 research run

Cognee vs 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. Both do agent memory.

Best memory layers for AI agents · All 188 memory comparisons

CogneeCognee · Platform C54.6/100#809 of 1238 TencentDB Agent MemoryTencent Cloud · HTTP API C56/100#766 of 1238

Which one, for what

Cognee C

Best 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

Best 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

CategoryWeight this runCogneeTencentDB Agent MemoryEdge
Reliability16%205051TencentDB Agent Memory +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28561Cognee +24
Agent ergonomics13%16.25968TencentDB Agent Memory +9
Security & auth14%17.53930Cognee +9
Payments & pricing10%12.53560TencentDB Agent Memory +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88270Cognee +12
Transparency & trust7%8.86768TencentDB Agent Memory +1
Negative events≤15-30
TotalC 54.6/100C 56/100

Facts side by side

FactCogneeTencentDB Agent Memory
KindPlatformHTTP API
VendorCogneeTencent Cloud
Hosted endpointhttps://<tenant>.aws.cognee.ai/api/v1no (local only)
TransportsHTTP, stdio, SSE (legacy)HTTP
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
LicenceApache-2.0MIT
Tools exposed7none
Read-only variant documentednono
llms.txtyesno
Last release2026-09-292026-10-26
Terms last updated2026-03-27no document linked
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity31k stars, 21k PyPI/wk2.2k npm/wk
Agent reviews3/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).

Other comparisons with Cognee or TencentDB Agent Memory

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report