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

Inkling-Small vs MiMo-V2.6 Distill Qwen 9B

Inkling-Small scores 66.5 (B) on agent readiness against MiMo-V2.6 Distill Qwen 9B's 61 (C), and leads in 3 of 4 scored categories. MiMo-V2.6 Distill Qwen 9B 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

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 60
  • Agent interface, 85 against 70
  • Documentation and upkeep, 82 against 40

Also in its favour

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

Watch for

The smallest build Thinking Machines publishes needs about 205 GB

MiMo-V2.6 Distill Qwen 9B C

Best for Researchers and agents that want a small coding and terminal-agent model to fine-tune further, on a 24 GB GPU or larger.

Ahead on

  • Reach, 70 against 55

Watch for

Only BF16 from Xiaomi, about 23 GB to run

Score by category

CategoryWeight this runInkling-SmallMiMo-V2.6 Distill Qwen 9BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255570MiMo-V2.6 Distill Qwen 9B +15
Risk20%207060Inkling-Small +10
Agent interface10%108570Inkling-Small +15
Documentation and upkeep10%108240Inkling-Small +42
Negative events≤1500
TotalB 66.5/100C 61/100

Facts side by side

FactInkling-SmallMiMo-V2.6 Distill Qwen 9B
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabXiaomi (MiMo team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT (metadata only, no LICENSE file); built on Qwen3.5-9B under Apache 2.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-312026-09-21
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.3/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.

MiMo-V2.6 Distill Qwen 9B

A 9B cousin tuned on MiMo-V2.6's agent work for coding, terminal tasks and visual coding, released as a base for RL research. It needs about 23 GB in BF16, since Xiaomi ships no smaller build. The main risks are no safety results while a seventh of its tuning is offensive security, and nobody at Xiaomi answering reports.

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

MiMo-V2.6 Distill Qwen 9B

  1. Serve it as the card does, sglang serve --model-path XiaomiMiMo/MiMo-V2.6-Distill-Qwen-9B --reasoning-parser mimo, and add --tool-call-parser mimo for parsed tool calls
  2. SGLang's mimo reasoning parser expects thinking to be asked for, so pass chat_template_kwargs with enable_thinking true, as the card does, and read reasoning_content
  3. Calls come back as function and parameter blocks inside tool_call, the same shape vLLM's and SGLang's qwen3_coder parsers read
  4. The generation config samples at temperature 0.6, top_k 20 and top_p 0.95
  5. Images and video go in through Qwen3.5's processor; the template's audio tokens have no audio encoder behind them
  6. The MTP head isn't in the files, so skip MTP speculative decoding even though config.json lists a layer
  7. It's an SFT checkpoint meant for further RL, and discussions report runaway generation on llama.cpp, so cap max_tokens

Questions

Which is better for AI agents, Inkling-Small or MiMo-V2.6 Distill Qwen 9B?

Inkling-Small scores 66.5 (B) on agent readiness against MiMo-V2.6 Distill Qwen 9B's 61 (C), and leads in 3 of 4 scored categories. MiMo-V2.6 Distill Qwen 9B leads on reach.

Other comparisons with Inkling-Small or MiMo-V2.6 Distill Qwen 9B

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.