Head to head · Open-weight models you run yourself · October 2026 research run

Inkling-Small vs MiniCPM-o 4.5

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

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Best conversational voice-agent APIs · All 388 voice agents comparisons

Which one, for what

Inkling-Small B

Best for Teams with 256 GB or more of datacentre GPU memory who want an open multimodal agent model with audio input and adjustable thinking.

Ahead on

  • Risk, 70 against 40
  • Agent interface, 85 against 35
  • Documentation and upkeep, 82 against 66

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.8 out of 5

Watch for

The smallest build Thinking Machines publishes needs about 205 GB

MiniCPM-o 4.5 C

Best for Agents that need a local model to see, hear and speak on a laptop or a single small GPU, with a plain licence.

Ahead on

  • Reach, 90 against 55

Watch for

Speech output and full duplex need trust_remote_code with Transformers 4.51.0 or OpenBMB's llama.cpp-omni

Score by category

CategoryWeight this runInkling-SmallMiniCPM-o 4.5Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255590MiniCPM-o 4.5 +35
Risk20%207040Inkling-Small +30
Agent interface10%108535Inkling-Small +50
Documentation and upkeep10%108266Inkling-Small +16
Negative events≤1500
TotalB 66.5/100C 61/100

Facts side by side

FactInkling-SmallMiniCPM-o 4.5
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabOpenBMB
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0; built from Qwen3-8B, SigLIP2, Whisper-medium and CosyVoice2, all Apache 2.0 on their Hub cards
Read-only variant documentednono
llms.txtnono
Last release2026-07-312026-10-16
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.5/5 (4)2.8/5 (4)

Verdicts

Inkling-Small

A mixture-of-experts generalist with images and audio in, several tool calls a turn and per-request thinking effort. It needs about 205 GB for Thinking Machines' NVFP4 build on recent NVIDIA or AMD datacentre GPUs, and Tinker or DeepInfra host it. The main risks are a use policy that binds on download and can change, and no outside safety results.

MiniCPM-o 4.5

A small omni cousin that sees, listens and talks back, with full-duplex speech and voice cloning, in about 7 GB at 4-bit through llama.cpp or Ollama for text and images. Speech output needs OpenBMB's remote code or llama.cpp-omni, and 28 GB of GPU for the full demo. The main risks are repository code and pickle files and no safety results.

Before you call either

Inkling-Small

  1. Start the NVFP4 build with SGLang's recipe, sglang serve --trust-remote-code --model-path thinkingmachines/Inkling-Small-NVFP4 --tp 8 --enable-multimodal --reasoning-parser inkling --tool-call-parser inkling, on Blackwell for W4A4
  2. Use the inkling tool and reasoning parsers in vLLM or SGLang, or Thinking Machines' tml-renderers package to render prompts and parse calls yourself
  3. Pass reasoning_effort as none, minimal, low, medium, high (the default) or max, or a number from 0 to 0.99. The repository's template has no xhigh preset and raises an error for it, though Thinking Machines' docs and SGLang's cookbook list xhigh
  4. Effort none conditions the model toward no reasoning but doesn't forbid it, and higher effort needs a larger max_tokens
  5. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  6. Images should be 40 to 4096 px a side and audio 16 kHz WAV under two minutes, per the card
  7. Use guided decoding or validate JSON yourself, since structured output isn't documented
  8. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

MiniCPM-o 4.5

  1. Quickest start for text and images is ollama run openbmb/minicpm-o4.5, about 6 GB
  2. With vLLM 0.16.0 or later pass --trust-remote-code, and send stop_token_ids [151643, 151645] as OpenBMB's guide does
  3. vLLM, llama.cpp and Ollama return text only; for speech out use the card's Transformers 4.51.0 code or OpenBMB's llama.cpp-omni
  4. In llama.cpp pass both the language GGUF and MiniCPM-o-4_5-vision-F16.gguf with --mmproj, and use --jinja --reasoning-budget 0 to turn thinking off
  5. Keep prompts within 40,960 tokens
  6. Don't rely on tool calls or JSON output, neither is documented; validate any you get

Questions

Which is better for AI agents, Inkling-Small or MiniCPM-o 4.5?

Inkling-Small scores 66.5 (B) on agent readiness against MiniCPM-o 4.5's 61 (C), and leads in 3 of 4 scored categories. MiniCPM-o 4.5 leads on reach.

Other comparisons with Inkling-Small or MiniCPM-o 4.5

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.