# Agent Platform Memory Bank vs TencentDB Agent Memory

> Agent Platform Memory Bank scores 65.6 (B) to TencentDB Agent Memory's 50.9 (D) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/google-memory-bank-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/google-memory-bank-vs-tencentdb-agent-memory.md (~6,350 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: 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)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Agent Platform Memory Bank scores 65.6 (B) on agent readiness against TencentDB Agent Memory's 50.9 (D), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and maintenance & community. Both do agent memory.

- Agent Platform Memory Bank: grade B, 65.6/100, rank #414 of 1510. Markdown https://www.anchorterminal.com/tools/google-memory-bank.md · JSON https://www.anchorterminal.com/api/v1/tools/google-memory-bank.json
- TencentDB Agent Memory: grade D, 50.9/100, rank #1049 of 1510. 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 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Agent Platform Memory Bank (B)

Good for: Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.

Ahead on:
- Reliability, 68 against 51
- Schema & documentation, 75 against 61
- Agent ergonomics, 75 against 68
- Security & auth, 72 against 35
- Transparency & trust, 81 against 68

Also in its favour:
- A hosted endpoint, with nothing to install
- No incidents deducted, where TencentDB Agent Memory loses 6 points for them

Watch for: Needs a Google Cloud project with billing, set up by a person in the console

### TencentDB Agent Memory (D)

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:
- Payments & pricing, 60 against 20
- Maintenance & community, 70 against 62

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


## Why the edge

### Payments & pricing: TencentDB Agent Memory +40

- Agent Platform Memory Bank (20): No x402, MPP or L402 (0). Storage, read and write prices are published without a login (20). No Memory Bank free tier found (0). A person creates the project, enables billing and sets up IAM in the console (0). Total 20.
- TencentDB Agent Memory (60): Read with the self-hosted rule. MIT software with nothing to buy from Tencent, so 20 for pricing, 20 for a free start and 20 for use without an account. No x402, MPP or L402 (0). Memory extraction, wiki and code-graph building and the proxied model are paid to whichever LLM provider the owner configures.

### Security & auth: Agent Platform Memory Bank +37

- Agent Platform Memory Bank (72): OAuth 2.0 with IAM and service accounts (30), less 10, as for the other Google API listings, because the v1 discovery document lists `access_token`, `oauth_token` and `key` as query parameters (20 of 30). IAM Conditions can restrict access by memory scope; purge and delete have no confirmation (15 of 20). Memories are written by an LLM from conversation content and returned to agents, with no injection guidance found (5 of 15). Access Transparency and Access Approval are listed; Cloud Audit Logs coverage for Memory Bank wasn't read (12 of 15). Google's valid security.txt, vulnerability reward programme and certifications, with HIPAA listed for Memory Bank (20). Total 72.
- TencentDB Agent Memory (35): Read as self-hosted software with a network API. Per-user `sk-mem-` keys, several per user and revocable, and OAuth2 for panel login. Against that, Memory Core's bearer gate is off by default and the .env template says setting it breaks the proxy's auth and session setup, the data plane takes team, agent and user IDs from the caller and needs only `x-tdai-service-id`, the proxy's rate-limit and session admin routes have no authentication, `/v3/instance/destroy` rests on the same unset bearer, the deploy README's defaults include an `admin` key, and the start scripts publish every port on all interfaces (8 of 30). Private-by-default assets with team, restricted and agent visibility, ACLs by user, role and agent, and read-only Knowledge tools. Data-plane deletes and `chat-memory/clear` make no user-level check and nothing asks for confirmation. Asset reads were scoped to the caller only in 2.0.2, and Agent and Task reads only in an unreleased commit of 28 October (8 of 20). The proxy injects stored memory, skills, imported documents and code into the system prompt, and we found no guidance on prompt injection or memory poisoning. Personal skills are private until shared after review (3 of 15). Participation logs, memory-generation logs and the raw L0 record let the operator trace what was written, and per-call analytics to ClickHouse is available but off by default (9 of 15). CONTRIBUTING.md asks for vulnerability reports by email to agentmemory@tencent.com rather than public issues, with no acknowledgement time, so a disclosure route without a stated time (7). No SECURITY.md on any branch, no security.txt on www.tencent.com, and no bounty or audit named. The npm plugin's postinstall runs a bash script that rewrites OpenClaw's installed files, with output sent to /dev/null. Two access-control fixes in 2026 are under the negative events.

### Reliability: Agent Platform Memory Bank +17

