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

DeepSeek-V4-Flash-0731 vs Qwen3.5-0.8B

DeepSeek-V4-Flash-0731 scores 62.4 (B) on agent readiness against Qwen3.5-0.8B's 46.7 (D), and leads in 3 of 5 scored categories. Qwen3.5-0.8B leads on reach and risk. 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-V4-Flash-0731 B

Best for Agents or teams with a multi-GPU server, or a provider account, who want DeepSeek's V4 agent model under MIT with a 1M context

Ahead on

  • Capability, 66 against 17
  • Agent interface, 75 against 60
  • Documentation and upkeep, 43 against 37

Watch for

The smallest 4-bit build is 156.4 GB, so it needs about 188 GB and doesn't fit a 128 GB machine

Qwen3.5-0.8B D

Best for Builders who want a near-free local helper or fine-tuning base for narrow tasks on a phone-class device, laptop or CPU

Ahead on

  • Reach, 80 against 70
  • Risk, 55 against 50

Watch for

No quantised build from Alibaba and no inference provider found

Score by category

CategoryWeight this runDeepSeek-V4-Flash-0731Qwen3.5-0.8BEdge
Capability35%356617DeepSeek-V4-Flash-0731 +49
Reach25%257080Qwen3.5-0.8B +10
Risk20%205055Qwen3.5-0.8B +5
Agent interface10%107560DeepSeek-V4-Flash-0731 +15
Documentation and upkeep10%104337DeepSeek-V4-Flash-0731 +6
Negative events≤1500
TotalB 62.4/100D 46.7/100

Facts side by side

FactDeepSeek-V4-Flash-0731Qwen3.5-0.8B
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 release2026-07-312026-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.5/5 (4)2.8/5 (4)

Verdicts

DeepSeek-V4-Flash-0731

A long-context agent cousin under MIT with documented tool calls, three reasoning effort levels and support in every major runtime but Ollama. It needs about 190 to 200 GB of memory, though six inference providers serve it. The main risks are prompts built from DeepSeek's Python, no published safety results and no answers in its repository.

Qwen3.5-0.8B

A tiny vision-language cousin for prototypes, fine-tuning and light local steps such as routing, tagging or reading an image, running in under 2 GB in every major runtime under plain Apache 2.0. Keep thinking off, since the card warns it loops. The main risk is neglect, with no hosted option, safety results or answers from Alibaba since March.

Before you call either

DeepSeek-V4-Flash-0731

  1. vllm serve deepseek-ai/DeepSeek-V4-Flash-0731 --trust-remote-code --kv-cache-dtype fp8 --block-size 256 --data-parallel-size 4 --enable-expert-parallel --moe-backend deep_gemm_mega_moe --attention-config '{"use_fp4_indexer_cache": true}' --speculative-config '{"method":"dspark","num_speculative_tokens":7,"draft_sample_method":"greedy"}' --tokenizer-mode deepseek_v4 --tool-call-parser deepseek_v4 --enable-auto-tool-choice --reasoning-parser deepseek_v4 (the card's 4x GB300 example plus the parser flags from vLLM's recipe)
  2. Build prompts with encoding_dsv4.py, deepseek-recipe's V4 encoder or vLLM's --tokenizer-mode deepseek_v4, since the repository has no Jinja template
  3. Tool calls come back in a DSML tool_calls block with invoke elements, string parameters carry string="true" and JSON values string="false"
  4. Set temperature 1.0 and top_p 0.95 for agent work, and allow up to 384K output tokens at reasoning effort high or max
  5. Without the hardware, call it through a Hugging Face inference provider (Together, DeepInfra, Novita, Baseten, Scaleway, Featherless), not DeepSeek's API, where deepseek-v4-flash now means V4.1 Flash
  6. LM Studio's library build is a 156.4 GB MXFP4 GGUF and LM Studio states 156 GB minimum system memory

Qwen3.5-0.8B

  1. Smallest start is ollama run qwen3.5:0.8b, or qwen3.5:0.8b-q8_0 at 1.0 GB
  2. Full precision vllm serve Qwen/Qwen3.5-0.8B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Thinking is off by default; if you turn it on with "chat_template_kwargs": {"enable_thinking": true}, stream and cut off runaway output, since the card warns of thinking loops, and add --reasoning-parser qwen3 in vLLM or SGLang to split the reasoning out
  4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=1.0, top_p=1.0, top_k=20, presence_penalty=2.0 for text without thinking
  5. Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
  6. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, DeepSeek-V4-Flash-0731 or Qwen3.5-0.8B?

DeepSeek-V4-Flash-0731 scores 62.4 (B) on agent readiness against Qwen3.5-0.8B's 46.7 (D), and leads in 3 of 5 scored categories. Qwen3.5-0.8B leads on reach and risk.

Other comparisons with DeepSeek-V4-Flash-0731 or Qwen3.5-0.8B

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.