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

DeepSeek-V3.2 vs Qwen3.5-9B

Qwen3.5-9B scores 60.5 (C) on agent readiness against DeepSeek-V3.2's 58.6 (C), and leads in 3 of 5 scored categories. DeepSeek-V3.2 leads on capability. 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

DeepSeek-V3.2 C

Best for Teams with an eight-GPU server who want an MIT agent model with broad runtime support, or agents calling it through a hosted provider

Ahead on

  • Capability, 69 against 51

Watch for

689.5 GB of FP8 files and no smaller build from DeepSeek or a runtime library, far beyond 107.4 GB

Qwen3.5-9B C

Best for Agents that want a small multimodal tool-calling cousin on a laptop or a 16 GB GPU, under a plain licence

Ahead on

  • Reach, 85 against 60
  • Risk, 55 against 50
  • Agent interface, 70 against 60

Watch for

No quantised build from Qwen itself

Score by category

CategoryWeight this runDeepSeek-V3.2Qwen3.5-9BEdge
Capability35%356951DeepSeek-V3.2 +18
Reach25%256085Qwen3.5-9B +25
Risk20%205055Qwen3.5-9B +5
Agent interface10%106070Qwen3.5-9B +10
Documentation and upkeep10%103434even
Negative events≤1500
TotalC 58.6/100C 60.5/100

Facts side by side

FactDeepSeek-V3.2Qwen3.5-9B
KindOpen-weight modelOpen-weight model
VendorDeepSeekAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2025-12-012026-03-02
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.3/5 (4)2.5/5 (4)

Verdicts

DeepSeek-V3.2

DeepSeek-V3.2 is an MIT-licensed reasoning model trained for parallel tool calls, with thinking chosen per request, for long agent work. It needs about 690 GB of FP8 files, eight 80 GB GPUs in vLLM's recipe and prompts built from DeepSeek's Python. The main risk is neglect, with no file changes since December 2025 and no safety evaluation.

Qwen3.5-9B

A small dense vision-language cousin with trained tool calling, switchable thinking and a 262,144-token context, for local agent subtasks. Ollama's 4-bit build needs about 8 GB and the BF16 files about 24 GB, in every major runtime. The main risk is neglect, with no file changes since March, no replies from Qwen to reports and no safety results.

Before you call either

DeepSeek-V3.2

  1. Start it with vLLM's recipe, vllm serve deepseek-ai/DeepSeek-V3.2 --tensor-parallel-size 8 --tokenizer-mode deepseek_v32 --enable-auto-tool-choice --tool-call-parser deepseek_v32 --reasoning-parser deepseek_v3
  2. It doesn't fit the 107.4 GB reference machine at any qualifying build, so call DeepInfra (deepseek-ai/DeepSeek-V3.2) or SambaNova (DeepSeek-V3.2) instead
  3. Outside vLLM, build prompts with encoding/encoding_dsv32.py and wrap parse_message_from_completion_text in error handling, since DeepSeek says it handles well-formed output only
  4. Pick thinking or chat with thinking_mode, and read the reasoning from reasoning_content
  5. Send developer messages only for search-agent prompts, the only use DeepSeek gives that role
  6. Use temperature 1.0 and top_p 0.95 and keep prompts within 128K tokens

Qwen3.5-9B

  1. Smallest start is ollama run qwen3.5:9b (6.6 GB, q4_k_m)
  2. On vLLM run vllm serve Qwen/Qwen3.5-9B --port 8000 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, or tool calls come back as text
  3. Tool calls use the XML style <tool_call><function=name><parameter=x>, not Hermes JSON, so use the qwen3_coder parser and not hermes
  4. Thinking is on by default; pass chat_template_kwargs with enable_thinking false for short tasks, since /nothink isn't supported
  5. There's no generation_config.json, so pass sampling yourself, temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5 when thinking, or 0.7, 0.8, 20, 1.5 without
  6. Keep at least 128K of context when thinking, and turn on YaRN only beyond 262,144 tokens
  7. Validate JSON output yourself or use the runtime's guided decoding

Questions

Which is better for AI agents, DeepSeek-V3.2 or Qwen3.5-9B?

Qwen3.5-9B scores 60.5 (C) on agent readiness against DeepSeek-V3.2's 58.6 (C), and leads in 3 of 5 scored categories. DeepSeek-V3.2 leads on capability.

Other comparisons with DeepSeek-V3.2 or Qwen3.5-9B

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.