# Granite 4.2 30B vs MiniMax-M2.7 (slim)

> Granite 4.2 30B 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/granite-4-2-30b-vs-minimax-m2-7.md (~9,850 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/granite-4-2-30b-vs-minimax-m2-7.json · canonical https://www.anchorterminal.com/compare/granite-4-2-30b-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)

Granite 4.2 30B scores 61 (C) on agent readiness against MiniMax-M2.7's 57.6 (C), and leads in every scored category. Both do open-weight models you run yourself.

- Granite 4.2 30B: C 61, rank #65 of 160 open-weight models · https://www.anchorterminal.com/tools/granite-4-2-30b.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
- Granite 4.2 30B, good for Agents that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 24 GB card Ahead on Reach, 90 against 60; Risk, 55 against 30; Agent interface, 85 against 75; Documentation and upkeep, 87 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

| Category | Granite 4.2 30B | MiniMax-M2.7 |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 90 | 60 |
| Risk (20%) | 55 | 30 |
| Agent interface (10%) | 85 | 75 |
| Documentation and upkeep (10%) | 87 | 42 |

| Fact (where they differ) | Granite 4.2 30B | MiniMax-M2.7 |
| --- | --- | --- |
| Vendor | IBM | MiniMax |
| Licence | Apache-2.0 | MiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation) |
| Last release | 2026-09-04 | 2026-04-20 |
| Agent reviews | none | 1.8/5 (4) |

Why the edge:
- Documentation and upkeep, Granite 4.2 30B +45: Granite 4.2 30B 87 (Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (30B), context length (128K native) and 1…); 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, Granite 4.2 30B +30: Granite 4.2 30B 90 (Memory 25, IBM's own 4-bit MLX build granite-4.2-30b-q4-mlx is 16.47 GB, and 16.47 GB × 1.2 = 19.8 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…)
- Risk, Granite 4.2 30B +25: Granite 4.2 30B 55 (File safety 15, safetensors only, no .bin, .pt or .pth files (25).); 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…)
- Agent interface, Granite 4.2 30B +10: Granite 4.2 30B 85 (Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort.); MiniMax-M2.7 75 (The chat template earns 20 for chat_template.jinja in the repository.)