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

Inkling-Small vs Nemotron 3 Super 120B A12B

Inkling-Small and Nemotron 3 Super 120B A12B score within a point of each other on agent readiness, 66.5 (B) and 66.2 (B). Nemotron 3 Super 120B A12B leads on reach and agent interface. 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

  • Capability, 63 against 54
  • Risk, 70 against 65
  • Documentation and upkeep, 82 against 65

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

Nemotron 3 Super 120B A12B B

Best for Agents on a 128 GB unified machine or Blackwell GPUs that want a long-context, tool-calling reasoning model with documented training data

Ahead on

  • Reach, 75 against 55
  • Agent interface, 90 against 85

Watch for

The card's serving commands pass --trust-remote-code

Score by category

CategoryWeight this runInkling-SmallNemotron 3 Super 120B A12BEdge
Capability35%356354Inkling-Small +9
Reach25%255575Nemotron 3 Super 120B A12B +20
Risk20%207065Inkling-Small +5
Agent interface10%108590Nemotron 3 Super 120B A12B +5
Documentation and upkeep10%108265Inkling-Small +17
Negative events≤1500
TotalB 66.5/100B 66.2/100

Facts side by side

FactInkling-SmallNemotron 3 Super 120B A12B
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabNVIDIA
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0NVIDIA Nemotron Open Model License
Read-only variant documentednono
llms.txtnono
Last release2026-07-312026-03-11
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.

Nemotron 3 Super 120B A12B

A long-context agent cousin with trained parallel tool calls, a reasoning switch and a full account of its training data, under a free commercial licence. It needs about 100 GB of GPU memory, a 128 GB unified machine or Blackwell hardware for NVIDIA's NVFP4. The main risks are serving commands that run repository code and no published 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

Nemotron 3 Super 120B A12B

  1. On the reference machine start it with ollama run nemotron-3-super, the 87 GB q4_K_M build, the only one that fits (about 104 GB with the margin)
  2. Raise the Strix Halo GPU memory limit first with amd-ttm --set 100, since the default of about 62.8 GiB is far below what it needs
  3. With vLLM serve it with --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder (SGLang uses --reasoning-parser nemotron_3)
  4. Use temperature=1.0 and top_p=0.95 for every task, as the card says
  5. Thinking is on by default. Pass enable_thinking: false or low_effort: true in chat_template_kwargs for short tasks
  6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, so a cut-off reasoning trace still returns content
  7. Raise context past 262,144 only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576)

Questions

Which is better for AI agents, Inkling-Small or Nemotron 3 Super 120B A12B?

Inkling-Small and Nemotron 3 Super 120B A12B score within a point of each other on agent readiness, 66.5 (B) and 66.2 (B). Nemotron 3 Super 120B A12B leads on reach and agent interface.

Other comparisons with Inkling-Small or Nemotron 3 Super 120B A12B

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.