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

Devstral Small 2 vs Kimi K3.1 Pro

Devstral Small 2 scores 61 (C) on agent readiness against Kimi K3.1 Pro's 48.6 (D), and leads in 2 of 4 scored categories. Kimi K3.1 Pro leads on documentation and upkeep. 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

Devstral Small 2 C

Best for Developers who want a dependable local coding agent on one consumer GPU or a 32 GB Mac

Ahead on

  • Reach, 90 against 40
  • Risk, 60 against 50

Watch for

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

Kimi K3.1 Pro D

Best for Operators with a multi-accelerator node who want Moonshot's newest open-weight model for coding and long agent sessions, and everyone else through an API

Ahead on

  • Documentation and upkeep, 51 against 46

Watch for

1,561 GB of files, so it needs a node of eight large accelerators at least

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 Devstral Small 2 +50

Devstral Small 2 90

Memory 25, the smallest build at 4 bits from a runtime's own library is Ollama's devstral-small-2 at Q4_K_M, 15 GB, and 15 GB × 1.2 = 18 GB, within 24 GB. Mistral's own FP8 files are 25.79 GB. Runtimes 25, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the mistral3 model, llama.cpp b12242 has the architecture with a GGUF from its own organisation, and Ollama's library has devstral-small-2. Builds 10, one quantised precision from Mistral, the FP8 weights it releases. Terms 15, Apache 2.0 in the card's metadata and text, an OSI licence with nothing added. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Mistral's own API serves Devstral Small 2: the card says the model is available through its API and points there when a local runtime underperforms. 25 + 25 + 10 + 15 + 10 + 5 = 90.

Kimi K3.1 Pro 40

Memory 0, the only build is Moonshot's 1,561 GB MXFP4 release, far above 256 GB. Runtimes 5, llama.cpp b12242 alone has the model code in a release, since vLLM's recipe needs 0.34.0 and SGLang's cookbook a branch. Builds 10, one precision. Terms 10, free commercial use below a model-as-a-service revenue threshold. Download 10, not gated. Hosted 5, Moonshot's API and Together serve it. 0 + 5 + 10 + 10 + 10 + 5 = 40.

Risk Devstral Small 2 +10

Devstral Small 2 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, files in Mistral's verified mistralai organisation, which Mistral's site links to per our Mistral Large 4 listing (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, mistral.ai's security.txt gives a security contact and a submission policy, as read for the Mistral Large 4 listing (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Kimi K3.1 Pro 50

File safety 15, safetensors only, less 10 for remote code and prompts built by the repository's script. Provenance 15, Moonshot's own organisation with a hash on every file. Safety evaluation 10, Moonshot's own cyber benchmark results and nobody else's yet. Agent guidance 0, none on the card. Licence risk 10, the revenue threshold. Security programme 0, no way to report a flaw found. 15 + 15 + 10 + 0 + 10 + 0 = 50.

Documentation and upkeep Kimi K3.1 Pro +5

Devstral Small 2 46

Model card 11, Intended use, the architecture, the parameters and the context are on the card. Training data 0, Nothing on the card about the training data. Last change 10, the last commit, on 15 July 2026, updated the files to match mistral-common, 118 days before this check and within 180. Responsiveness 10, Of the 23 most recent discussions that aren't pull requests (9 December 2025 to 6 November 2026), 11 have a reply from a mistralai member, which is some. Version policy 5, Devstral Small 1.1 stays in its own repository, which this card links as the predecessor, with no dated note on the older card that we read. File health 10, Config, template, tokenizer and card agree, and the June and July commits fixed stray tokens and brought the files in line with mistral-common. 11 + 0 + 10 + 10 + 5 + 10 = 46.

Kimi K3.1 Pro 51

Model card 11, no limitations, languages or cut-off. Training data 5, one general sentence. Last change 20, a commit on 5 November 2026. Responsiveness 0, none of the 8 newest discussions has a reply from Moonshot. Version policy 5, Kimi K3 keeps its repository and no dated note was found. File health 10, the files agree. 11 + 5 + 20 + 0 + 5 + 10 = 51.

Score by category

CategoryWeight this runDevstral Small 2Kimi K3.1 ProEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259040Devstral Small 2 +50
Risk20%206050Devstral Small 2 +10
Agent interface10%106565even
Documentation and upkeep10%104651Kimi K3.1 Pro +5
Negative events≤1500
TotalC 61/100D 48.6/100

Facts side by side

FactDevstral Small 2Kimi K3.1 Pro
KindOpen-weight modelOpen-weight model
VendorMistral AIMoonshot AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Kimi K3.1 Pro License (modified MIT)
Read-only variant documentednono
llms.txtnono
Last release2026-07-152026-11-05
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked

Verdicts

Devstral Small 2

The easy one to run: a 24B coding agent under Apache 2.0 that five runtimes carry, 15 GB at 4 bits in Ollama, with a 256K context, image input and well-documented tool calling. It's eleven months old, calls tools one at a time, has no reasoning mode, and its card says nothing on limits, safety or data.

Kimi K3.1 Pro

Moonshot's newest flagship, eight days old when read, for operators with a rack. Only llama.cpp has its model code in a release, with vLLM and SGLang support still on a release candidate and a branch. The licence is permissive below a revenue threshold, and Moonshot hasn't answered a discussion on the repository yet.

Before you call either

Devstral Small 2

  1. ollama run devstral-small-2 is the quickest start, at 15 GB
  2. On vLLM pass --tool-call-parser mistral --enable-auto-tool-choice
  3. Send the system prompt from CHAT_SYSTEM_PROMPT.txt in the repository. The card says results depend on it
  4. Use a low temperature. The repository's default is 0.15
  5. Plan for one tool call per turn
  6. The same model is on our Mistral API listing if you'd rather not host it

Kimi K3.1 Pro

  1. Use Moonshot's API or Together unless you have a node of eight B300-class accelerators
  2. With vLLM use 0.34.0 or later and the recipe's flags, --tool-call-parser kimi_k3 --reasoning-parser kimi_k3
  3. Pass the whole assistant message back in later turns, reasoning_content and tool_calls included, as the card requires
  4. Set reasoning_effort to low, high or max per request. Max is the default and thinking can't be turned off
  5. Kimi K3's model code doesn't load it, because the attention layers changed
  6. Validate JSON output yourself, since the card doesn't document structured output for the weights

Questions

Which is better for AI agents, Devstral Small 2 or Kimi K3.1 Pro?

Devstral Small 2 scores 61 (C) on agent readiness against Kimi K3.1 Pro's 48.6 (D), and leads in 2 of 4 scored categories. Kimi K3.1 Pro leads on documentation and upkeep.

Other comparisons with Devstral Small 2 or Kimi K3.1 Pro

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.