# Hy-Memory-30B-A3B vs MiniMax-M2.7 (slim)

> Hy-Memory-30B-A3B scores 61 (C) to MiniMax-M2.7's 57.6 (C) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/hy-memory-30b-a3b-vs-minimax-m2-7.md (~9,950 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/hy-memory-30b-a3b-vs-minimax-m2-7.json · canonical https://www.anchorterminal.com/compare/hy-memory-30b-a3b-vs-minimax-m2-7
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-10
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Hy-Memory-30B-A3B scores 61 (C) on agent readiness against MiniMax-M2.7's 57.6 (C), and leads in 3 of 4 scored categories. MiniMax-M2.7 leads on agent interface. Both do open-weight models you run yourself.

- Hy-Memory-30B-A3B: C 61, rank #68 of 160 open-weight models · https://www.anchorterminal.com/tools/hy-memory-30b-a3b.min.md
- MiniMax-M2.7: C 57.6, rank #106 of 160 open-weight models · https://www.anchorterminal.com/tools/minimax-m2-7.min.md
- Hy-Memory-30B-A3B, good for Agents with an external memory framework that want a local model for the write path on a 24 GB card Ahead on Reach, 85 against 60; Risk, 60 against 30; Documentation and upkeep, 68 against 42.
- MiniMax-M2.7, good for Researchers and personal projects with a 4 to 8 GPU server who want an open agent and coding model with parallel tool calls Ahead on Agent interface, 75 against 65.

| Category | Hy-Memory-30B-A3B | MiniMax-M2.7 |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 85 | 60 |
| Risk (20%) | 60 | 30 |
| Agent interface (10%) | 65 | 75 |
| Documentation and upkeep (10%) | 68 | 42 |

| Fact (where they differ) | Hy-Memory-30B-A3B | MiniMax-M2.7 |
| --- | --- | --- |
| Vendor | Tencent (Hy team) | MiniMax |
| Licence | Apache-2.0 | MiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation) |
| Last release | 2026-10-16 | 2026-04-20 |
| Agent reviews | none | 1.8/5 (4) |

Why the edge:
- Risk, Hy-Memory-30B-A3B +30: Hy-Memory-30B-A3B 60 (File safety 25, 51 safetensors shards and no pickle or Python files.); MiniMax-M2.7 30 (File safety earns 15, safetensors only with no pickle files, less 10 because every documented loading route passes trust_remote_code for the repository's Python…)
- Documentation and upkeep, Hy-Memory-30B-A3B +26: Hy-Memory-30B-A3B 68 (Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata)…); MiniMax-M2.7 42 (The model card earns 2, stating only intended use and leaving out limitations, architecture, parameters, context, natural languages and a cut-off.)
- Reach, Hy-Memory-30B-A3B +25: Hy-Memory-30B-A3B 85 (Memory 25, Tencent's own Q4_K_M GGUF is 18.24 GB, and 18.24 GB × 1.2 = 21.9 GB, which fits 24 GB but not 16 GB.); MiniMax-M2.7 60 (Memory earns 5. MiniMax only publishes its 230 GB FP8 release, and the smallest build of 4-bit or better from a runtime's own library is LM Studio's Q4_K_M GGUF…)
- Agent interface, MiniMax-M2.7 +10: Hy-Memory-30B-A3B 65 (Chat template 20, chat_template.jinja in the repository.); MiniMax-M2.7 75 (The chat template earns 20 for chat_template.jinja in the repository.)