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

DeepSeek-V3.2 vs ZAYA1-8B

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

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

ZAYA1-8B C

Best for People who want a small, fast reasoning model for maths and code and can live without tool calling

Ahead on

  • Reach, 80 against 60
  • Risk, 55 against 50
  • Documentation and upkeep, 50 against 34

Watch for

Tool calling needs a parser that only Zyphra's vLLM fork has

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reach ZAYA1-8B +20

DeepSeek-V3.2 60

Memory earns nothing, because the only build from DeepSeek or a runtime's library is the 689.5 GB FP8 release, which needs about 827 GB with the fifth added. Runtimes earn the full 25 for released model code in vLLM, SGLang, llama.cpp and Transformers, and for Ollama 0.40.14, whose llama.cpp pin (b11963) carries the deepseek32 architecture with no gate in Ollama's server code, though its library entry stays retired; nothing from LM Studio. Builds earn 10 for the single FP8 precision DeepSeek publishes. Terms earn the full 15 for MIT with nothing added, and download the full 10 since the repository isn't gated. Hosted earns nothing, since DeepSeek's own API moved to V4 on 24 April 2026 and Hugging Face maps only DeepInfra as live for it on 4 November (Novita and Featherless in error), where the line needs two providers. Fireworks' model page says Serverless Not Supported and lists it only for on-demand deployment on dedicated GPUs, which is renting the hardware rather than calling a served model.

ZAYA1-8B 80

Memory 30, the smallest build from Zyphra is the MXFP4-Experts repository, 5.85 GB, and 5.85 GB × 1.2 = 7.0 GB, within 16 GB. Runtimes 10, Released Transformers 5.22.2 has the zaya model and SGLang 0.5.23 has srt/models/zaya.py. Builds 15, Quantised builds from Zyphra at two precisions, FP8 and MXFP4 for the experts, each in its own repository. Terms 15, Apache 2.0 in the card's metadata, an OSI licence with nothing added. Download 10, the Hub API reports gated false for the model and its builds on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it, and the card names no API. Zyphra's site lists a cloud product for its open models, which wasn't checked for this model. 30 + 10 + 15 + 15 + 10 + 0 = 80.

Documentation and upkeep ZAYA1-8B +16

DeepSeek-V3.2 34

The model card earns 14 when read with DeepSeek's own V3.2 model card PDF, which adds intended use and a parameter count, leaving languages and a knowledge cut-off missing. Training data earns 5, a general description with no cut-off. Last change earns 5, as nothing in the repository has changed since 1 December 2025 (338 days on 4 November) and DeepSeek's deepseek-recipe has no V3.2 code. Responsiveness earns nothing, with no reply from a deepseek-ai member in any of the 40 most recent discussions. Version policy earns 5 for earlier versions kept apart without dated notes. File health earns 5 because loading and parsing reports wait without a reply.

ZAYA1-8B 50

Model card 5, Intended use and the parameter counts are on the card. Training data 0, Nothing on the card about the training data. Last change 10, the main repository last changed on 26 June 2026 (the checkpoint reshaped for Transformers), 137 days before this check, and the quantised repositories on 2 July, 131 days. Responsiveness 20, Of the 16 most recent discussions that aren't pull requests (7 May to 14 August 2026), 10 have a reply from a Zyphra member, which is most. Version policy 5, the original checkpoint is kept as ZAYA1-8B-legacy and the card says so at the top, without a date. File health 10, Config, template and card agree on the architecture after the reshape. 5 + 0 + 10 + 20 + 5 + 10 = 50.

Risk ZAYA1-8B +5

DeepSeek-V3.2 50

File safety earns 15, safetensors only but 10 off because prompts are built by running DeepSeek's Python from the repository. Provenance earns the full 15 for the deepseek-ai organisation and a SHA-256 on every shard. Safety evaluation earns nothing, since no results are published anywhere. Agent guidance earns nothing, since the notes about the parser and the developer role are usage notes, read alike for all three DeepSeek listings. Licence risk keeps the full 15 for plain MIT. The security programme earns 5 for the security@deepseek.com reporting address on DeepSeek's site, with no public advisories.

ZAYA1-8B 55

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the Zyphra organisation, which the card ties to zyphra.com's blog post for the model (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or safety section, and nothing on prompt injection, instruction priority or what the model refuses. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 0, no way to report a flaw on the card, and www.zyphra.com has no security.txt. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Score by category

CategoryWeight this runDeepSeek-V3.2ZAYA1-8BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256080ZAYA1-8B +20
Risk20%205055ZAYA1-8B +5
Agent interface10%106060even
Documentation and upkeep10%103450ZAYA1-8B +16
Negative events≤1500
TotalC 58.6/100C 61/100

Facts side by side

FactDeepSeek-V3.2ZAYA1-8B
KindOpen-weight modelOpen-weight model
VendorDeepSeekZyphra
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-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
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.

ZAYA1-8B

A small reasoning model trained from scratch by one lab, with a clean licence, 4-bit and FP8 builds and a team that answers questions. It's the hardest of the small models to run: its own architecture, a card that points at forks, and tool calling that needs a parser no release has. Little on limits, data or safety.

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 deploy it on Fireworks 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

ZAYA1-8B

  1. Use it for reasoning, maths and code. Don't count on tool calling outside Zyphra's vLLM fork
  2. Run it with Transformers 5.22.2 or SGLang 0.5.23, which have the model built in
  3. Use temperature 1.0 and top_p 0.95 in general, and temperature 0.6 for agent and code work
  4. Download Zyphra/ZAYA1-8B, not the legacy repository, for the released runtimes
  5. The quantised repositories have no licence tag. The main one is Apache 2.0

Questions

Which is better for AI agents, DeepSeek-V3.2 or ZAYA1-8B?

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

Other comparisons with DeepSeek-V3.2 or ZAYA1-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.