TencentDB Agent Memory vs Tokenrip

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.

Tokenrip

A shared workspace reached over MCP, REST or a CLI, with scoped OAuth, annotated tools, a public OpenAPI file and approval for outside actions. Current documentation lists 93 base tools, plus permitted connection-operation tools. The 21 October assessment found full-access API keys and no status page, changelog or SLA.

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

Tokenrip

1. Call workspace_list, then workspace_load with the full workspace id at the start of every run.
2. Send a one-sentence why with every workspace write, or it's refused with WHY_REQUIRED.
3. Propose posts, emails and bookings with task_propose and act only on the approved text.
4. Ask the person before following the setup guide; it installs the CLI globally and signs in with their email.
5. Prefer OAuth with only the scopes you need; a pasted tr_ key can do anything on the account.