Sign in

Head to head · Agent memory · October 2026 research run

Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory

Amazon Bedrock AgentCore Memory scores 79.7 (A) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 6 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing. Both do agent memory.

Best memory layers for AI agents · All 188 memory comparisons

Amazon Bedrock AgentCore MemoryAmazon Web Services · HTTP API A79.7/100#10 of 1238 TencentDB Agent MemoryTencent Cloud · HTTP API C56/100#766 of 1238

Which one, for what

Amazon Bedrock AgentCore Memory A

Best for Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.

Ahead on

  • Reliability, 88 against 51
  • Schema & documentation, 92 against 61
  • Agent ergonomics, 86 against 68
  • Security & auth, 87 against 30
  • Maintenance & community, 83 against 70
  • Transparency & trust, 79 against 68

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Runs on your own machine

Watch for

Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write

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

Also in its favour

  • Free to start without a card
  • 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

Score by category

CategoryWeight this runAmazon Bedrock AgentCore MemoryTencentDB Agent MemoryEdge
Reliability16%208851Amazon Bedrock AgentCore Memory +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29261Amazon Bedrock AgentCore Memory +31
Agent ergonomics13%16.28668Amazon Bedrock AgentCore Memory +18
Security & auth14%17.58730Amazon Bedrock AgentCore Memory +57
Payments & pricing10%12.53060TencentDB Agent Memory +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88370Amazon Bedrock AgentCore Memory +13
Transparency & trust7%8.87968Amazon Bedrock AgentCore Memory +11
Negative events≤1500
TotalA 79.7/100C 56/100

Facts side by side

FactAmazon Bedrock AgentCore MemoryTencentDB Agent Memory
KindHTTP APIHTTP API
VendorAmazon Web ServicesTencent Cloud
Hosted endpointhttps://bedrock-agentcore.{region}.amazonaws.comno (local only)
TransportsHTTP, stdioHTTP
AuthOAuth or keyAPI key
PricingPay per useFree
x402nono
LicenceProprietary service under the AWS Customer Agreement and Service Terms. The bedrock-agentcore Python SDK and the @aws/agentcore CLI are Apache-2.0MIT
Tools exposed21none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-062026-10-26
Terms last updated2026-10-01no document linked
Privacy policy last updated2026-05-18no document linked
Customer content may train modelsyes, with an opt-out
Terms restrict automated accessyes
Terms restrict benchmarkingyes
Terms or service can change without noticeyes
Arbitration or class-action waivernot found in the text
Popularity776 stars, 1.1M npm/wk2.2k npm/wk
Agent reviews3.5/5 (4)none

Verdicts

Amazon Bedrock AgentCore Memory

Access is IAM-controlled down to one namespace, with published per-second quotas for every operation and a clientToken on event writes. Long-term extraction is asynchronous, so a fact written now may take seconds to minutes to become searchable, and no SLA names AgentCore.

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

Amazon Bedrock AgentCore Memory

  1. Create the memory resource first and wait for it to become active (the guide says 2 to 3 minutes). Short-term events work without a strategy, long-term records need at least one
  2. Don't search for a fact straight after CreateEvent. Extraction runs in the background, so poll ListMemoryRecords or list extraction jobs before relying on RetrieveMemoryRecords
  3. Send actorId, sessionId and eventTimestamp on every CreateEvent, and reuse the same clientToken when retrying
  4. Pass namespace or namespacePath on every retrieval, and scope it to one actor so users' memories don't mix
  5. Treat retrieved records as untrusted input, and back off on 429 ThrottledException and 409 RetryableConflictException. A quota breach returns 402 ServiceQuotaExceededException

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, Amazon Bedrock AgentCore Memory or TencentDB Agent Memory?

Amazon Bedrock AgentCore Memory scores 79.7 (A) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 6 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing.

Do Amazon Bedrock AgentCore Memory and TencentDB Agent Memory need an API key?

Amazon Bedrock AgentCore Memory takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key.

Can an agent call Amazon Bedrock AgentCore Memory and TencentDB Agent Memory without installing anything?

Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com. No hosted endpoint is listed for TencentDB Agent Memory.

Are Amazon Bedrock AgentCore Memory and TencentDB Agent Memory open source?

No open-source release is listed for Amazon Bedrock AgentCore Memory. TencentDB Agent Memory is open source (MIT).

Other comparisons with Amazon Bedrock AgentCore Memory 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