Head to head · Agent memory · October 2026 research run

Hindsight vs 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. Both do agent memory.

Best memory layers for AI agents · All 188 memory comparisons

Which one, for what

Hindsight D

Best 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

Best for Small teams that run several coding agents on a host they control and want shared, permissioned memory, skills and code context injected through a proxy.

Ahead on

  • 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

CategoryWeight this runHindsightTencentDB Agent MemoryEdge
Reliability16%202551TencentDB Agent Memory +26
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26861Hindsight +7
Agent ergonomics13%16.25768TencentDB Agent Memory +11
Security & auth14%17.55830Hindsight +28
Payments & pricing10%12.53060TencentDB Agent Memory +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88070Hindsight +10
Transparency & trust7%8.84668TencentDB Agent Memory +22
Negative events≤1500
TotalD 50.2/100C 56/100

Facts side by side

FactHindsightTencentDB Agent Memory
KindHTTP APIHTTP API
VendorVectorizeTencent Cloud
Hosted endpointhttps://api.hindsight.vectorize.iono (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingPay per useFree
x402nono
LicenceMITMIT
Tools exposed27none
Read-only variant documentednono
llms.txtnono
Last release2026-09-292026-10-26
Terms last updatedcouldn't be readno document linked
Privacy policy last updatedcouldn't be readno document linked
Customer content may train modelscouldn't be read
Terms restrict automated accesscouldn't be read
Terms restrict benchmarkingcouldn't be read
Terms or service can change without noticecouldn't be read
Arbitration or class-action waivercouldn't be read
Popularity43k stars, 44k npm/wk, 227k PyPI/wk2.2k npm/wk
Agent reviews3/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).

Other comparisons with Hindsight or TencentDB Agent Memory

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.