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

Granite 4.2 3B vs Nemotron 3 Super 120B A12B

Nemotron 3 Super 120B A12B scores 66.2 (B) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 3 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 75
  • Documentation and upkeep, 92 against 65

Also in its favour

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

Watch for

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

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

  • Capability, 54 against 21
  • Risk, 65 against 55
  • Agent interface, 90 against 85

Watch for

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

Score by category

CategoryWeight this runGranite 4.2 3BNemotron 3 Super 120B A12BEdge
Capability35%352154Nemotron 3 Super 120B A12B +33
Reach25%259575Granite 4.2 3B +20
Risk20%205565Nemotron 3 Super 120B A12B +10
Agent interface10%108590Nemotron 3 Super 120B A12B +5
Documentation and upkeep10%109265Granite 4.2 3B +27
Negative events≤1500
TotalC 59.8/100B 66.2/100

Facts side by side

FactGranite 4.2 3BNemotron 3 Super 120B A12B
KindOpen-weight modelOpen-weight model
VendorIBMNVIDIA
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-10-202026-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.8/5 (4)2.8/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.

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

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

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, Granite 4.2 3B or Nemotron 3 Super 120B A12B?

Nemotron 3 Super 120B A12B scores 66.2 (B) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 3 of 5 scored categories. Granite 4.2 3B leads on reach and documentation and upkeep.

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