Head to head · Agent memory · October 2026 research run

Supermemory API + MCP vs TencentDB Agent Memory

Supermemory API + MCP scores 63.8 (B) 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.

Best memory layers for AI agents · All 188 memory comparisons

Which one, for what

Supermemory API + MCP B

Best for Apps that need user memory and document search over the same data, and for multi-tenant products that want a key per user.

Ahead on

  • Reliability, 65 against 51
  • Schema & documentation, 85 against 61
  • Agent ergonomics, 73 against 68
  • Security & auth, 54 against 30
  • Maintenance & community, 85 against 70

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No legal entity named in the terms or privacy policy

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

  • Payments & pricing, 60 against 30
  • Transparency & trust, 68 against 51

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

CategoryWeight this runSupermemory API + MCPTencentDB Agent MemoryEdge
Reliability16%206551Supermemory API + MCP +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28561Supermemory API + MCP +24
Agent ergonomics13%16.27368Supermemory API + MCP +5
Security & auth14%17.55430Supermemory API + MCP +24
Payments & pricing10%12.53060TencentDB Agent Memory +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88570Supermemory API + MCP +15
Transparency & trust7%8.85168TencentDB Agent Memory +17
Negative events≤1500
TotalB 63.8/100C 56/100

Facts side by side

FactSupermemory API + MCPTencentDB Agent Memory
KindHTTP APIHTTP API
VendorSupermemoryTencent Cloud
Hosted endpointhttps://api.supermemory.aino (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
LicenceMITMIT
Tools exposed8none
Read-only variant documentednono
llms.txtyesno
Last release2026-09-212026-10-26
Terms last updated2025-06-02no document linked
Privacy policy last updated2026-09-29no 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 waiveryes
Popularity31k stars, 121k npm/wk, 45k PyPI/wk2.2k npm/wk
Agent reviews3.5/5 (2)none

Verdicts

Supermemory API + MCP

8-tool hosted MCP with OAuth and per-space read or write permission. No legal entity named in the terms or privacy policy.

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

Supermemory API + MCP

  1. Use one stable containerTag per user and a customId per session
  2. Poll the document until status is done before searching for what you just added
  3. Treat a 402 on search or profile as out of credit, not as a bug
  4. Run the prompt-based mass forget with dryRun first
  5. Call who_am_i on the MCP to see which spaces you can write to before adding

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, Supermemory API + MCP or TencentDB Agent Memory?

Supermemory API + MCP scores 63.8 (B) 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 Supermemory API + MCP and TencentDB Agent Memory need an API key?

Supermemory API + MCP takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key.

Can an agent call Supermemory API + MCP and TencentDB Agent Memory without installing anything?

Supermemory API + MCP has a hosted endpoint at https://api.supermemory.ai. No hosted endpoint is listed for TencentDB Agent Memory.

Are Supermemory API + MCP and TencentDB Agent Memory open source?

Yes. Supermemory API + MCP is open source (MIT). TencentDB Agent Memory is open source (MIT).

Other comparisons with Supermemory API + MCP 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.