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

Darwin-36B-Opus vs Nemotron 3.5 Lightning 30B A3B

Nemotron 3.5 Lightning 30B A3B scores 64.2 (B) on agent readiness against Darwin-36B-Opus's 61 (C), and leads in every scored category. 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

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

Watch for

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

Nemotron 3.5 Lightning 30B A3B B

Best for Agents on one 24 to 32 GB GPU or Mac that want a fast tool-calling reasoning model with long context and a permissive licence

Ahead on

  • Reach, 85 against 80
  • Risk, 75 against 55
  • Agent interface, 90 against 70
  • Documentation and upkeep, 70 against 51

Also in its favour

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

Watch for

No safety evaluation results published

Score by category

CategoryWeight this runDarwin-36B-OpusNemotron 3.5 Lightning 30B A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258085Nemotron 3.5 Lightning 30B A3B +5
Risk20%205575Nemotron 3.5 Lightning 30B A3B +20
Agent interface10%107090Nemotron 3.5 Lightning 30B A3B +20
Documentation and upkeep10%105170Nemotron 3.5 Lightning 30B A3B +19
Negative events≤1500
TotalC 61/100B 64.2/100

Facts side by side

FactDarwin-36B-OpusNemotron 3.5 Lightning 30B A3B
KindOpen-weight modelOpen-weight model
VendorFINAL-Bench (VIDRAFT)NVIDIA
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0OpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-04-232026-08-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)3/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.5 Lightning 30B A3B

A small agent cousin, 3B active parameters, with trained parallel tool calls, a thinking switch and up to 1M tokens of context, under a permissive licence. It runs in about 23 GB from the GGUF or Ollama builds, and NVIDIA's NVFP4 build needs NVIDIA GPUs. The main risks are no published safety results and one answered question across two repositories.

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.5 Lightning 30B A3B

  1. Quickest start is ollama run nemotron-3.5-lightning, about 19 to 25 GB of files depending on the platform
  2. On the reference machine use llama-server -hf ggml-org/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-GGUF:Q4_0 --jinja, since the card's Q4_K_M tag doesn't exist there and NVFP4 needs NVIDIA GPUs
  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, as the card says
  5. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false for short tasks
  6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, which vLLM's nemotron_v3 parser reads so a cut-off reasoning trace still returns content
  7. Go past 262,144 tokens only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576) and enough memory

Questions

Which is better for AI agents, Darwin-36B-Opus or Nemotron 3.5 Lightning 30B A3B?

Nemotron 3.5 Lightning 30B A3B scores 64.2 (B) on agent readiness against Darwin-36B-Opus's 61 (C), and leads in every scored category.

Other comparisons with Darwin-36B-Opus or Nemotron 3.5 Lightning 30B A3B

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.