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

DeepSeek-V3.2 vs Nanbeige4.3-33B

Nanbeige4.3-33B scores 61 (C) on agent readiness against DeepSeek-V3.2's 58.6 (C), and leads in 3 of 4 scored categories. DeepSeek-V3.2 leads on reach. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 3341 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

  • Reach, 60 against 55

Watch for

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

Nanbeige4.3-33B C

Best for Agents with about 96 GB of GPU memory, or the 128 GB reference machine, that want an Apache-tagged 33B model for long coding and tool loops and can wait for independent results.

Ahead on

  • Risk, 60 against 50
  • Agent interface, 85 against 60
  • Documentation and upkeep, 56 against 34

Watch for

No independent benchmark result yet; every agentic number on the card is Nanbeige's own run

Score by category

CategoryWeight this runDeepSeek-V3.2Nanbeige4.3-33BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256055DeepSeek-V3.2 +5
Risk20%205060Nanbeige4.3-33B +10
Agent interface10%106085Nanbeige4.3-33B +25
Documentation and upkeep10%103456Nanbeige4.3-33B +22
Negative events≤1500
TotalC 58.6/100C 61/100

Facts side by side

FactDeepSeek-V3.2Nanbeige4.3-33B
KindOpen-weight modelOpen-weight model
VendorDeepSeekNanbeige LLM Lab (BOSS Zhipin)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0 (Hub metadata only; the repository has no LICENSE file)
Read-only variant documentednono
llms.txtnono
Last release2025-12-012026-10-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.3/5 (4)none

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.

Nanbeige4.3-33B

A dense 33B Llama-architecture cousin for long agentic coding and office tasks, with per-request thinking, XML tool calls that stock vLLM and SGLang parse, and 512K of context. It needs about 96 GB at BF16, as Nanbeige ships no quantised build. Its agentic results so far are Nanbeige's own, with no safety results, training data notes or licence file.

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

Nanbeige4.3-33B

  1. Serve with vllm serve Nanbeige/Nanbeige4.3-33B --enable-auto-tool-choice --reasoning-parser qwen3 --tool-call-parser qwen3_coder, as the card says, or SGLang with the same two parsers
  2. Keep tool_call_format at its default xml, since qwen3_coder parses that format; the json option writes Hermes-style JSON calls, which need a different parser such as vLLM's hermes
  3. Pass chat_template_kwargs {"preserve_thinking": true} for multi-turn tool use and coding, and {"enable_thinking": false} to skip reasoning, as the card recommends
  4. Use temperature 1.0, top_p 0.95 and up to 65,536 new tokens for agent work, and temperature 0.6 for reasoning and chat, per the card
  5. Send your own system prompt, since without one the template injects a Chinese identity line, or a Chinese tool-expert prompt when tools are passed
  6. Send one system message at the start only, as the template raises an error for a later one
  7. In plain Transformers pass use_cache=True to generate, since config.json and generation_config.json set it false; trust_remote_code isn't needed

Questions

Which is better for AI agents, DeepSeek-V3.2 or Nanbeige4.3-33B?

Nanbeige4.3-33B scores 61 (C) on agent readiness against DeepSeek-V3.2's 58.6 (C), and leads in 3 of 4 scored categories. DeepSeek-V3.2 leads on reach.

Other comparisons with DeepSeek-V3.2 or Nanbeige4.3-33B

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.