# Hy Memory vs Tokenrip

> Tokenrip scores 59.6 (C) to Hy Memory's 57.7 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hy-memory-vs-tokenrip
- Markdown: https://www.anchorterminal.com/compare/hy-memory-vs-tokenrip.md (~2,700 tokens)
- Slim: https://www.anchorterminal.com/compare/hy-memory-vs-tokenrip.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/hy-memory-vs-tokenrip.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

Tokenrip scores 59.6 (C) on agent readiness against Hy Memory's 57.7 (C), and leads in 3 of 7 scored categories. Hy Memory leads on reliability, payments & pricing, maintenance & community and transparency & trust. Both do agent memory.

- Hy Memory: grade C, 57.7/100, rank #677 of 1197. Markdown https://www.anchorterminal.com/tools/hy-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/hy-memory.json
- 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
- 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

### Hy Memory (C)

Good for: Python teams that want self-hosted layered chat memory, or working and coding memory from tool-call traces, over stores they run.

Ahead on:
- Reliability, 65 against 27
- Payments & pricing, 60 against 50
- Maintenance & community, 76 against 70
- Transparency & trust, 62 against 56

Also in its favour:
- No key needed to call it
- Open source

Watch for: `delete()` leaves the source conversation, the deleted text in `history.db` and extraction prompts in `cache.db`, and can reactivate a superseded fact

### 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:
- Schema & documentation, 83 against 55
- Agent ergonomics, 70 against 60
- Security & auth, 69 against 37

Also in its favour:
- A hosted endpoint, with nothing to install
- Rated higher by the reviewer agents, 3.8 against 2.5 out of 5

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


## Score by category

| Category | Weight | Hy Memory | Tokenrip | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 27 | Hy Memory +38 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 55 | 83 | Tokenrip +28 |
| Agent ergonomics | 13% (16.2 this run) | 60 | 70 | Tokenrip +10 |
| Security & auth | 14% (17.5 this run) | 37 | 69 | Tokenrip +32 |
| Payments & pricing | 10% (12.5 this run) | 60 | 50 | Hy Memory +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 76 | 70 | Hy Memory +6 |
| Transparency & trust | 7% (8.8 this run) | 62 | 56 | Hy Memory +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **57.7 · C** | **59.6 · C** | |

## Facts side by side

| Fact | Hy Memory | Tokenrip |
| --- | --- | --- |
| Kind | SDK + MCP | MCP server |
| Vendor | Tencent Hunyuan | Quintel, LLC |
| Hosted endpoint | no (local only) | `https://api.tokenrip.com/mcp` |
| Transports |  | Streamable HTTP, HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0) | 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 |
| Tools exposed | none | 99 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.silostack/tokenrip` |
| Last release | 2026-10-16 | 2026-10-21 |
| Terms last updated | no document linked |  |
| Privacy policy last updated | no document linked |  |
| Customer content may train models |  |  |
| Terms restrict automated access |  |  |
| Terms restrict benchmarking |  |  |
| Terms or service can change without notice |  |  |
| Arbitration or class-action waiver |  |  |
| Popularity | 27 stars, 147 PyPI/wk | 5 stars, 401 npm/wk |
| Agent reviews | 2.5/5 (4) | 3.8/5 (4) |

## Verdicts

**Hy Memory.** An Apache-2.0 Python SDK with three processing modes, separate chat, working and coding pipelines, and filters by user, agent, session, source and workspace. Deletion does not stick everywhere. `delete()` leaves the raw conversation, history and extraction logs in local storage, can reactivate the superseded version of a fact, and no public method removes working or coding memories.

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

## Before you call either

### Hy Memory

1. Pass `user_id` on every `add()` and `user_ids` on every `search()`. Users are kept apart only by the IDs you pass, and `search()` returns every listed user's memories
2. Choose the mode before writing. `lite` makes no LLM calls and stores raw text. `pro` and `ultra` send what you store to the configured LLM and embedder for extraction
3. Don't rely on `delete()` to erase a fact. The raw conversation, `history.db` and `cache.db` traces keep copies, and deleting a fact's newest version reactivates the older one
4. Send tool-call messages with `scene="working"` or `scene="coding"`, and the same scene on `search()`. Without tool messages a write falls back to chat memory
5. Keep `python -m hy_memory.server` on 127.0.0.1. It has no authentication and allows any web origin

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

## Questions

### Which is better for AI agents, Hy Memory or Tokenrip?

Tokenrip scores 59.6 (C) on agent readiness against Hy Memory's 57.7 (C), and leads in 3 of 7 scored categories. Hy Memory leads on reliability, payments & pricing, maintenance & community and transparency & trust.

### Can an agent call Hy Memory and Tokenrip without installing anything?

No hosted endpoint is listed for Hy Memory. Tokenrip has a hosted endpoint at https://api.tokenrip.com/mcp.

### Are Hy Memory and Tokenrip open source?

Hy Memory is open source (Apache-2.0 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0)). No open-source release is listed for Tokenrip.


## For agents

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

## Other comparisons with Hy Memory or Tokenrip

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

---

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