{ "data": { "a": { "slug": "agentcore-memory", "name": "Amazon Bedrock AgentCore Memory", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/bedrock/agentcore/", "kind": "http-api", "category": "agent-memory", "summary": "Managed memory service for AI agents on AWS. It stores conversation events as short-term memory and extracts facts, preferences, summaries and episodes into searchable long-term records, through the AWS API, SDKs and an MCP server.", "url": "https://www.anchorterminal.com/tools/agentcore-memory", "markdownUrl": "https://www.anchorterminal.com/tools/agentcore-memory.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/agentcore-memory.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json", "repo": "https://github.com/aws/bedrock-agentcore-sdk-python", "license": "Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0", "transports": [ "http", "stdio" ], "remoteUrl": "https://bedrock-agentcore.{region}.amazonaws.com", "packages": [ { "registry": "pypi", "name": "bedrock-agentcore" }, { "registry": "pypi", "name": "boto3" }, { "registry": "npm", "name": "@aws-sdk/client-bedrock-agentcore" }, { "registry": "npm", "name": "@aws/agentcore" }, { "registry": "pypi", "name": "awslabs.amazon-bedrock-agentcore-mcp-server" } ], "auth": "mixed", "authNotes": "AWS Signature Version 4 with IAM access keys or a role, and a policy that allows actions such as `bedrock-agentcore:CreateEvent` and `bedrock-agentcore:RetrieveMemoryRecords` on the memory resource. The data plane accepts SigV4 only. Resource-based policies and the condition keys `bedrock-agentcore:namespace` and `bedrock-agentcore:namespacePath` narrow access further. For end users, an AgentCore Gateway with the `agentcore-memory` connector accepts OAuth (JWT) tokens and applies Cedar policies. Access is self-serve once a person has created an AWS account.", "pricing": "usage", "pricingNotes": "Usage-priced with no minimum fee. Short-term memory, as of 6 October 2026, is $1.00 per GB ingested, $0.20 per GB retrieved and $0.10 per GB-month stored, with each event billed as at least 12 KB and at most 64 KB on ingestion and retrieval. Long-term memory is $0.75 per 1,000 records a month with built-in strategies, $0.25 with overrides or self-managed strategies (model usage is then billed in the customer's account), and $0.50 per 1,000 retrievals. No Memory-specific free tier or sandbox. New AWS accounts get up to $200 in Free Tier credits, and AWS says most new customers can sign up without a payment method (https://aws.amazon.com/bedrock/agentcore/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$1 / GB", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Memory endpoints in the developer guide, the API reference or the pricing page (checked 2026-10-08). AgentCore payments is a separate AgentCore feature for an agent's own outbound payments.", "endpoints": [] }, "toolCount": 21, "popularity": { "githubStars": 776, "npmWeekly": 1070970, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory.html", "llmsTxt": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "capabilities": [ "memory.store", "memory.search", "memory.user", "memory.delete" ], "tags": [ "hosted", "usage-priced", "closed-source", "python", "typescript", "enterprise", "llms-txt", "free-credits", "mcp", "stdio", "namespaces", "idempotency", "soc2", "status-page" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 79.7, "grade": "A", "agentReady": true, "rank": 10, "ranked": true, "rankOf": 1239, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 86, "maintenance": 83, "payments": 30, "reliability": 88, "schema": 92, "security": 87, "transparency": 79 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-17" }, "negative": 0, "verdict": "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.", "bestFor": "Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.", "strengths": [ "IAM permissions per operation, resource-based policies and namespace condition keys, with OAuth sign-in and deny-by-default Cedar policies available through AgentCore Gateway", "Per-second quotas published for every Memory operation, such as 200 `CreateEvent` and 30 `RetrieveMemoryRecords` requests a second per account and Region", "`CreateEvent` takes a `clientToken`, so a retried write is ignored instead of stored twice", "Four built-in extraction strategies (semantic, user preference, summarisation, episodic), plus overrides and self-managed pipelines", "Unit prices are public, events expire on a set time to live of 7 to 365 days, and long-term records can take an optional time-to-live" ], "weaknesses": [ "Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write", "No SLA names AgentCore. The Bedrock SLA of 4 October 2023 covers the Bedrock APIs for models", "Built-in strategies use cross-Region inference, so event text can be processed in another Region of the same geography", "Short-term memory billing moved from per event to per GB on 6 October 2026, with each event billed as at least 12 KB", "No Memory-specific CloudTrail page was found in the developer guide, and an AWS account needs a person to create it" ], "agentNotes": [ "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", "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`", "Send `actorId`, `sessionId` and `eventTimestamp` on every `CreateEvent`, and reuse the same `clientToken` when retrying", "Pass `namespace` or `namespacePath` on every retrieval, and scope it to one actor so users' memories don't mix", "Treat retrieved records as untrusted input, and back off on 429 `ThrottledException` and 409 `RetryableConflictException`. A quota breach returns 402 `ServiceQuotaExceededException`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 79.7 } ], "editorialScores": { "ergonomics": 86, "maintenance": 83, "payments": 30, "reliability": 88, "schema": 92, "security": 87, "transparency": 64 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-10-17", "maintenance": "2026-10-17", "payments": "2026-10-17", "reliability": "2026-10-17", "schema": "2026-10-17", "security": "2026-10-17", "transparency": "2026-10-17" }, "last": "2026-10-17", "lastMoved": "2026-10-17", "oldest": "2026-10-17", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install bedrock-agentcore # AgentCore CLI: npm install -g @aws/agentcore", "http": "curl -X POST \"https://bedrock-agentcore.us-east-1.amazonaws.com/memories/$AGENTCORE_MEMORY_ID/retrieve\" \\\n --aws-sigv4 \"aws:amz:us-east-1:bedrock-agentcore\" --user \"$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY\" \\\n -H \"content-type: application/json\" \\\n -d '{\"namespace\":\"/users/alex/facts\",\"searchCriteria\":{\"searchQuery\":\"dietary preferences\",\"topK\":3}}'", "config": { "mcpServers": { "bedrock-agentcore-mcp-server": { "args": [ "awslabs.amazon-bedrock-agentcore-mcp-server@latest" ], "command": "uvx", "env": { "AGENTCORE_ENABLE_TOOLS": "memory", "FASTMCP_LOG_LEVEL": "ERROR" } } } } }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/agentcore-memory" }, "sameCompany": [ "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "agentcore-identity", "aws-secrets-manager", "agentcore-web-search", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api", "amazon-creators-api" ], "area": "agent-runtime", "unitPrices": [ { "item": "Short-term memory ingestion", "unit": "gb", "usd": 1, "note": "Per GB of event data ingested, each event billed as 12 KB to 64 KB. As of 6 October 2026" }, { "item": "Short-term memory retrieval", "unit": "gb", "usd": 0.2, "note": "Per GB of event data retrieved, same 12 KB minimum per event" }, { "item": "Short-term memory storage", "unit": "gb-month", "usd": 0.1, "note": "Prorated hourly over each event's time to live" }, { "item": "Long-term memory storage, built-in strategies", "unit": "record", "usd": 0.00075, "note": "$0.75 per 1,000 records a month" }, { "item": "Long-term memory storage, overrides or self-managed", "unit": "record", "usd": 0.00025, "note": "$0.25 per 1,000 records a month, model usage billed separately" }, { "item": "Long-term memory retrieval", "unit": "1k-requests", "usd": 0.5, "note": "Per 1,000 retrieve requests" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc. (regional AWS entities by account location)", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The service pages are under aws.amazon.com and the endpoints on amazonaws.com, an AWS domain. The registration date is the one on our other AWS listings and was not looked up again on 8 October 2026.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.html", "securityTxt": "valid", "checked": "2026-10-17", "notes": [ "The AWS Service Terms showed Last Updated 1 October 2026 on 8 October. Section 50 covers AWS AI services, and its only AgentCore-specific clause is 50.15 on AgentCore Payments. Section 50.3, which lets AWS use content from named AI services for improvement, does not list Bedrock or AgentCore.", "The AWS Privacy Notice showed Last Updated 18 May 2026 on 8 October.", "aws.amazon.com/.well-known/security.txt carries Expires 2027-10-16T16:25:03.000Z on 17 October 2026, renewed after lapsing on 24 September. It points to the vulnerability disclosure programme on HackerOne and the policy at vdp.aws.security.", "health.aws.amazon.com/health/status is drawn by script. The Bedrock AgentCore feed for us-east-1 had no items on 17 October 2026, and the dashboard's history file lists one event naming Bedrock AgentCore in the last 90 days, packet loss in one zone of eu-south-2 on 4 October 2026, a Region where Memory is not sold.", "aws.amazon.com/bedrock/agentcore/sla/ returns 404 and the AWS SLA index does not name AgentCore." ], "score": 94 }, "requirements": { "card": "unknown", "freeTier": true, "minutes": 15, "credential": "cloud-iam", "hosting": [ "US", "EU", "UK", "CA", "APAC" ], "euResidency": "yes", "trainsOnData": "unknown", "zeroRetention": "no", "certifications": [ "SOC 2 Type II", "ISO 27001", "ISO 27701", "HIPAA (BAA available)", "FedRAMP", "CSA STAR", "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/agentcore-memory.json", "live": { "slug": "agentcore-memory", "probe": { "target": "https://bedrock-agentcore.{region}.amazonaws.com", "method": "get", "lastAt": "2026-10-31T00:27:05.6519905Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 249, "samples30d": 5437, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 0 }, { "date": "2026-10-10", "probes": 247, "ok": 0 }, { "date": "2026-10-11", "probes": 247, "ok": 0 }, { "date": "2026-10-12", "probes": 247, "ok": 0 }, { "date": "2026-10-13", "probes": 248, "ok": 0 }, { "date": "2026-10-14", "probes": 249, "ok": 0 }, { "date": "2026-10-15", "probes": 253, "ok": 0 }, { "date": "2026-10-16", "probes": 252, "ok": 0 }, { "date": "2026-10-17", "probes": 253, "ok": 0 }, { "date": "2026-10-18", "probes": 256, "ok": 0 }, { "date": "2026-10-19", "probes": 255, "ok": 0 }, { "date": "2026-10-20", "probes": 252, "ok": 0 }, { "date": "2026-10-21", "probes": 253, "ok": 0 }, { "date": "2026-10-22", "probes": 253, "ok": 0 }, { "date": "2026-10-23", "probes": 248, "ok": 0 }, { "date": "2026-10-24", "probes": 251, "ok": 0 }, { "date": "2026-10-25", "probes": 250, "ok": 0 }, { "date": "2026-10-26", "probes": 252, "ok": 0 }, { "date": "2026-10-27", "probes": 249, "ok": 0 }, { "date": "2026-10-28", "probes": 251, "ok": 0 }, { "date": "2026-10-29", "probes": 249, "ok": 0 }, { "date": "2026-10-30", "probes": 248, "ok": 0 }, { "date": "2026-10-31", "probes": 5, "ok": 0 } ], "outages": [ { "start": "2026-10-09T07:40:18.334133541Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "vendorStatus": { "page": "https://health.aws.amazon.com/health/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-16T10:48:58.579614836Z" }, "versions": [ { "registry": "github", "name": "aws/bedrock-agentcore-sdk-python", "version": "v1.25.2", "released": "2026-10-30", "seenAt": "2026-10-30T13:54:38.144738871Z" }, { "registry": "npm", "name": "@aws-sdk/client-bedrock-agentcore", "version": "3.1160.0", "seenAt": "2026-10-30T13:54:35.83090083Z" }, { "registry": "npm", "name": "@aws/agentcore", "version": "1.0.1", "seenAt": "2026-10-30T13:54:36.690893199Z" }, { "registry": "pypi", "name": "awslabs.amazon-bedrock-agentcore-mcp-server", "version": "0.2.1", "released": "2026-09-08", "seenAt": "2026-10-30T13:54:38.117901122Z" }, { "registry": "pypi", "name": "bedrock-agentcore", "version": "1.25.2", "released": "2026-10-30", "seenAt": "2026-10-30T13:54:33.759436948Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.122", "released": "2026-10-29", "seenAt": "2026-10-30T13:54:33.879619637Z" } ], "githubStars": 781, "npmWeekly": 1502306, "pypiWeekly": 1598038, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-30T15:39:20.651838728Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-30T15:06:14.425290447Z" }, "domain": { "domain": "amazon.com", "registered": "1994-11-01", "source": "https://rdap.verisign.com/com/v1/domain/amazon.com", "checkedAt": "2026-10-25T13:56:37.051259568Z" }, "github": { "repo": "aws/bedrock-agentcore-sdk-python", "checkedAt": "2026-10-26T07:12:41.690258733Z", "stars": 780, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-23T20:42:42Z", "openIssues": 82, "openPRs": 49, "issuesOpened90d": 22, "issuesClosed90d": 10, "prsMerged90d": 48, "ci": { "branch": "main", "runs": 50, "success": 45, "failure": 5, "other": 0, "latest": "failure", "latestAt": "2026-10-23T21:50:54Z" }, "advisories": [ { "ghsa": "GHSA-j6g5-3hh3-pgw8", "cve": "CVE-2026-16796", "severity": "high", "published": "2026-07-23T20:11:08Z" }, { "ghsa": "GHSA-hqf8-7w95-9r33", "cve": "CVE-2026-15737", "severity": "medium", "published": "2026-07-16T17:05:36Z" }, { "ghsa": "GHSA-6rfw-mq36-jm8h", "cve": "CVE-2026-12530", "severity": "high", "published": "2026-06-17T21:10:20Z" } ], "replies": { "sampled": 25, "unanswered": 15, "medianDays": 5.5 } }, "updatedAt": "2026-10-31T00:27:05.6519905Z" } }, "answer": "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 \u0026 pricing.", "b": { "slug": "tencentdb-agent-memory", "name": "TencentDB Agent Memory", "vendor": "Tencent Cloud", "vendorUrl": "https://github.com/TencentCloud/TencentDB-Agent-Memory", "kind": "http-api", "category": "agent-memory", "summary": "TencentDB Agent Memory is Tencent Cloud's MIT-licensed, self-hosted memory stack for coding agents. A proxy injects layered conversation memory, skills, wiki pages and code graphs into each request, with a team panel and HTTP API over SQLite.", "url": "https://www.anchorterminal.com/tools/tencentdb-agent-memory", "markdownUrl": "https://www.anchorterminal.com/tools/tencentdb-agent-memory.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tencentdb-agent-memory.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tencentdb-agent-memory.json", "repo": "https://github.com/TencentCloud/TencentDB-Agent-Memory", "license": "MIT", "transports": [ "http" ], "packages": [ { "registry": "oci", "name": "agentmemory/memory-core" }, { "registry": "oci", "name": "agentmemory/memory-hub" }, { "registry": "oci", "name": "agentmemory/memory-proxy" }, { "registry": "npm", "name": "@tencentdb-agent-memory/memory-tencentdb" }, { "registry": "npm", "name": "@tencentdb-agent-memory/memory-sdk-ts-v2" } ], "auth": "api-key", "authNotes": "Self-hosted, with no Tencent account. Agents reach memory through the proxy with a per-user key (`sk-mem-...`) sent as the Anthropic or OpenAI auth token, which the proxy checks against Memory Core. Users can hold several revocable keys, and the panel can log in through an OAuth2 identity provider. Memory Core's own bearer gate (`MEMORY_CORE_GATEWAY_API_KEY`) is empty by default, data-plane routes need only the `x-tdai-service-id` header, and the proxy's admin routes have no authentication (https://github.com/TencentCloud/TencentDB-Agent-Memory/blob/master/MemoryCore/v3-api-memorycore-doc.md).", "pricing": "free", "pricingNotes": "Free under MIT, with nothing to buy and no signup. The owner pays for the LLM calls that extract L1 to L3 memory, build wiki pages and code graphs and answer through the proxy, at whichever OpenAI-compatible or Anthropic-compatible provider is configured (https://github.com/TencentCloud/TencentDB-Agent-Memory/blob/master/INSTALL.md).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, install guide, API references or changelog read on 30 October 2026. Self-hosted open-source software with no paid endpoint.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 2218, "pypiWeekly": null, "asOf": "2026-10-30" }, "docsUrl": "https://github.com/TencentCloud/TencentDB-Agent-Memory/blob/master/INSTALL.md", "openapi": "https://github.com/TencentCloud/TencentDB-Agent-Memory/blob/master/MemoryKnowledge/openapi.yaml", "capabilities": [ "memory.store", "memory.search", "memory.user", "memory.delete", "knowledge.search" ], "tags": [ "self-hosted", "open-source", "local", "docker", "typescript", "python", "free", "no-card", "mit", "openai-compatible", "skills", "beta" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 56, "grade": "C", "agentReady": false, "rank": 767, "ranked": true, "rankOf": 1239, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 70, "payments": 60, "reliability": 51, "schema": 61, "security": 30, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-30" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "MIT licence in the repository and on every npm package, with three multi-architecture Docker images on Docker Hub's agentmemory account", "Layered recall from L3 persona and L2 scenarios down to L1 atoms and raw L0 conversation, with hybrid BM25 and vector search", "Assets are private by default, with team, restricted (user, role and agent ACLs) and agent visibility, and per-user revocable keys", "Coding agents join through the proxy by changing a base URL, for Claude Code, Codex, CodeBuddy, OpenCode, DeepSeek Harness and others", "Seven releases from 2.0.0 on 3 August to 2.0.3 on 26 October 2026, each in a dated Keep a Changelog file" ], "weaknesses": [ "The core's bearer gate is off by default, and the deploy notes say enabling it breaks the proxy's auth and session setup", "Data-plane deletes and chat-memory clears make no user-level check, trusting the bearer gate and `x-tdai-service-id`, per the API reference", "The proxy's rate-limit routes (GET, PUT, DELETE) and session admin routes have no authentication, per its own API reference", "No SECURITY.md on either branch, no security.txt and no disclosure route named for the project", "The npm OpenClaw plugin's postinstall rewrites the installed OpenClaw's files with sed, output silenced, unless skipped" ], "agentNotes": [ "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", "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", "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", "Check `data.valid` on `/v3/meta/auth/verify` and `data.isError` on `/v3/tools/call`. Both can fail inside a success envelope", "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" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56 } ], "editorialScores": { "ergonomics": 68, "maintenance": 70, "payments": 60, "reliability": 51, "schema": 61, "security": 30, "transparency": 61 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-10-30", "maintenance": "2026-10-30", "payments": "2026-10-30", "reliability": "2026-10-30", "schema": "2026-10-30", "security": "2026-10-30", "transparency": "2026-10-30" }, "last": "2026-10-30", "oldest": "2026-10-30", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "git clone https://github.com/TencentCloud/TencentDB-Agent-Memory.git\ncd TencentDB-Agent-Memory/deploy/global-images\ncp .env.example .env\n./start-all.sh", "http": "export ANTHROPIC_BASE_URL=http://127.0.0.1:8096/claude-code/default\nexport ANTHROPIC_AUTH_TOKEN='\u003csk-mem- user key\u003e'\nclaude --model \u003cPROXY_UPSTREAM_MODEL\u003e" }, "letme": { "capability": "https://letme.dev/memory.store", "tool": "https://letme.dev/tencentdb-agent-memory" }, "sameCompany": [ "hy-memory", "hy3" ], "area": "agent-runtime", "provenance": { "legalEntity": "Tencent", "domain": "tencent.com", "domainRegistered": "1998-09-14", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/TencentCloud/TencentDB-Agent-Memory/blob/master/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-30", "notes": [ "LICENSE reads 'Copyright (C) 2026 Tencent. All rights reserved.' above the MIT text, and the README footer reads '© TencentDB Agent Memory Team'. No fuller legal name was found.", "The repository is in GitHub's TencentCloud organisation. The 2.0.0 changelog and main-branch links still use github.com/Tencent/TencentDB-Agent-Memory, and raw files answer at both paths. The project has no website of its own. RDAP at Verisign gives tencent.com a registration date of 14 September 1998.", "No terms or privacy policy applies beyond the MIT licence. Self-hosted, so no status page.", "security.txt returns 404 on www.tencent.com. www.tencentcloud.com answers with a bot check, so its security.txt wasn't read. Neither branch has SECURITY.md.", "github.com pages and api.github.com weren't read. github.com/robots.txt couldn't be fetched from our session, so the host was left alone, and api.github.com is closed by the session's proxy. Files were read from raw.githubusercontent.com, which has no robots.txt (404)." ], "score": 75 }, "requirements": { "card": "no", "freeTier": true, "minutes": 30, "credential": "api-key", "hosting": [ "self-hosted" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "unknown", "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tencentdb-agent-memory.json" }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Tencent Cloud", "name": "Vendor" }, { "a": "https://bedrock-agentcore.{region}.amazonaws.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0", "b": "MIT", "name": "Licence" }, { "a": "21", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-10-26", "name": "Last release" }, { "a": "2026-10-01", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "776 stars, 1.1M npm/wk", "b": "2.2k npm/wk", "name": "Popularity" }, { "a": "3.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 pricing.", "question": "Which is better for AI agents, Amazon Bedrock AgentCore Memory or TencentDB Agent Memory?" }, { "answer": "Amazon Bedrock AgentCore Memory takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key.", "question": "Do Amazon Bedrock AgentCore Memory and TencentDB Agent Memory need an API key?" }, { "answer": "Amazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com. No hosted endpoint is listed for TencentDB Agent Memory.", "question": "Can an agent call Amazon Bedrock AgentCore Memory and TencentDB Agent Memory without installing anything?" }, { "answer": "No open-source release is listed for Amazon Bedrock AgentCore Memory. TencentDB Agent Memory is open source (MIT).", "question": "Are Amazon Bedrock AgentCore Memory and TencentDB Agent Memory open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 88 against 51", "Schema \u0026 documentation, 92 against 61", "Agent ergonomics, 86 against 68", "Security \u0026 auth, 87 against 30", "Maintenance \u0026 community, 83 against 70", "Transparency \u0026 trust, 79 against 68" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.", "slug": "agentcore-memory", "watchFor": "Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write" }, { "aheadOn": [ "Payments \u0026 pricing, 60 against 30" ], "also": [ "Free to start without a card", "Open source" ], "goodFor": "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.", "slug": "tencentdb-agent-memory", "watchFor": "The core's bearer gate is off by default, and the deploy notes say enabling it breaks the proxy's auth and session setup" } ], "job": { "capability": "memory.store", "name": "Agent memory" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-claude-mem.json", "title": "Amazon Bedrock AgentCore Memory vs claude-mem", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-claude-mem" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.json", "title": "Amazon Bedrock AgentCore Memory vs Cognee", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle.json", "title": "Amazon Bedrock AgentCore Memory vs Graphicle", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.json", "title": "Amazon Bedrock AgentCore Memory vs Graphiti", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.json", "title": "Amazon Bedrock AgentCore Memory vs Hindsight", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho.json", "title": "Amazon Bedrock AgentCore Memory vs Honcho", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.json", "title": "Amazon Bedrock AgentCore Memory vs Hy Memory", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.json", "title": "Amazon Bedrock AgentCore Memory vs LangMem", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost.json", "title": "Amazon Bedrock AgentCore Memory vs LocalGhost", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.json", "title": "Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.json", "title": "Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mempalace.json", "title": "Amazon Bedrock AgentCore Memory vs MemPalace", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-mempalace" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-past-dev.json", "title": "Amazon Bedrock AgentCore Memory vs past.dev", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-past-dev" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory.json", "title": "Amazon Bedrock AgentCore Memory vs Supermemory API + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip.json", "title": "Amazon Bedrock AgentCore Memory vs Tokenrip", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.json", "title": "Amazon Bedrock AgentCore Memory vs Zep", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/claude-mem-vs-tencentdb-agent-memory.json", "title": "claude-mem vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/claude-mem-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory.json", "title": "Cognee vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory.json", "title": "Graphiti vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.json", "title": "Hindsight vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.json", "title": "Honcho vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/hy-memory-vs-tencentdb-agent-memory.json", "title": "Hy Memory vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/hy-memory-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/langmem-vs-tencentdb-agent-memory.json", "title": "LangMem vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/langmem-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/localghost-vs-tencentdb-agent-memory.json", "title": "LocalGhost vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/localghost-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory.json", "title": "Mem0 Platform + MCP vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.json", "title": "Memory (MCP reference server) vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/mempalace-vs-tencentdb-agent-memory.json", "title": "MemPalace vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/mempalace-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/past-dev-vs-tencentdb-agent-memory.json", "title": "past.dev vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/past-dev-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/supermemory-vs-tencentdb-agent-memory.json", "title": "Supermemory API + MCP vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/supermemory-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-tokenrip.json", "title": "TencentDB Agent Memory vs Tokenrip", "url": "https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-tokenrip" }, { "json": "https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.json", "title": "TencentDB Agent Memory vs Zep", "url": "https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-ai-memory.json", "title": "Amazon Bedrock AgentCore Memory vs AI Memory", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-ai-memory" }, { "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode.json", "title": "Amazon Bedrock AgentCore Memory vs Context Mode Engine", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode" }, { "json": "https://www.anchorterminal.com/compare/ai-memory-vs-tencentdb-agent-memory.json", "title": "AI Memory vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/ai-memory-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.json", "title": "Context Mode Engine vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory" }, { "json": "https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory.json", "title": "Graphicle vs TencentDB Agent Memory", "url": "https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory" } ], "scores": [ { "agentcore-memory": 88, "by": 37, "edge": "agentcore-memory", "key": "reliability", "name": "Reliability", "tencentdb-agent-memory": 51, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "agentcore-memory": 92, "by": 31, "edge": "agentcore-memory", "key": "schema", "name": "Schema \u0026 documentation", "tencentdb-agent-memory": 61, "weight": 13 }, { "agentcore-memory": 86, "by": 18, "edge": "agentcore-memory", "key": "ergonomics", "name": "Agent ergonomics", "tencentdb-agent-memory": 68, "weight": 13 }, { "agentcore-memory": 87, "by": 57, "edge": "agentcore-memory", "key": "security", "name": "Security \u0026 auth", "tencentdb-agent-memory": 30, "weight": 14 }, { "agentcore-memory": 30, "by": 30, "edge": "tencentdb-agent-memory", "key": "payments", "name": "Payments \u0026 pricing", "tencentdb-agent-memory": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "agentcore-memory": 83, "by": 13, "edge": "agentcore-memory", "key": "maintenance", "name": "Maintenance \u0026 community", "tencentdb-agent-memory": 70, "weight": 7 }, { "agentcore-memory": 79, "by": 11, "edge": "agentcore-memory", "key": "transparency", "name": "Transparency \u0026 trust", "tencentdb-agent-memory": 68, "weight": 7 } ], "summary": "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 \u0026 pricing. Both do agent memory.", "tutorials": [], "verdicts": { "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory", "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.min.md" }, "markdown": "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 \u0026 pricing. Both do agent memory.\n\n- Amazon Bedrock AgentCore Memory: grade A, 79.7/100, rank #10 of 1239. Markdown https://www.anchorterminal.com/tools/agentcore-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json\n- 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\n- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md\n- All 188 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md\n\n## Which one, for what\n\n### Amazon Bedrock AgentCore Memory (A)\n\nGood for: Teams already on AWS that want per-user memory under IAM, KMS and Regional controls, with extraction run for them.\n\nAhead on:\n- Reliability, 88 against 51\n- Schema \u0026 documentation, 92 against 61\n- Agent ergonomics, 86 against 68\n- Security \u0026 auth, 87 against 30\n- Maintenance \u0026 community, 83 against 70\n- Transparency \u0026 trust, 79 against 68\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Long-term extraction is asynchronous. The docs say records appear within seconds to minutes after a write\n\n### TencentDB Agent Memory (C)\n\nGood 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.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 30\n\nAlso in its favour:\n- Free to start without a card\n- Open source\n\nWatch 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\n\n\n## Score by category\n\n| Category | Weight | Amazon Bedrock AgentCore Memory | TencentDB Agent Memory | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 88 | 51 | Amazon Bedrock AgentCore Memory +37 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 61 | Amazon Bedrock AgentCore Memory +31 |\n| Agent ergonomics | 13% (16.2 this run) | 86 | 68 | Amazon Bedrock AgentCore Memory +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 87 | 30 | Amazon Bedrock AgentCore Memory +57 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 60 | TencentDB Agent Memory +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 70 | Amazon Bedrock AgentCore Memory +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 79 | 68 | Amazon Bedrock AgentCore Memory +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **79.7 · A** | **56 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon Bedrock AgentCore Memory | TencentDB Agent Memory |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Tencent Cloud |\n| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com` | no (local only) |\n| Transports | HTTP, stdio | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement and Service Terms. The `bedrock-agentcore` Python SDK and the `@aws/agentcore` CLI are Apache-2.0 | MIT |\n| Tools exposed | 21 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-06 | 2026-10-26 |\n| Terms last updated | 2026-10-01 | no document linked |\n| Privacy policy last updated | 2026-05-18 | no document linked |\n| Customer content may train models | yes, with an opt-out | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 776 stars, 1.1M npm/wk | 2.2k npm/wk |\n| Agent reviews | 3.5/5 (4) | none |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Amazon Bedrock AgentCore Memory\n\n1. 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\n2. 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`\n3. Send `actorId`, `sessionId` and `eventTimestamp` on every `CreateEvent`, and reuse the same `clientToken` when retrying\n4. Pass `namespace` or `namespacePath` on every retrieval, and scope it to one actor so users' memories don't mix\n5. Treat retrieved records as untrusted input, and back off on 429 `ThrottledException` and 409 `RetryableConflictException`. A quota breach returns 402 `ServiceQuotaExceededException`\n\n### TencentDB Agent Memory\n\n1. 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\n2. 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\n3. 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\n4. Check `data.valid` on `/v3/meta/auth/verify` and `data.isError` on `/v3/tools/call`. Both can fail inside a success envelope\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Amazon Bedrock AgentCore Memory or TencentDB Agent Memory?\n\nAmazon 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 \u0026 pricing.\n\n### Do Amazon Bedrock AgentCore Memory and TencentDB Agent Memory need an API key?\n\nAmazon Bedrock AgentCore Memory takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key.\n\n### Can an agent call Amazon Bedrock AgentCore Memory and TencentDB Agent Memory without installing anything?\n\nAmazon Bedrock AgentCore Memory has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com. No hosted endpoint is listed for TencentDB Agent Memory.\n\n### Are Amazon Bedrock AgentCore Memory and TencentDB Agent Memory open source?\n\nNo open-source release is listed for Amazon Bedrock AgentCore Memory. TencentDB Agent Memory is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"agentcore-memory\", \"b\": \"tencentdb-agent-memory\"}`. From a terminal: `anchor compare agentcore-memory tencentdb-agent-memory`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agentcore-memory.json and https://www.anchorterminal.com/api/v1/tools/tencentdb-agent-memory.json\n\n## Other comparisons with Amazon Bedrock AgentCore Memory or TencentDB Agent Memory\n\n- [Amazon Bedrock AgentCore Memory vs claude-mem](https://www.anchorterminal.com/compare/agentcore-memory-vs-claude-mem.md)\n- [Amazon Bedrock AgentCore Memory vs Cognee](https://www.anchorterminal.com/compare/agentcore-memory-vs-cognee.md)\n- [Amazon Bedrock AgentCore Memory vs Graphicle](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle.md)\n- [Amazon Bedrock AgentCore Memory vs Graphiti](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphiti.md)\n- [Amazon Bedrock AgentCore Memory vs Hindsight](https://www.anchorterminal.com/compare/agentcore-memory-vs-hindsight.md)\n- [Amazon Bedrock AgentCore Memory vs Honcho](https://www.anchorterminal.com/compare/agentcore-memory-vs-honcho.md)\n- [Amazon Bedrock AgentCore Memory vs Hy Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.md)\n- [Amazon Bedrock AgentCore Memory vs LangMem](https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.md)\n- [Amazon Bedrock AgentCore Memory vs LocalGhost](https://www.anchorterminal.com/compare/agentcore-memory-vs-localghost.md)\n- [Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-mem0.md)\n- [Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.md)\n- [Amazon Bedrock AgentCore Memory vs MemPalace](https://www.anchorterminal.com/compare/agentcore-memory-vs-mempalace.md)\n- [Amazon Bedrock AgentCore Memory vs past.dev](https://www.anchorterminal.com/compare/agentcore-memory-vs-past-dev.md)\n- [Amazon Bedrock AgentCore Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/agentcore-memory-vs-supermemory.md)\n- [Amazon Bedrock AgentCore Memory vs Tokenrip](https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip.md)\n- [Amazon Bedrock AgentCore Memory vs Zep](https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.md)\n- [claude-mem vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/claude-mem-vs-tencentdb-agent-memory.md)\n- [Cognee vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory.md)\n- [Graphiti vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory.md)\n- [Hindsight vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.md)\n- [Honcho vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.md)\n- [Hy Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hy-memory-vs-tencentdb-agent-memory.md)\n- [LangMem vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/langmem-vs-tencentdb-agent-memory.md)\n- [LocalGhost vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/localghost-vs-tencentdb-agent-memory.md)\n- [Mem0 Platform + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory.md)\n- [Memory (MCP reference server) vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.md)\n- [MemPalace vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/mempalace-vs-tencentdb-agent-memory.md)\n- [past.dev vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/past-dev-vs-tencentdb-agent-memory.md)\n- [Supermemory API + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/supermemory-vs-tencentdb-agent-memory.md)\n- [TencentDB Agent Memory vs Tokenrip](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-tokenrip.md)\n- [TencentDB Agent Memory vs Zep](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.md)\n- [Amazon Bedrock AgentCore Memory vs AI Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-ai-memory.md)\n- [Amazon Bedrock AgentCore Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode.md)\n- [AI Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/ai-memory-vs-tencentdb-agent-memory.md)\n- [Context Mode Engine vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.md)\n- [Graphicle vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-31", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory", "url": "" } ], "description": "Amazon Bedrock AgentCore Memory scores 79.7 (A) to TencentDB Agent Memory's 56 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon Bedrock AgentCore Memory A 79.7", "TencentDB Agent Memory C 56", "scores" ], "h1": "Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory", "image": "https://www.anchorterminal.com/assets/og/compare-agentcore-memory-vs-tencentdb-agent-memory.png", "path": "/compare/agentcore-memory-vs-tencentdb-agent-memory", "published": "2026-10-01", "section": "tools", "title": "Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory (2026)", "toc": null, "updated": "2026-10-30", "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory" }, "tokens": { "markdown": 3350, "slim": 780 }, "version": 1 }