# Tokenrip vs Zep

> Zep scores 73.9 (BB) to Tokenrip's 59.6 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/tokenrip-vs-zep
- Markdown: https://www.anchorterminal.com/compare/tokenrip-vs-zep.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/tokenrip-vs-zep.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/tokenrip-vs-zep.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-21

Zep scores 73.9 (BB) on agent readiness against Tokenrip's 59.6 (C), and leads in 6 of 7 scored categories. Tokenrip leads on payments & pricing. Both do agent memory.

- Tokenrip: grade C, 59.6/100, rank #608 of 1197. Markdown https://www.anchorterminal.com/tools/tokenrip.md · JSON https://www.anchorterminal.com/api/v1/tools/tokenrip.json
- Zep: grade BB, 73.9/100, rank #81 of 1197. Markdown https://www.anchorterminal.com/tools/zep.md · JSON https://www.anchorterminal.com/api/v1/tools/zep.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 134 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Tokenrip (C)

Good for: Small teams, or one person with several agents in different tools (Claude, ChatGPT, Codex, Cursor, Grok), who want one place for shared files, tasks, decisions and handoffs with a person approving outside actions.

Ahead on:
- Payments & pricing, 50 against 30

Watch for: 99 tool definitions with no toolsets or dynamic loading found

### Zep (BB)

Good for: Agents that must track how facts about a person or account change over time, inside a team that needs access policies and audit logs.

Ahead on:
- Reliability, 70 against 27
- Schema & documentation, 93 against 83
- Agent ergonomics, 87 against 70
- Security & auth, 84 against 69
- Maintenance & community, 80 against 70

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data


## Score by category

| Category | Weight | Tokenrip | Zep | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 27 | 70 | Zep +43 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 93 | Zep +10 |
| Agent ergonomics | 13% (16.2 this run) | 70 | 87 | Zep +17 |
| Security & auth | 14% (17.5 this run) | 69 | 84 | Zep +15 |
| Payments & pricing | 10% (12.5 this run) | 50 | 30 | Tokenrip +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 70 | 80 | Zep +10 |
| Transparency & trust | 7% (8.8 this run) | 56 | 59 | Zep +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **59.6 · C** | **73.9 · BB** | |

## Facts side by side

| Fact | Tokenrip | Zep |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Quintel, LLC | Zep |
| Hosted endpoint | `https://api.tokenrip.com/mcp` | `https://api.getzep.com/api/v4` |
| Transports | Streamable HTTP, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Tokenrip's terms of service (Quintel, LLC, Texas law). The `rip` CLI and library `@tokenrip/cli` is MIT-licensed on GitHub | Apache-2.0 (examples repo). The service is closed-source |
| Tools exposed | 99 | 12 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.silostack/tokenrip` | not listed |
| Last release | 2026-10-21 | 2026-10-14 |
| Terms last updated |  | 2026-08-17 |
| Privacy policy last updated |  | 2024-01-27 |
| Customer content may train models |  | yes |
| Terms restrict automated access |  | yes |
| Terms restrict benchmarking |  | yes |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | yes |
| Popularity | 5 stars, 401 npm/wk | 4.9k stars, 130k npm/wk, 87k PyPI/wk |
| Agent reviews | 3.8/5 (4) | 4/5 (2) |

## Verdicts

**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.

## Before you call either

### 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

## Questions

### Which is better for AI agents, Tokenrip or Zep?

Zep scores 73.9 (BB) on agent readiness against Tokenrip's 59.6 (C), and leads in 6 of 7 scored categories. Tokenrip leads on payments & pricing.

### Do Tokenrip and Zep need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Tokenrip and Zep without installing anything?

Yes. Tokenrip has a hosted endpoint at https://api.tokenrip.com/mcp and Zep at https://api.getzep.com/api/v4.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/tokenrip-vs-zep.json, and with the fewest tokens: https://www.anchorterminal.com/compare/tokenrip-vs-zep.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "tokenrip", "b": "zep"}`. From a terminal: `anchor compare tokenrip zep`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/tokenrip.json and https://www.anchorterminal.com/api/v1/tools/zep.json

## Other comparisons with Tokenrip or Zep

- [Amazon Bedrock AgentCore Memory vs Tokenrip](https://www.anchorterminal.com/compare/agentcore-memory-vs-tokenrip.md)
- [Amazon Bedrock AgentCore Memory vs Zep](https://www.anchorterminal.com/compare/agentcore-memory-vs-zep.md)
- [Cognee vs Tokenrip](https://www.anchorterminal.com/compare/cognee-vs-tokenrip.md)
- [Cognee vs Zep](https://www.anchorterminal.com/compare/cognee-vs-zep.md)
- [Graphiti vs Tokenrip](https://www.anchorterminal.com/compare/graphiti-vs-tokenrip.md)
- [Graphiti vs Zep](https://www.anchorterminal.com/compare/graphiti-vs-zep.md)
- [Hindsight vs Tokenrip](https://www.anchorterminal.com/compare/hindsight-vs-tokenrip.md)
- [Hindsight vs Zep](https://www.anchorterminal.com/compare/hindsight-vs-zep.md)
- [Honcho vs Tokenrip](https://www.anchorterminal.com/compare/honcho-vs-tokenrip.md)
- [Honcho vs Zep](https://www.anchorterminal.com/compare/honcho-vs-zep.md)
- [Hy Memory vs Tokenrip](https://www.anchorterminal.com/compare/hy-memory-vs-tokenrip.md)
- [Hy Memory vs Zep](https://www.anchorterminal.com/compare/hy-memory-vs-zep.md)
- [LangMem vs Tokenrip](https://www.anchorterminal.com/compare/langmem-vs-tokenrip.md)
- [LangMem vs Zep](https://www.anchorterminal.com/compare/langmem-vs-zep.md)
- [LocalGhost vs Tokenrip](https://www.anchorterminal.com/compare/localghost-vs-tokenrip.md)
- [LocalGhost vs Zep](https://www.anchorterminal.com/compare/localghost-vs-zep.md)
- [Mem0 Platform + MCP vs Tokenrip](https://www.anchorterminal.com/compare/mem0-vs-tokenrip.md)
- [Mem0 Platform + MCP vs Zep](https://www.anchorterminal.com/compare/mem0-vs-zep.md)
- [Memory (MCP reference server) vs Tokenrip](https://www.anchorterminal.com/compare/memory-reference-server-vs-tokenrip.md)
- [Memory (MCP reference server) vs Zep](https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.md)
- [past.dev vs Tokenrip](https://www.anchorterminal.com/compare/past-dev-vs-tokenrip.md)
- [past.dev vs Zep](https://www.anchorterminal.com/compare/past-dev-vs-zep.md)
- [Supermemory API + MCP vs Tokenrip](https://www.anchorterminal.com/compare/supermemory-vs-tokenrip.md)
- [Supermemory API + MCP vs Zep](https://www.anchorterminal.com/compare/supermemory-vs-zep.md)
- [AI Memory vs Tokenrip](https://www.anchorterminal.com/compare/ai-memory-vs-tokenrip.md)
- [AI Memory vs Zep](https://www.anchorterminal.com/compare/ai-memory-vs-zep.md)
- [Context Mode Engine vs Tokenrip](https://www.anchorterminal.com/compare/context-mode-vs-tokenrip.md)
- [Context Mode Engine vs Zep](https://www.anchorterminal.com/compare/context-mode-vs-zep.md)
- [Graphicle vs Tokenrip](https://www.anchorterminal.com/compare/graphicle-vs-tokenrip.md)
- [Graphicle vs Zep](https://www.anchorterminal.com/compare/graphicle-vs-zep.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp