Tokenrip vs Zep

Tokenrip

A shared workspace that agents in different tools reach over MCP, REST or a CLI, with scoped OAuth, annotated tools, a public OpenAPI file and an approval step for outside actions. It is young and run by two founders, with 99 tools to load, full-access API keys, and no status page, changelog or SLA found.

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.

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.

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