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

Inkling vs Inkling-Small

Inkling-Small scores 66.5 (B) on agent readiness against Inkling's 64.2 (B), and leads in 2 of 5 scored categories. 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 B

Best 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The smallest build Thinking Machines publishes needs about 710 GB, beyond any single workstation

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

  • Reach, 55 against 50

Also in its favour

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

Watch for

The smallest build Thinking Machines publishes needs about 205 GB

Score by category

CategoryWeight this runInklingInkling-SmallEdge
Capability35%356063Inkling-Small +3
Reach25%255055Inkling-Small +5
Risk20%207070even
Agent interface10%108585even
Documentation and upkeep10%108282even
Negative events≤1500
TotalB 64.2/100B 66.5/100

Facts side by side

FactInklingInkling-Small
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabThinking Machines Lab
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-232026-07-31
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 (4)3.5/5 (4)

Verdicts

Inkling

Thinking Machines' large multimodal generalist, stronger than Inkling-Small on factual recall by its own numbers. It needs about 710 GB of datacentre GPU memory even in NVFP4, so most agents will use a host such as Together AI or Tinker. The main risks are a use policy that binds on download and can change, and no outside safety results.

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.

Before you call either

Inkling

  1. Unless you have a multi-GPU Blackwell or H200 node, call it through Together AI, Fireworks, DeepInfra or Tinker rather than starting it
  2. On 8 B200 GPUs, SGLang's recipe is sglang serve --trust-remote-code --model-path thinkingmachines/Inkling-NVFP4 --tp 8 --quantization modelopt_fp4 --enable-multimodal --reasoning-parser inkling --tool-call-parser inkling
  3. Use the inkling tool parser, not Hermes, and the inkling reasoning parser
  4. 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 list xhigh
  5. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  6. Audio should be 16 kHz WAV, ideally under 20 minutes, and images 40 to 4096 px a side, per the card
  7. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

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

Questions

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

Inkling-Small scores 66.5 (B) on agent readiness against Inkling's 64.2 (B), and leads in 2 of 5 scored categories.

Other comparisons with Inkling or Inkling-Small

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.