# MiniMax-M3.1-Flash vs Ripple-65B Preview (slim)

> MiniMax-M3.1-Flash scores 54.3 (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-m3-1-flash-vs-ripple-65b-preview.md (~8,450 tokens) · this version ~1,780 tokens · JSON https://www.anchorterminal.com/compare/minimax-m3-1-flash-vs-ripple-65b-preview.json · canonical https://www.anchorterminal.com/compare/minimax-m3-1-flash-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-M3.1-Flash scores 54.3 (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, agent interface and documentation and upkeep. Both do open-weight models you run yourself.

- MiniMax-M3.1-Flash: C 54.3, rank #100 of 121 open-weight models · https://www.anchorterminal.com/tools/minimax-m3-1-flash.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-M3.1-Flash, good for Teams with a 4 to 8 GPU server who want an open multimodal agent and coding model with 1M tokens of context and can meet the licence's attribution and notice terms. Ahead on Reach, 55 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 35; Agent interface, 75 against 70; Documentation and upkeep, 49 against 41.

| Category | MiniMax-M3.1-Flash | Ripple-65B Preview |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 55 | 45 |
| Risk (20%) | 35 | 55 |
| Agent interface (10%) | 70 | 75 |
| Documentation and upkeep (10%) | 41 | 49 |

| Fact (where they differ) | MiniMax-M3.1-Flash | Ripple-65B Preview |
| --- | --- | --- |
| Vendor | MiniMax | Ricursive Intelligence |
| Licence | MiniMax Community License (custom; commercial use needs a "Built with MiniMax M3.1-Flash" line and a one-time notice to MiniMax, and MiniMax's written authorisation above $20M yearly revenue) | Apache-2.0 |
| Last release | 2026-10-23 | 2026-11-04 |
| Terms last updated | no document linked | not read yet |
| Agent reviews | 2.3/5 (4) | none |

Why the edge:
- Risk, Ripple-65B Preview +20: MiniMax-M3.1-Flash 35 (File safety earns 15, safetensors only, less 10 because the SGLang route the card links passes trust_remote_code for the repository's configuration and processor code. 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; the launch post's security testing measured offensive capability, and the template's root role isn't documented as a trained hierarchy. Licence risk earns 5, after the military-use ban and the $20M threshold. The security programme earns nothing, with no security.txt, disclosure policy or advisories.); 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-M3.1-Flash +10: MiniMax-M3.1-Flash 55 (Memory earns nothing. MiniMax's only build is its 250 GB NVFP4 and MXFP8 release, about 300 GB with the fifth added, above 256 GB, and no runtime library has a local build. Runtimes earn 20. llama.cpp from b11861 runs it, Ollama v0.40.14 pins llama.cpp b11963 with the minimax-m3 architecture, vLLM v0.33.0 (tagged 1 November 2026) registers the architecture and meets its recipe's minimum version, and SGLang v0.5.23 (tagged 29 October) registers it with M3.1 processor code and tests, though its cookbook still points to a pull request. Transformers support is in progress per the card and LM Studio has no entry. Builds earn 10 for one publisher precision. Terms earn 10, since commercial use is free with attribution and a notice below $20M of yearly revenue. Download earns 10, with no gate. Hosted earns 5, since MiniMax's API and Novita serve it. 0 + 20 + 10 + 10 + 10 + 5 = 55.); 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 +8: MiniMax-M3.1-Flash 41 (The model card earns 11, missing limitations, languages and a knowledge cut-off. Training data earns nothing, as it isn't described. The last change earns 20, an evaluation-results commit of 30 October 2026 after the release commit of 23 October. Responsiveness earns nothing, with no MiniMax reply in nine discussions opened from 23 to 31 October. Version policy earns 5 for a first release in its own repository. File health earns 5, for the tokenizer's 40,960,000-token model_max_length against the 1M context, the Transformers library tag against the card, and an unanswered vLLM streaming report. 11 + 0 + 20 + 0 + 5 + 5 = 41.); 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.)
- Agent interface, Ripple-65B Preview +5: MiniMax-M3.1-Flash 70 (The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 10, since only the template shows the format and the parsers come from vLLM's and SGLang's own docs. Trained tool calling earns 20, with several invoke blocks in one call. Structured output earns nothing, as it isn't documented. Reasoning control earns 10, with reasoning_effort per request on the card and the reasoning in mm:think tags. Context earns 10 for 1,048,576 tokens with no position scaling.); Ripple-65B Preview 75 (Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, Ricursive's server README says how tools are declared and calls come back, with the ripple parser in SGLang 0.5.19. Trained tool calling 20, one or more calls a turn and agentic-coding RL. Structured output 0, not documented. Reasoning control 0, the template has no thinking switch or effort levels. Context 10, long-context training at 2M-token sequences for a stated 1M.)