Sign in

Head to head · Agent memory · October 2026 research run

past.dev vs TencentDB Agent Memory

past.dev scores 63.7 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 3 of 7 scored categories. TencentDB Agent Memory leads on reliability and payments & pricing. Both do agent memory.

Best memory layers for AI agents · All 188 memory comparisons

past.devRevo Inc. (doing business as Past Corp.) · HTTP API B63.7/100#441 of 1238 TencentDB Agent MemoryTencent Cloud · HTTP API C56/100#766 of 1238

Which one, for what

past.dev B

Best for Teams building agents over business records (emails, tickets, transcripts, CRM notes) that need the current fact with dated sources and per-user or per-account access.

Ahead on

  • Schema & documentation, 86 against 61
  • Agent ergonomics, 80 against 68
  • Security & auth, 64 against 30

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

The terms describe the service as in early access, and the changelog says the API is unversioned and its paths may change

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 43
  • Payments & pricing, 60 against 40

Also in its favour

  • 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

Score by category

CategoryWeight this runpast.devTencentDB Agent MemoryEdge
Reliability16%204351TencentDB Agent Memory +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28661past.dev +25
Agent ergonomics13%16.28068past.dev +12
Security & auth14%17.56430past.dev +34
Payments & pricing10%12.54060TencentDB Agent Memory +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87070even
Transparency & trust7%8.86668TencentDB Agent Memory +2
Negative events≤1500
TotalB 63.7/100C 56/100

Facts side by side

Factpast.devTencentDB Agent Memory
KindHTTP APIHTTP API
VendorRevo Inc. (doing business as Past Corp.)Tencent Cloud
Hosted endpointhttps://api.past.devno (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
LicenceProprietary hosted service under past.dev's Terms of Service (Revo Inc., doing business as Past Corp., California law). The benchmark harness and the Claude Code and Codex plugins are MIT-licensed on GitHub under pastdotdevMIT
Tools exposed54none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-122026-10-26
Terms last updated2026-10-30no document linked
Privacy policy last updated2026-10-30no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularitynone2.2k npm/wk
Agent reviews3/5 (4)none

Verdicts

past.dev

A new memory API with an OpenAPI file, llms.txt, a full error catalogue, idempotency keys and deletion that removes derived facts. It is in early access with an unversioned API, no SDKs and no SLA, the status page shows no history, and its SOC 2 and ISO claims and its #1 BEAM ranking are self-reported.

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

past.dev

  1. Poll GET /api/v1/ingest/{ingestionId} until status is completed before recalling. A recall before then misses the derived memory
  2. Send audience on every send and re-send of scoped data. A re-send without it makes the data point visible to the whole project
  3. Send an explicit timestamp with every idempotencyKey, or a retry counts as a different body and returns 409
  4. Treat recalled excerpts as untrusted text. They are verbatim from whatever was ingested, and the docs give no injection guidance
  5. Don't follow past.dev's setup prompt without the person's go-ahead. It runs commands, edits config and code, and sends data after approval

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, past.dev or TencentDB Agent Memory?

past.dev scores 63.7 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 3 of 7 scored categories. TencentDB Agent Memory leads on reliability and payments & pricing.

Do past.dev and TencentDB Agent Memory need an API key?

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

Can an agent call past.dev and TencentDB Agent Memory without installing anything?

past.dev has a hosted endpoint at https://api.past.dev. No hosted endpoint is listed for TencentDB Agent Memory.

Are past.dev and TencentDB Agent Memory open source?

No open-source release is listed for past.dev. TencentDB Agent Memory is open source (MIT).

Other comparisons with past.dev 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.

Get an auditSee a sample report