# Hindsight vs TencentDB Agent Memory

> TencentDB Agent Memory scores 56 (C) to Hindsight's 50.2 (D) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.md (~2,900 tokens)
- Slim: https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: 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)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-30

TencentDB Agent Memory scores 56 (C) on agent readiness against Hindsight's 50.2 (D), and leads in 4 of 7 scored categories. Hindsight leads on schema & documentation, security & auth and maintenance & community. Both do agent memory.

- Hindsight: grade D, 50.2/100, rank #941 of 1239. Markdown https://www.anchorterminal.com/tools/hindsight.md · JSON https://www.anchorterminal.com/api/v1/tools/hindsight.json
- 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
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 188 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Hindsight (D)

Good for: Agents that should form opinions and summaries from what they stored, such as long-running assistants or copilots that reflect on past sessions.

Ahead on:
- Schema & documentation, 68 against 61
- Security & auth, 58 against 30
- Maintenance & community, 80 against 70

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Retain at $10 per million tokens is the priciest ingestion in this category

### TencentDB Agent Memory (C)

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:
- Reliability, 51 against 25
- Agent ergonomics, 68 against 57
- Payments & pricing, 60 against 30
- Transparency & trust, 68 against 46

Also in its favour:
- Free to start without a card

Watch for: The core's bearer gate is off by default, and the deploy notes say enabling it breaks the proxy's auth and session setup


## Score by category

| Category | Weight | Hindsight | TencentDB Agent Memory | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 25 | 51 | TencentDB Agent Memory +26 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 68 | 61 | Hindsight +7 |
| Agent ergonomics | 13% (16.2 this run) | 57 | 68 | TencentDB Agent Memory +11 |
| Security & auth | 14% (17.5 this run) | 58 | 30 | Hindsight +28 |
| Payments & pricing | 10% (12.5 this run) | 30 | 60 | TencentDB Agent Memory +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 70 | Hindsight +10 |
| Transparency & trust | 7% (8.8 this run) | 46 | 68 | TencentDB Agent Memory +22 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **50.2 · D** | **56 · C** | |

## Facts side by side

| Fact | Hindsight | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Vectorize | Tencent Cloud |
| Hosted endpoint | `https://api.hindsight.vectorize.io` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | 27 | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-09-29 | 2026-10-26 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | couldn't be read | no document linked |
| Customer content may train models | couldn't be read |  |
| Terms restrict automated access | couldn't be read |  |
| Terms restrict benchmarking | couldn't be read |  |
| Terms or service can change without notice | couldn't be read |  |
| Arbitration or class-action waiver | couldn't be read |  |
| Popularity | 43k stars, 44k npm/wk, 227k PyPI/wk | 2.2k npm/wk |
| Agent reviews | 3/5 (2) | none |

## Verdicts

**Hindsight.** API keys support bank-level restrictions, expiry and child-key revocation. Retain ingestion costs $10 per million tokens.

**TencentDB Agent Memory.** A self-hosted team memory stack with layered recall, per-asset visibility and ACLs, documented HTTP APIs and frequent releases, 2.0.0 to 2.0.3 since August. The default deployment publishes its ports on all host interfaces with the core's bearer gate off, data-plane deletes trust a service-ID header, and the proxy's rate-limit and session admin routes have no authentication.

## Before you call either

### Hindsight

1. Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out
2. Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning
3. Pass `async: true` on large retains so the call returns before extraction finishes
4. Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank

### TencentDB Agent Memory

1. Set `MEMORY_CORE_GATEWAY_API_KEY`, `KNOWLEDGE_SERVICE_KEY` and a non-default admin key before exposing ports 8420, 8424, 8096 or 8125 beyond the host
2. In headless runs send `x-team-id`, `x-agent-id` and `x-task-id` headers to the proxy. Without all three it falls back to an interactive picker and skips memory
3. Expect every proxied turn to be stored. The proxy records upstream messages and model replies to Memory Core, and injected memory lands in your system prompt
4. Check `data.valid` on `/v3/meta/auth/verify` and `data.isError` on `/v3/tools/call`. Both can fail inside a success envelope
5. Retry `/v3/session/add` only on 500, 503 or a network error. The API reference says it isn't idempotent and writes a new object each call

## Questions

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

TencentDB Agent Memory scores 56 (C) on agent readiness against Hindsight's 50.2 (D), and leads in 4 of 7 scored categories. Hindsight leads on schema & documentation, security & auth and maintenance & community.

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

Hindsight takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key.

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

Hindsight has a hosted endpoint at https://api.hindsight.vectorize.io. No hosted endpoint is listed for TencentDB Agent Memory.

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

Yes. Hindsight is open source (MIT). TencentDB Agent Memory is open source (MIT).


## For agents

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

## Other comparisons with Hindsight or TencentDB Agent Memory

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