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

Darwin-36B-Opus vs Qwen3.5-122B-A10B

Qwen3.5-122B-A10B scores 63.6 (B) on agent readiness against Darwin-36B-Opus's 61 (C), and leads in 0 of 4 scored categories. Darwin-36B-Opus leads on 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

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

  • Documentation and upkeep, 51 against 39

Watch for

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

Qwen3.5-122B-A10B B

Best for Agents with a 128 GB unified-memory machine or two large GPUs that want a capable vision-language model with a plain licence.

Also in its favour

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

Watch for

Too big for a single 64 GB machine even at 4 bits

Score by category

CategoryWeight this runDarwin-36B-OpusQwen3.5-122B-A10BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258080even
Risk20%205555even
Agent interface10%107070even
Documentation and upkeep10%105139Darwin-36B-Opus +12
Negative events≤1500
TotalC 61/100B 63.6/100

Facts side by side

FactDarwin-36B-OpusQwen3.5-122B-A10B
KindOpen-weight modelOpen-weight model
VendorFINAL-Bench (VIDRAFT)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-04-232026-02-24
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.

Qwen3.5-122B-A10B

A strong mid-size cousin for coding, agent steps and reading images or video, with thinking you can switch off per request. Alibaba's 4-bit build needs about 95 GB, which fits one 128 GB unified-memory machine, and several providers host it. The main risk is silence, with no safety results, agent guidance or answers from Alibaba.

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

Qwen3.5-122B-A10B

  1. Quickest start on a 128 GB machine is ollama run qwen3.5:122b (Q4_K_M, 81 GB of files, about 97 GB with context)
  2. Alibaba's 4-bit build serves with vllm serve Qwen/Qwen3.5-122B-A10B-GPTQ-Int4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder --quantization moe_wna16, though that kernel isn't documented for AMD gfx1151
  3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as the card's commands do
  4. Turn thinking off with "chat_template_kwargs": {"enable_thinking": false} in the request body, since it's on by default and /think and /nothink aren't supported
  5. Sampling per the card is temperature 0.6, top_p 0.95 and top_k 20 when thinking, and temperature 0.7, top_p 0.8, top_k 20 and presence_penalty 1.5 without
  6. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  7. Add --language-model-only in vLLM to skip the vision encoder and free memory for the KV cache when you only need text
  8. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, Darwin-36B-Opus or Qwen3.5-122B-A10B?

Qwen3.5-122B-A10B scores 63.6 (B) on agent readiness against Darwin-36B-Opus's 61 (C), and leads in 0 of 4 scored categories. Darwin-36B-Opus leads on documentation and upkeep.

Other comparisons with Darwin-36B-Opus or Qwen3.5-122B-A10B

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.