# Inkling vs MiniCPM-V 4.7 1B (slim)

> Inkling scores 64.7 (B) to MiniCPM-V 4.7 1B's 61 (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-minicpm-v-4-7-1b.md (~9,450 tokens) · this version ~730 tokens · JSON https://www.anchorterminal.com/compare/inkling-vs-minicpm-v-4-7-1b.json · canonical https://www.anchorterminal.com/compare/inkling-vs-minicpm-v-4-7-1b
- 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)

Inkling scores 64.7 (B) on agent readiness against MiniCPM-V 4.7 1B's 61 (C), and leads in 3 of 4 scored categories. MiniCPM-V 4.7 1B leads on reach. Both do open-weight models you run yourself.

- Inkling: B 64.7, rank #19 of 160 open-weight models · https://www.anchorterminal.com/tools/inkling.min.md
- MiniCPM-V 4.7 1B: C 61, rank #76 of 160 open-weight models · https://www.anchorterminal.com/tools/minicpm-v-4-7-1b.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 Risk, 70 against 55; Agent interface, 85 against 70; Documentation and upkeep, 87 against 48.
- MiniCPM-V 4.7 1B, good for Agents that need a cheap local model to read screenshots, photos and short video on a phone, a laptop or beside a bigger model Ahead on Reach, 95 against 50.

| Category | Inkling | MiniCPM-V 4.7 1B |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 50 | 95 |
| Risk (20%) | 70 | 55 |
| Agent interface (10%) | 85 | 70 |
| Documentation and upkeep (10%) | 87 | 48 |

| Fact (where they differ) | Inkling | MiniCPM-V 4.7 1B |
| --- | --- | --- |
| Vendor | Thinking Machines Lab | OpenBMB |
| Last release | 2026-07-23 | 2026-10-30 |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Reach, MiniCPM-V 4.7 1B +45: Inkling 50 (Memory 0 of 30, the smallest 4-bit build is Thinking Machines' NVFP4 at 592.0 GB, about 710 GB with a fifth added, far above 256 GB.); MiniCPM-V 4.7 1B 95 (Memory 30, OpenBMB's own IQ4_XS GGUF is 0.64 GB, 1.54 GB with the 0.90 GB vision projector, and 1.54 GB × 1.2 = 1.9 GB, which fits 16 GB with room to spare.)
- Documentation and upkeep, Inkling +39: Inkling 87 (Model card 17 of 20, everything but a dated knowledge cut-off, counting Thinking Machines' own model card page.); MiniCPM-V 4.7 1B 48 (Model card 8, Intended use (image, multi-image and video understanding on device), architecture (early visual-token compression inside the vision encoder) and p…)
- Risk, Inkling +15: Inkling 70 (File safety 25, safetensors only and no repository code to run.); MiniCPM-V 4.7 1B 55 (File safety 25, safetensors in the main repository and the AWQ, GPTQ and int4 builds, GGUF in the GGUF build, with no .bin, .pt, .pth or .py files in the main r…)
- Agent interface, Inkling +15: Inkling 85 (Chat template 20, a Jinja file in the repository.); MiniCPM-V 4.7 1B 70 (Chat template 20, chat_template.jinja in the repository, 7,249 characters.)