- Agent Platform Memory Bank (68): Hosted lines. Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November 2026, holds four incidents since 8 August (20 August, 27 products; 1 September, us-central1-b; 8 October, Cloud Storage; 20 October, europe-west2, 38 products), and none names Agent Platform, Vertex or Memory Bank (30). No Memory Bank quotas or rate limits were found; the platform quotas path guessed returned 404 (0, unchecked). Generation is a long-running operation with wait and cancel methods, and Google's retry guidance wasn't re-read for this API (8 of 15). No SLA for Memory Bank was found in the pages read (0, unchecked). Memory profiles, IngestEvents and multi-regional endpoints are GA (10). Total 68.
- TencentDB Agent Memory (51): Local-software reading, as software the owner runs. Official multi-architecture images (amd64 and arm64) on Docker Hub's agentmemory account, named in the changelog, with Node 22.16 or later stated for the plugin and Python 3.9 or later for the SDK. Setup still needs a git clone for the start scripts, which pull `:latest` (18 of 20). Vitest suites are declared in the package files. The one CI workflow, pr-ci.yml, runs on pull requests to the main branch (the OpenClaw plugin) and installs, packs and checks the manifest, package size and skill-queue isolation without running the test suites, and nothing runs on the default branch, now feat/server_team. GitHub's Actions pages weren't readable, so no result was read (8 of 25). GitHub issues weren't readable, so open crash reports weren't counted. The changelogs list fixes for empty recall, lost memories, duplicated history and a Knowledge service that failed to start on OpenTelemetry drift, and outside pull requests (#31, #59, #79, #85) were merged into the plugin (8 of 25). Keep a Changelog with SemVer declared and upgrade notes, such as backend switches not migrating data and a v2 to v3 migration tool, but three version streams disagree (image tags 1.0.x for releases 2.0.x, the npm plugin at 1.0.3 while main's changelog stops at 0.3.6) and ROADMAP.md still says 2.0.1-beta.1 is current on 4 November (9 of 15). Release 2.0.3, but the README heads the Hub 'Team Memory Beta' and the SDKs are beta-only (8 of 15).

### Schema & documentation: Agent Platform Memory Bank +14

- Agent Platform Memory Bank (75): Google's discovery document is a machine-readable contract for every memory method (25). No llms.txt or Markdown docs found (0). Method descriptions are 13 to 39 characters, one-line summaries, while the guides explain when to generate from sessions or from direct facts (12 of 20). Typed schemas with required fields in the discovery document (12 of 15). Python examples, a troubleshooting page and a documented 404 for deleted memories (11 of 15). v1 and v1beta1 and dated release notes (15). Total 75.
- TencentDB Agent Memory (61): API reading for a self-hosted HTTP service. The Knowledge service has an OpenAPI 3.0.3 file of 28 paths with no security scheme. Memory Core's 109 endpoints and the proxy's routes are described only in Markdown references, and the proxy's main LLM paths are outside them (10 of 25). No website and no llms.txt. The docs are Markdown in the repository and readable raw (5 of 10). Each Core endpoint states what it does, its limits and caveats, such as which deletes skip user checks, and Knowledge's tool list marks its tools read-only. The API references and the changelog are in Chinese; the README and install guide are in English (11 of 20). Zod-checked inputs with bounds (1 to 100 messages, 8,192 characters per message, `limit` up to 100) and enums for atom types, but the reference records that `version` comes back as a string from `atomic/update` and a number from `query` (10 of 15). Worked request and response examples per endpoint and error tables per module, with the three different error-message formats set out (12 of 15). `/v3` paths with v1 and v2 routes listed as deprecated, and a dated public changelog for every release since 0.1.0 (13 of 15).

### Transparency & trust: Agent Platform Memory Bank +13

- Agent Platform Memory Bank (81): Closed service under the Google Cloud terms (15). Data residency at rest, CMEK and the Cloud Data Processing Addendum apply; no Memory Bank retention period or time-to-live was read (20 of 30). The rename was announced in the release notes with old and new names listed, and Google's deprecation policy covers GA services (14 of 20). Google Cloud's subprocessor list and regional endpoints are published (16 of 20). Total 65.
- TencentDB Agent Memory (68): MIT on both branches and in npm metadata, with the codegraph and Hermes Agent code it reuses credited in the README (30 of 30). The README says new chat memory and skills are private by default and sets out what each visibility means. No privacy statement says what each layer keeps or for how long. The proxy records every turn's upstream messages and model replies, the plugin's L0 and L1 retention defaults to never, `chat-memory/clear` empties L0, L1 and profile content while keeping the asset, and switching storage backends leaves data behind (12 of 30). v1 and v2 routes are marked deprecated with removal 'planned' and no date, and known limitations promise fixes 'in the next version' without dates (6 of 20). The plugin's metrics reporting is off by default and writes to local logs only, and ClickHouse analytics are off by default and documented. Core depends on OpenTelemetry exporters, and we didn't audit whether anything exports by default. The Hermes Docker image's default model endpoint is Tencent Cloud LKE, which the README states (13 of 20).

### Maintenance & community: TencentDB Agent Memory +8

