# MiniMax-M3.1-Flash vs Ornith-1.5-122B (slim)

> Ornith-1.5-122B scores 61 (C) to MiniMax-M3.1-Flash's 54.3 (C) 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-ornith-1-5-122b.md (~10,100 tokens) · this version ~830 tokens · JSON https://www.anchorterminal.com/compare/minimax-m3-1-flash-vs-ornith-1-5-122b.json · canonical https://www.anchorterminal.com/compare/minimax-m3-1-flash-vs-ornith-1-5-122b
- 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)

Ornith-1.5-122B scores 61 (C) on agent readiness against MiniMax-M3.1-Flash's 54.3 (C), and leads in 3 of 4 scored categories. MiniMax-M3.1-Flash leads on documentation and upkeep. Both do open-weight models you run yourself.

- MiniMax-M3.1-Flash: C 54.3, rank #131 of 160 open-weight models · https://www.anchorterminal.com/tools/minimax-m3-1-flash.min.md
- Ornith-1.5-122B: C 61, rank #81 of 160 open-weight models · https://www.anchorterminal.com/tools/ornith-1-5-122b.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 Documentation and upkeep, 41 against 36.
- Ornith-1.5-122B, good for Local coding and terminal agents on a 128 GB unified-memory machine or a 96 GB GPU setup, where a clear licence file and an answering publisher aren't required Ahead on Reach, 75 against 55; Risk, 50 against 35; Agent interface, 85 against 70.

| Category | MiniMax-M3.1-Flash | Ornith-1.5-122B |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 55 | 75 |
| Risk (20%) | 35 | 50 |
| Agent interface (10%) | 70 | 85 |
| Documentation and upkeep (10%) | 41 | 36 |

| Fact (where they differ) | MiniMax-M3.1-Flash | Ornith-1.5-122B |
| --- | --- | --- |
| Vendor | MiniMax | Ornith |
| 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) | MIT |
| Last release | 2026-10-23 | 2026-10-24 |
| Agent reviews | 2.3/5 (4) | none |

Why the edge:
- Reach, Ornith-1.5-122B +20: MiniMax-M3.1-Flash 55 (Memory earns nothing.); Ornith-1.5-122B 75 (Memory 10, since Ornith's own MLX 4-bit build is 69.7 GB and needs about 83.6 GB with the fifth added, over 64 GB and inside the reference machine's 107.4 GB, a…)
- Risk, Ornith-1.5-122B +15: 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 processo…); Ornith-1.5-122B 50 (File safety 25, safetensors and GGUF only and no Python in any of Ornith's repositories for this size, so the card's --trust-remote-code flag loads nothing from…)
- Agent interface, Ornith-1.5-122B +15: MiniMax-M3.1-Flash 70 (The chat template earns 20 for chat_template.jinja in the repository.); Ornith-1.5-122B 85 (Chat template 20, a Jinja file in the repository.)
- Documentation and upkeep, MiniMax-M3.1-Flash +5: MiniMax-M3.1-Flash 41 (The model card earns 11, missing limitations, languages and a knowledge cut-off.); Ornith-1.5-122B 36 (Model card 11, it covers intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off.)