# MemMachine vs TencentDB Agent Memory

> MemMachine scores 58 (C) 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/memmachine-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/memmachine-vs-tencentdb-agent-memory.md (~5,400 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

MemMachine scores 58 (C) on agent readiness against TencentDB Agent Memory's 50.9 (D), and leads in 3 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and transparency & trust. Both do agent memory.

- MemMachine: grade C, 58/100, rank #767 of 1486. Markdown https://www.anchorterminal.com/tools/memmachine.md · JSON https://www.anchorterminal.com/api/v1/tools/memmachine.json
- TencentDB Agent Memory: grade D, 50.9/100, rank #1040 of 1486. 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

### MemMachine (C)

Good for: Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations.

Ahead on:
- Schema & documentation, 79 against 61
- Security & auth, 41 against 35
- Maintenance & community, 83 against 70

Also in its favour:
- No key needed to call it
- Runs on your own machine
- No incidents deducted, where TencentDB Agent Memory loses 6 points for them

Watch for: Version 0.4.0 of 6 October 2026, pre-1.0, with no changelog file in the repository

### 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 40
- Transparency & trust, 68 against 57

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


## Why the edge

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

- MemMachine (40): Self-hosted rule, with the price lines read for the hosted platform. No x402, MPP or L402 (0 of 40). No hosted prices found on the site or docs (0). Free to self-host with no card (20). An agent can install it from PyPI with no account (20). Total 40.
- 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.

### Schema & documentation: MemMachine +18

- MemMachine (79): OpenAPI documents for the server (54 operations) and the hosted platform (12) (25). llms.txt on docs.memmachine.ai with Markdown pages (10). Every operation has a description, and the docs explain memory types and scoping (15 of 20). Typed request models generated from the server, with search options for limits and filters (12 of 15). Examples for each client and the MCP tools, but only 422 is documented on the server and the README's first example doesn't run (8 of 15). `/api/v2` paths and tagged releases, no changelog (9 of 15). Total 79.
- 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).

### Maintenance & community: MemMachine +13

- MemMachine (83): v0.4.0 on PyPI on 8 October 2026, 29 days before the check (30). v0.3.9-post1, v0.4.0, v0.4.1-dev0 and v0.4.1-a1 in 90 days (20). Many open issues and recent reports with few replies (12 of 25). Python and TypeScript clients, both current (12 of 15). uv lock checks, security audit, SBOM and stale-issue workflows (9 of 10). Total 83.
- 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).

### Transparency & trust: TencentDB Agent Memory +11

- MemMachine (57): Apache-2.0 (30). The terms say hosted customer data is destroyed on termination, with no period, and use usage data only in aggregate; the privacy policy wasn't read (12 of 30). No deprecation policy or notices found (3 of 20). No telemetry calls found in the server or client source, and the docs don't address it (10 of 20). Total 55.
- 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).

### Security & auth: MemMachine +6

- MemMachine (41): Framework reading for software the owner runs. The server has no authentication and no security scheme in its OpenAPI document (15 of 30). No read-only mode or confirmation for deletes (5 of 20). No guidance on recalled memories as untrusted text (4 of 15). No audit log on the self-hosted server; the hosted console shows usage (5 of 15). SECURITY.md with GitHub private reporting and a two-business-day acknowledgement, with security-audit and SBOM workflows; no security.txt or certification (12 of 20). Total 41.
- 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.

## Score by category

| Category | Weight | MemMachine | TencentDB Agent Memory | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 51 | 51 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 61 | MemMachine +18 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 68 | TencentDB Agent Memory +3 |
| Security & auth | 14% (17.5 this run) | 41 | 35 | MemMachine +6 |
| Payments & pricing | 10% (12.5 this run) | 40 | 60 | TencentDB Agent Memory +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 70 | MemMachine +13 |
| Transparency & trust | 7% (8.8 this run) | 57 | 68 | TencentDB Agent Memory +11 |
| Negative events | ≤15 | 0 | -6 | |
| **Total** | | **58 · C** | **50.9 · D** | |

## Facts side by side

| Fact | MemMachine | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | MemVerge, Inc. | Tencent Cloud |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, stdio, Streamable HTTP | HTTP |
| Auth | None | API key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 3 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-08 | 2026-10-26 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | 2026-05-20 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 3.1k stars, 28 npm/wk, 581 PyPI/wk | 2.2k npm/wk |

## How the scores have moved

### MemMachine

No score change since it was listed.

### TencentDB Agent Memory

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

## Verdicts

**MemMachine.** MemMachine is an Apache-2.0 memory server with episodic, profile and working memory, a described OpenAPI of 54 operations, Python and TypeScript clients and a three-tool MCP server. It is version 0.4.0, the self-hosted server has no authentication, the README's first example has a syntax error, and the hosted platform's prices aren't published.

**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

### MemMachine

1. Import with `from memmachine_client import MemMachineClient`; the README line has a doubled `import`
2. Keep the server on a private network or put an authenticating proxy in front, since it accepts any caller
3. Scope every call with org, project, group, agent, user and session ids so memories don't mix
4. Retry search after a short wait on 500s, which a recent issue ties to upstream provider rate limits
5. Treat recalled episodes as untrusted text from past 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, MemMachine or TencentDB Agent Memory?

MemMachine scores 58 (C) on agent readiness against TencentDB Agent Memory's 50.9 (D), and leads in 3 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and transparency & trust.

### Do MemMachine and TencentDB Agent Memory need an API key?

MemMachine needs no key. TencentDB Agent Memory needs an API key.

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

MemMachine runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for TencentDB Agent Memory.

### Are MemMachine and TencentDB Agent Memory open source?

Yes. MemMachine is open source (Apache-2.0). TencentDB Agent Memory is open source (MIT).


## For agents

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

## Other comparisons with MemMachine or TencentDB Agent Memory

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