# Granite 4.2 30B vs Kolibri-1 (slim)

> Granite 4.2 30B and Kolibri-1 score within a point of each other for open-weight models you run yourself, 61 and 61 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/granite-4-2-30b-vs-kolibri-1.md (~9,650 tokens) · this version ~730 tokens · JSON https://www.anchorterminal.com/compare/granite-4-2-30b-vs-kolibri-1.json · canonical https://www.anchorterminal.com/compare/granite-4-2-30b-vs-kolibri-1
- 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 and Kolibri-1 score within a point of each other on agent readiness, 61 (C) and 61 (C). Kolibri-1 leads on risk and agent interface. 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
- Kolibri-1: C 61, rank #44 of 160 open-weight models · https://www.anchorterminal.com/tools/kolibri-1.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 65; Documentation and upkeep, 87 against 70.
- Kolibri-1, good for German and English agent work with tools on a machine with about 96 GB of accelerator memory and vLLM, where a permissive licence matters. Ahead on Risk, 65 against 55; Agent interface, 90 against 85.

| Category | Granite 4.2 30B | Kolibri-1 |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 90 | 65 |
| Risk (20%) | 55 | 65 |
| Agent interface (10%) | 85 | 90 |
| Documentation and upkeep (10%) | 87 | 70 |

| Fact (where they differ) | Granite 4.2 30B | Kolibri-1 |
| --- | --- | --- |
| Vendor | IBM | Aleph Alpha |
| Last release | 2026-09-04 | 2026-10-19 |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Reach, Granite 4.2 30B +25: 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.); Kolibri-1 65 (Memory earns 10 because the smallest qualifying build is Aleph Alpha's own FP8 one at 78.8 GB, which comes to 94.6 GB with the fifth added and so fits only the…)
- Documentation and upkeep, Granite 4.2 30B +17: 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…); Kolibri-1 70 (The model card earns 20 with all seven items.)
- Risk, Kolibri-1 +10: Granite 4.2 30B 55 (File safety 15, safetensors only, no .bin, .pt or .pth files (25).); Kolibri-1 65 (File safety earns 25 for safetensors only, with no repository code run on load.)
- Agent interface, Kolibri-1 +5: 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.); Kolibri-1 90 (The chat template earns 20 as Jinja in tokenizer_config.json.)