- Agent Platform Memory Bank (62): The newest Memory Bank release notes are of 20 August 2026 (IngestEvents GA, metadata, Gemini Embedding 2), 78 days before the check, and billing started on 1 September (20). Three Memory Bank entries in the 90 days, all on 20 August (10 of 20). Public release notes and Cloud Customer Care (12 of 15). `google-cloud-agentplatform` 2.7.0 on 28 October 2026, twelve releases in 90 days per its PyPI release feed, plus ADK (15). SDK test status not checked (5 of 10). Total 62.
- TencentDB Agent Memory (70): Release 2.0.3 on 26 October 2026 by the changelog and its tag, 9 days before this check (30). Six changelog releases in the 90 days from 6 August, 2.0.1-beta.1 (13 August), 2.0.1 (25 August), 2.0.2-beta.1 (7 September), 2.0.2 (9 October), 2.0.3-beta.1 (13 October) and 2.0.3, with image tags v1.0.2 (8 September) and v1.0.3 (22 September) between. The three stable releases 2.0.1, 2.0.2 and 2.0.3 meet the line without the pre-releases, which this run doesn't count (20). GitHub issues and pull requests weren't readable, so reply times weren't judged. The plugin changelog credits fixes to numbered issues and outside pull requests, and the README says issues get a reply within 24 hours, which we couldn't check. A workflow added on 28 October posts an automatic acknowledgement on new external pull requests, which isn't a maintainer reply (10 of 25). Official TypeScript and Python SDKs exist but only as betas, the TypeScript one last published on 14 August 2026, and the Python package name differs between the changelog and its pyproject. No MCP server, so the registry line doesn't apply (6 of 15). npm packages carry registry signatures but no provenance attestations, the deploy pulls `:latest` images, the one CI workflow skips the tests and doesn't run on the default branch, and 2.0.3 fixed a Knowledge service broken by OpenTelemetry dependency drift (4 of 10).

## Score by category

| Category | Weight | Agent Platform Memory Bank | TencentDB Agent Memory | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 68 | 51 | Agent Platform Memory Bank +17 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 75 | 61 | Agent Platform Memory Bank +14 |
| Agent ergonomics | 13% (16.2 this run) | 75 | 68 | Agent Platform Memory Bank +7 |
| Security & auth | 14% (17.5 this run) | 72 | 35 | Agent Platform Memory Bank +37 |
| Payments & pricing | 10% (12.5 this run) | 20 | 60 | TencentDB Agent Memory +40 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 62 | 70 | TencentDB Agent Memory +8 |
| Transparency & trust | 7% (8.8 this run) | 81 | 68 | Agent Platform Memory Bank +13 |
| Negative events | ≤15 | 0 | -6 | |
| **Total** | | **65.6 · B** | **50.9 · D** | |

## Facts side by side

| Fact | Agent Platform Memory Bank | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Google Cloud | Tencent Cloud |
| Hosted endpoint | `https://aiplatform.googleapis.com/v1` | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | none | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-08-20 | 2026-10-26 |
| Terms last updated | 2026-09-02 | no document linked |
| Privacy policy last updated | 2026-10-01 | no document linked |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 2.2k npm/wk |

## How the scores have moved

### Agent Platform Memory Bank

No score change since it was listed.

### TencentDB Agent Memory

- -5.1 on 4 November 2026 (C to D): security, correction

## Verdicts

**Agent Platform Memory Bank.** Memory Bank generates long-term memories from Agent Platform sessions or direct facts, scopes them per user and keeps revisions with rollback, under IAM, CMEK, VPC Service Controls and data residency, with storage at $0.30 per GiB-month. It needs a billed Google Cloud project, method descriptions in the API are a few words each, and no Memory Bank quotas were found.

**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.1 to 2.0.3 since August. The default deployment publishes its ports on all interfaces with the core's bearer gate off, the proxy's admin routes have no authentication, and two 2026 access-control fixes came without advisories.

## Before you call either

### Agent Platform Memory Bank

1. Run `memories.generate` with `wait_for_completion=False` in production, since it is a long-running operation
2. Always pass a `scope` such as {"user_id": ...} so one user's memories never reach another
3. Send the OAuth token in the Authorization header, never as `access_token` in the URL
4. Expect a 404 when fetching a deleted memory and treat it as gone
5. Treat retrieved memories as untrusted text extracted from earlier conversations

### 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
6. Build from the default branch past 2.0.3, or wait for the next release, before giving several users one Memory Core. Agent and Task reads were unscoped until 28 October

## Questions

### Which is better for AI agents, Agent Platform Memory Bank or TencentDB Agent Memory?

Agent Platform Memory Bank scores 65.6 (B) on agent readiness against TencentDB Agent Memory's 50.9 (D), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and maintenance & community.

### Do Agent Platform Memory Bank and TencentDB Agent Memory need an API key?

Agent Platform Memory Bank uses an OAuth sign-in. TencentDB Agent Memory needs an API key.

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

Agent Platform Memory Bank has a hosted endpoint at https://aiplatform.googleapis.com/v1. No hosted endpoint is listed for TencentDB Agent Memory.

### Are Agent Platform Memory Bank and TencentDB Agent Memory open source?

No open-source release is listed for Agent Platform Memory Bank. TencentDB Agent Memory is open source (MIT).


## For agents

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

## Other comparisons with Agent Platform Memory Bank or TencentDB Agent Memory

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