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

DeepSeek-V3.2 vs North Mini Code 1.0

North Mini Code 1.0 scores 61 (C) on agent readiness against DeepSeek-V3.2's 58.6 (C), and leads in every scored category. 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

North Mini Code 1.0 C

Best for Developers who want a coding agent on their own GPU with a permissive licence

Ahead on

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

Watch for

No limitations, safety results, languages or data description on the card

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 North Mini Code 1.0 +25

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.

North Mini Code 1.0 85

Memory 25, the smallest build from Cohere is the w4a16 repository, 19.38 GB, and 19.38 GB × 1.2 = 23.3 GB, within 24 GB. Unsloth's GGUF isn't read for this line. Runtimes 20, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the cohere2_moe model, and llama.cpp b12242 has the cohere2moe architecture. Builds 15, Quantised builds from Cohere at two precisions, FP8 and 4-bit weights (w4a16), each in its own repository. Terms 15, Apache 2.0 in the metadata and on the card, 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. 25 + 20 + 15 + 15 + 10 + 0 = 85.

Agent interface North Mini Code 1.0 +25

DeepSeek-V3.2 60

The chat template earns 10, as the format exists only as Python code to run. The tool-calling format earns 10 because DeepSeek documents the DSML format in code but names no runtime parser, which only vLLM's own recipe does. Trained tool calling earns the full 20 for several calls in one block. Structured output earns nothing, as JSON output isn't documented. Reasoning control earns 10 for thinking or chat mode per request with reasoning_content returned. Context earns 10 for 128K trained tokens.

North Mini Code 1.0 85

Chat template 20, chat_template.jinja in the repository (12,397 characters). Tool-calling format 25, the card documents how tools are declared (JSON schema through the chat template), how the call and its thinking go back into the history and how results are appended, and names the cohere_command4 tool-call parser for vLLM, which released vLLM has. Trained tool calling 20, the card says the model was specifically trained with tool-use capabilities for agentic coding, with reinforcement learning on verifiable tasks, and the template renders every call in a turn with thinking between them. Structured output 0, JSON schema is for describing tools. Reasoning control 10, the template has a reasoning_effort setting, and the card names the cohere_command4 reasoning parser, which returns thinking apart from the answer. Context 10, 256K tokens per the card, with 64K of output, and 500,000 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Risk North Mini Code 1.0 +10

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.

North Mini Code 1.0 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in Cohere's verified CohereLabs organisation, which cohere.com links to per our other Cohere listings (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 5, Cohere's trust centre holds a responsible disclosure policy with a bug bounty, as recorded on our Cohere listings (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Score by category

CategoryWeight this runDeepSeek-V3.2North Mini Code 1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256085North Mini Code 1.0 +25
Risk20%205060North Mini Code 1.0 +10
Agent interface10%106085North Mini Code 1.0 +25
Documentation and upkeep10%103436North Mini Code 1.0 +2
Negative events≤1500
TotalC 58.6/100C 61/100

Facts side by side

FactDeepSeek-V3.2North Mini Code 1.0
KindOpen-weight modelOpen-weight model
VendorDeepSeekCohere
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-29
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.

North Mini Code 1.0

A coding agent model that fits one 24 GB GPU at 4 bits, trained for tool use, with a 256K context, Apache 2.0 and four released runtimes. It's a research release and reads like one: nothing on limitations, safety or data, the card's run instructions are out of date, and Cohere hasn't answered a question on the repository.

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

North Mini Code 1.0

  1. Serve it with vLLM 0.33.0 or later and --tool-call-parser cohere_command4 --reasoning-parser cohere_command4 --enable-auto-tool-choice, with cohere_melody installed
  2. Pass the model's thinking back with its tool calls on every turn. The card says results drop without it
  3. Describe tools in JSON schema and append tool results as a dictionary with the tool role
  4. Use temperature 1.0 and top_p 0.95
  5. For llama.cpp the GGUF files are Unsloth's or bartowski's conversions, not Cohere's
  6. It's text only. Don't send images

Questions

Which is better for AI agents, DeepSeek-V3.2 or North Mini Code 1.0?

North Mini Code 1.0 scores 61 (C) on agent readiness against DeepSeek-V3.2's 58.6 (C), and leads in every scored category.

Other comparisons with DeepSeek-V3.2 or North Mini Code 1.0

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.