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

DeepSeek-V3.2 vs Inkling

Inkling scores 64.2 (B) 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 and reach. 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 60
  • Reach, 60 against 50

Watch for

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

Inkling B

Best for Agents calling a hosted open multimodal model with audio input, or teams with a multi-GPU datacentre node who want to run it themselves.

Ahead on

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

Also in its favour

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

Watch for

The smallest build Thinking Machines publishes needs about 710 GB, beyond any single workstation

Score by category

CategoryWeight this runDeepSeek-V3.2InklingEdge
Capability35%356960DeepSeek-V3.2 +9
Reach25%256050DeepSeek-V3.2 +10
Risk20%205070Inkling +20
Agent interface10%106085Inkling +25
Documentation and upkeep10%103482Inkling +48
Negative events≤1500
TotalC 58.6/100B 64.2/100

Facts side by side

FactDeepSeek-V3.2Inkling
KindOpen-weight modelOpen-weight model
VendorDeepSeekThinking Machines Lab
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2025-12-012026-07-23
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)3/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.

Inkling

Thinking Machines' large multimodal generalist, stronger than Inkling-Small on factual recall by its own numbers. It needs about 710 GB of datacentre GPU memory even in NVFP4, so most agents will use a host such as Together AI or Tinker. The main risks are a use policy that binds on download and can change, and no outside 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

Inkling

  1. Unless you have a multi-GPU Blackwell or H200 node, call it through Together AI, Fireworks, DeepInfra or Tinker rather than starting it
  2. On 8 B200 GPUs, SGLang's recipe is sglang serve --trust-remote-code --model-path thinkingmachines/Inkling-NVFP4 --tp 8 --quantization modelopt_fp4 --enable-multimodal --reasoning-parser inkling --tool-call-parser inkling
  3. Use the inkling tool parser, not Hermes, and the inkling reasoning parser
  4. Pass reasoning_effort as none, minimal, low, medium, high (the default) or max, or a number from 0 to 0.99. The repository's template has no xhigh preset and raises an error for it, though Thinking Machines' docs list xhigh
  5. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  6. Audio should be 16 kHz WAV, ideally under 20 minutes, and images 40 to 4096 px a side, per the card
  7. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Questions

Which is better for AI agents, DeepSeek-V3.2 or Inkling?

Inkling scores 64.2 (B) 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 and reach.

Other comparisons with DeepSeek-V3.2 or Inkling

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.