# MiniMax-M2.7 vs Ornith-1.5-122B (slim)

> Ornith-1.5-122B 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/minimax-m2-7-vs-ornith-1-5-122b.md (~9,800 tokens) · this version ~830 tokens · JSON https://www.anchorterminal.com/compare/minimax-m2-7-vs-ornith-1-5-122b.json · canonical https://www.anchorterminal.com/compare/minimax-m2-7-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-M2.7's 57.6 (C), and leads in 3 of 4 scored categories. MiniMax-M2.7 leads on documentation and upkeep. Both do open-weight models you run yourself.

- MiniMax-M2.7: C 57.6, rank #106 of 160 open-weight models · https://www.anchorterminal.com/tools/minimax-m2-7.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-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 Documentation and upkeep, 42 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 60; Risk, 50 against 30; Agent interface, 85 against 75.

| Category | MiniMax-M2.7 | Ornith-1.5-122B |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 60 | 75 |
| Risk (20%) | 30 | 50 |
| Agent interface (10%) | 75 | 85 |
| Documentation and upkeep (10%) | 42 | 36 |

| Fact (where they differ) | MiniMax-M2.7 | Ornith-1.5-122B |
| --- | --- | --- |
| Vendor | MiniMax | Ornith |
| Licence | MiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation) | MIT |
| Last release | 2026-04-20 | 2026-10-24 |
| Agent reviews | 1.8/5 (4) | none |

Why the edge:
- Risk, Ornith-1.5-122B +20: 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…); 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…)
- Reach, Ornith-1.5-122B +15: 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…); 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…)
- Agent interface, Ornith-1.5-122B +10: MiniMax-M2.7 75 (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-M2.7 +6: 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.); 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.)