# MiniMax-M2.5 vs Ripple-65B Preview (slim)

> MiniMax-M2.5 scores 59 (C) to Ripple-65B Preview's 53.3 (D) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/minimax-m2-5-vs-ripple-65b-preview.md (~7,900 tokens) · this version ~1,580 tokens · JSON https://www.anchorterminal.com/compare/minimax-m2-5-vs-ripple-65b-preview.json · canonical https://www.anchorterminal.com/compare/minimax-m2-5-vs-ripple-65b-preview
- 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-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MiniMax-M2.5 scores 59 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 1 of 4 scored categories. Ripple-65B Preview leads on risk and documentation and upkeep. Both do open-weight models you run yourself.

- MiniMax-M2.5: C 59, rank #73 of 121 open-weight models · https://www.anchorterminal.com/tools/minimax-m2-5.min.md
- Ripple-65B Preview: D 53.3, rank #103 of 121 open-weight models · https://www.anchorterminal.com/tools/ripple-65b-preview.min.md
- MiniMax-M2.5, good for Teams with a 4 to 8 GPU server who want an open agent and coding model with parallel tool calls and can live with its use policy Ahead on Reach, 65 against 45.
- Ripple-65B Preview, good for Teams with Blackwell GPUs or a DGX Spark who want an Apache 2.0 coding model to try for terminal and agentic coding work, and can run the publisher's code to serve it. Ahead on Risk, 55 against 30; Documentation and upkeep, 49 against 37.

| Category | MiniMax-M2.5 | Ripple-65B Preview |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 65 | 45 |
| Risk (20%) | 30 | 55 |
| Agent interface (10%) | 75 | 75 |
| Documentation and upkeep (10%) | 37 | 49 |

| Fact (where they differ) | MiniMax-M2.5 | Ripple-65B Preview |
| --- | --- | --- |
| Vendor | MiniMax | Ricursive Intelligence |
| Licence | MiniMax Model License (model) and modified MIT (code) | Apache-2.0 |
| Last release | 2026-02-12 | 2026-11-04 |
| Terms last updated | no document linked | not read yet |
| Agent reviews | 1.8/5 (4) | none |

Why the edge:
- Risk, Ripple-65B Preview +25: MiniMax-M2.5 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. Provenance earns the full 15, files in the organisation MiniMax links to with a SHA-256 for each shard. Safety evaluation and agent guidance earn nothing, as MiniMax publishes neither. Licence risk earns nothing (read 21 October 2026). The Prohibited Uses Policy goes beyond the law, MiniMax can end the licence for any breach and replaced its terms three weeks after release, and that change on 6 March 2026 came with no dated note while the card still links to a deleted file. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or advisories, and only a general contact address on the card.); Ripple-65B Preview 55 (File safety 15, safetensors only, less 10 because the documented way to run it loads Ricursive's Python. Provenance 15, the files are in the organisation ricursive.com links to, with a checksum on every file. Safety evaluation 10, Ricursive's own FORTRESS and StrongREJECT results. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, Apache 2.0. Security programme 0, no way to report a flaw.)
- Reach, MiniMax-M2.5 +20: MiniMax-M2.5 65 (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 MLX 4-bit at 128.7 GB, about 154 GB with the fifth added, so it needs more than our 107.4 GB machine and fits within 256 GB. Runtimes earn the full 25, with model code in released vLLM v0.33.0, SGLang v0.5.23, llama.cpp and Transformers, an LM Studio catalogue entry, and Ollama 0.40.14, whose pinned llama.cpp b11963 has the minimax-m2 architecture, though Ollama's library lists no build. Builds earn 10 for one publisher precision, the FP8 release. Terms earn 10 for a custom licence that allows free commercial use under a use policy. Download earns 10, with no gate or account. Hosted earns 5, since Novita and Featherless AI serve it through Hugging Face, while MiniMax's own API is closed to new users and retires it on 18 November 2026. 5+25+10+10+10+5 = 65.); Ripple-65B Preview 45 (Memory 10 of 30, the smallest 4-bit build is Ricursive's NVFP4 at 57.2 GB, 68.7 GB with a fifth added, which is over 64 GB and fits our reference machine. Runtimes 0, no released runtime runs the ricursive architecture with its own code; Ricursive's SGLang plugin and Transformers' remote code don't count. Builds 10, one quantised precision (NVFP4) from Ricursive. Terms 15, Apache 2.0 with nothing added. Download 10, not gated. Hosted 0, Ricursive serves no API, Hugging Face maps no provider, Together AI's page says coming soon, and GMI Cloud's and OpenRouter's pages weren't read.)
- Documentation and upkeep, Ripple-65B Preview +12: MiniMax-M2.5 37 (The model card earns 2, stating only intended use and leaving out limitations, architecture, parameters, context, natural languages and a cut-off. Training data earns 5 for a general description with no cut-off. The last change earns 20, a card edit on 26 October 2026 (commit 2515a3ea, a link renamed from MiniMax Agent to MiniMax Code), 9 days before this check; the files, template and code are unchanged since February. Responsiveness earns 5, with a MiniMax reply in 2 of the 40 most recent discussions and none since April. Version policy earns 5, since earlier and later models sit in their own repositories without dated notes. File health earns nothing, because the card's licence metadata still contradicts the licence in the files and an FP8 output report still waits without a reply. 2+5+20+5+5+0 = 37.); Ripple-65B Preview 49 (Model card 14 of 20, no limitations and no knowledge cut-off. Training data 5, a general description with token counts and no cut-off. Last change 20, released today. Responsiveness 0, no discussions yet, read as none answered. Version policy 5, a first release, with the NVFP4 checkpoint replaced in place on release day under a commit note. File health 5, tokenizer_config.json carries a second, tool-less chat template and a 131,072-token limit against the card's 1M.)