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

Darwin-36B-Opus vs Nemotron 3 Super 120B A12B

Nemotron 3 Super 120B A12B scores 66.2 (B) on agent readiness against Darwin-36B-Opus's 61 (C), and leads in 3 of 4 scored categories. Darwin-36B-Opus 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

Darwin-36B-Opus C

Best for Reasoning-heavy text tasks on a 32 GB machine or a single 80 GB GPU, where a disclosed training method isn't required

Ahead on

  • Reach, 80 against 75

Watch for

The merge method is proprietary and the current weights include an undescribed targeted refinement

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

  • Risk, 65 against 55
  • Agent interface, 90 against 70
  • Documentation and upkeep, 65 against 51

Watch for

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

Score by category

CategoryWeight this runDarwin-36B-OpusNemotron 3 Super 120B A12BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258075Darwin-36B-Opus +5
Risk20%205565Nemotron 3 Super 120B A12B +10
Agent interface10%107090Nemotron 3 Super 120B A12B +20
Documentation and upkeep10%105165Nemotron 3 Super 120B A12B +14
Negative events≤1500
TotalC 61/100B 66.2/100

Facts side by side

FactDarwin-36B-OpusNemotron 3 Super 120B A12B
KindOpen-weight modelOpen-weight model
VendorFINAL-Bench (VIDRAFT)NVIDIA
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-04-232026-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 reviews2.5/5 (4)2.8/5 (4)

Verdicts

Darwin-36B-Opus

A text-only reasoning cousin merged from Qwen3.6-35B-A3B and a reasoning-distilled fine-tune of it, with about 3B active parameters. It needs 32 GB for the publisher's 4-bit GGUF or about 83 GB in BF16, and runs in vLLM, SGLang, Transformers and llama.cpp. The main risks are an undisclosed merge method, a card that disagrees with its files, and no 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

Darwin-36B-Opus

  1. Quickest start is llama-server -hf FINAL-Bench/POCKET-35B-GGUF:Q4_K_M --jinja, about 21 GB of files
  2. On the reference machine BF16 fits, vllm serve FINAL-Bench/Darwin-36B-Opus --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parsers for Qwen3.6's format
  3. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  4. The card suggests temperature 0.6 to 0.7 and at least 5,120 new tokens for its think traces
  5. generation_config.json stops only on the end-of-text token, so add <|im_end|> as a stop token if a runtime keeps generating after the turn ends
  6. Text only, the vision encoder of Qwen3.6-35B-A3B isn't in these files
  7. Validate JSON output yourself, since structured output isn't documented

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, Darwin-36B-Opus or Nemotron 3 Super 120B A12B?

Nemotron 3 Super 120B A12B scores 66.2 (B) on agent readiness against Darwin-36B-Opus's 61 (C), and leads in 3 of 4 scored categories. Darwin-36B-Opus leads on reach.

Other comparisons with Darwin-36B-Opus 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.