# Inkling vs MiniCPM5-2B (slim)

> Inkling scores 64.2 (B) to MiniCPM5-2B's 60.2 (C) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/inkling-vs-minicpm5-2b.md (~5,800 tokens) · this version ~430 tokens · JSON https://www.anchorterminal.com/compare/inkling-vs-minicpm5-2b.json · canonical https://www.anchorterminal.com/compare/inkling-vs-minicpm5-2b
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-21
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Inkling scores 64.2 (B) on agent readiness against MiniCPM5-2B's 60.2 (C), and leads in 3 of 5 scored categories. MiniCPM5-2B leads on reach and documentation and upkeep. Both do open-weight models you run yourself.

- Inkling: B 64.2, rank #20 of 100 open-weight models · https://www.anchorterminal.com/tools/inkling.min.md
- MiniCPM5-2B: C 60.2, rank #56 of 100 open-weight models · https://www.anchorterminal.com/tools/minicpm5-2b.min.md
- Inkling, good for Agents calling a hosted open multimodal model with audio input, or teams with a multi-GPU datacentre node who want to run it themselves. Ahead on Capability, 60 against 27; Risk, 70 against 55; Agent interface, 85 against 75.
- MiniCPM5-2B, good for On-device and laptop agents that want a 2 GB tool-calling helper with long context and open training data Ahead on Reach, 90 against 50; Documentation and upkeep, 97 against 82.

| Category | Inkling | MiniCPM5-2B |
| --- | --- | --- |
| Capability (35%) | 60 | 27 |
| Reach (25%) | 50 | 90 |
| Risk (20%) | 70 | 55 |
| Agent interface (10%) | 85 | 75 |
| Documentation and upkeep (10%) | 82 | 97 |

| Fact (where they differ) | Inkling | MiniCPM5-2B |
| --- | --- | --- |
| Vendor | Thinking Machines Lab | OpenBMB |
| Last release | 2026-07-23 | 2026-09-29 |