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

Granite 4.2 3B vs Inkling-Small

Inkling-Small scores 66.5 (B) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 2 of 5 scored categories. Granite 4.2 3B leads on reach and documentation and upkeep. 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

Granite 4.2 3B C

Best for Agents on small hardware that want a permissive reasoning model for tool calls and coding, with thinking they can switch off

Ahead on

  • Reach, 95 against 55
  • Documentation and upkeep, 92 against 82

Watch for

No safety results published for 4.2, and only general safety cautions

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 21
  • Risk, 70 against 55

Watch for

The smallest build Thinking Machines publishes needs about 205 GB

Score by category

CategoryWeight this runGranite 4.2 3BInkling-SmallEdge
Capability35%352163Inkling-Small +42
Reach25%259555Granite 4.2 3B +40
Risk20%205570Inkling-Small +15
Agent interface10%108585even
Documentation and upkeep10%109282Granite 4.2 3B +10
Negative events≤1500
TotalC 59.8/100B 66.5/100

Facts side by side

FactGranite 4.2 3BInkling-Small
KindOpen-weight modelOpen-weight model
VendorIBMThinking 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-10-202026-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.8/5 (4)3.5/5 (4)

Verdicts

Granite 4.2 3B

A small reasoning cousin for tool calls, coding and multilingual chat that runs almost anywhere, from a 2.2 GB Ollama build to vLLM and SGLang, under plain Apache 2.0 with signed files and a dataset disclosure. Thinking turns off or shortens per request. It has no published safety results and no documented JSON mode.

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

Granite 4.2 3B

  1. Start it with ollama run granite4.2:3b; set options.num_ctx in the request, since Ollama's default context is short and the model takes up to 131,072
  2. With vLLM 0.32.0 or later, serve ibm-granite/granite-4.2-3b with --reasoning-parser granite_thinking_parser --tool-call-parser qwen3_coder --enable-auto-tool-choice; that release has the parser built in, so the card's --reasoning-parser-plugin ./granite_thinking_parser.py isn't needed
  3. With SGLang 0.5.18 or later, --reasoning-parser auto --tool-call-parser auto resolve to IBM's recommended parsers, and the reasoning comes back in reasoning_content
  4. Use temperature 1.0 and top_p 0.95 for every mode, as IBM requires
  5. Pass enable_thinking false for direct answers or low_effort true for short reasoning, through chat_template_kwargs on an OpenAI-compatible server
  6. Earlier turns' thinking is stripped by default (truncate_history_thinking), so pass it false to keep reasoning in multi-turn history
  7. For JSON, use the runtime's guided decoding, since IBM documents no JSON mode for 4.2
  8. Verify the files with python -m model_signing verify sigstore and IBM's identity, per IBM's signature guide

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, Granite 4.2 3B or Inkling-Small?

Inkling-Small scores 66.5 (B) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 2 of 5 scored categories. Granite 4.2 3B leads on reach and documentation and upkeep.

Other comparisons with Granite 4.2 3B 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.