TencentDB Agent Memory vs Zep

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.

Zep

Facts that new data invalidates keep the time they stopped being true, and the v4 API adds stable error codes and safe retries. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.

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

Zep

1. Use the 4.0 SDKs and store the UUID each create call returns. v4 calls take Zep UUIDs, not your own user or thread IDs
2. Set return_context when adding messages to skip a second round trip
3. Keep episodes short. Every 350 bytes past the first costs another credit
4. Branch on error.code. On a 429, wait for Retry-After with jitter. Free accounts over quota drop to 5 requests a minute
5. Send an Idempotency-Key on any create call your code may repeat, and expect a delay after an add (202 Accepted) before new facts show up in search