Sign in

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

Kimi K3.1 Pro vs Qwen3-30B-A3B-Instruct-2507

Qwen3-30B-A3B-Instruct-2507 scores 56.6 (C) on agent readiness against Kimi K3.1 Pro's 48.6 (D), and leads in 3 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

Kimi K3.1 ProMoonshot AI · Open-weight model D48.6/100#151 of 160 open-weight models Qwen3-30B-A3B-Instruct-2507Alibaba (Qwen team) · Open-weight model C56.6/100#113 of 160 open-weight models

Which one, for what

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 26

Watch for

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

Qwen3-30B-A3B-Instruct-2507 C

Best for Agents that want an instruct model with tool calling on one 24 GB GPU or a 32 GB Mac, with a plain licence and a 262,144-token context.

Ahead on

  • Reach, 90 against 40
  • Risk, 55 against 50
  • Agent interface, 75 against 65

Watch for

No safety results, prompt-injection guidance or security contact

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 Qwen3-30B-A3B-Instruct-2507 +50

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.

Qwen3-30B-A3B-Instruct-2507 90

Memory 25 of 30, LM Studio's MLX 4-bit build is 17.2 GB and Ollama's 4-bit build 19 GB, 21 to 23 GB with a fifth added, which fits 24 GB. Runtimes 25, released Transformers, vLLM, SGLang and llama.cpp run the qwen3_moe architecture, and Ollama's library and LM Studio's catalogue carry it. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, Featherless AI on Hugging Face plus DekaLLM and SiliconFlow on OpenRouter serve it. On 4 November both repositories were still ungated with no file changed since 17 September 2025, and Featherless AI was still live in the Hub's provider mapping (OpenRouter's providers per 21 October). 25 + 25 + 10 + 15 + 10 + 5 = 90.

Documentation and upkeep Kimi K3.1 Pro +25

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.

Qwen3-30B-A3B-Instruct-2507 26

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, named languages and a knowledge cut-off aren't. Training data 5, the cited Qwen3 report describes the data in general terms without a cut-off. Last change 0, the files and card last changed on 17 September 2025 (Hub lastModified on 4 November), and QwenLM/Qwen3's commits since are documentation only (the newest 8 January 2026). Responsiveness 0, counted by script on 4 November, with 32 discussions, 23 not pull requests (the newest 18 June 2026), and the only reply from a Qwen organisation member is Haihao's on discussion 3 (30 July 2025), who isn't counted as the publisher's staff (the ehartford and danielhanchen reading). Version policy 5, the older Qwen3-30B-A3B stays in its own repository without a note. File health 5, the files agree with the card but reports about the 1M mode wait without a reply. 11 + 5 + 0 + 0 + 5 + 5 = 26.

Agent interface Qwen3-30B-A3B-Instruct-2507 +10

Kimi K3.1 Pro 65

Chat template 10, the format is only code to run. Tool-calling format 10, the parser is named in the runtimes' recipes and the card doesn't say how tools are declared. Trained tool calling 20, several calls a turn on Kimi K3's tools channel. Structured output 5, named among linked guides without the how. Reasoning control 10, reasoning_effort per request. Context 10, 1M tokens. 10 + 10 + 20 + 5 + 10 + 10 = 65.

Qwen3-30B-A3B-Instruct-2507 75

Chat template 20, a Jinja template in tokenizer_config.json. Tool-calling format 25, Qwen's own Function Calling guide documents the Hermes-style declaration and how calls come back, and names vLLM's hermes parser. Trained tool calling 20, the template allows one or more calls a turn. Structured output 0, not documented for the model, and Qwen's docs only point to vLLM's generic guided decoding. Reasoning control 0, this edition has no thinking. Context 10, 262,144 tokens native, with the 1M mode not counted. Template and config unchanged on 4 November. 20 + 25 + 20 + 0 + 0 + 10 = 75.

Risk Qwen3-30B-A3B-Instruct-2507 +5

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.

Qwen3-30B-A3B-Instruct-2507 55

File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, plain Apache 2.0 whose only change was the copyright year before release. Security programme 0, no security.txt, disclosure policy or security contact for Qwen was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent. Files unchanged on 4 November, and QwenLM/Qwen3 still has no SECURITY.md. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Score by category

CategoryWeight this runKimi K3.1 ProQwen3-30B-A3B-Instruct-2507Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254090Qwen3-30B-A3B-Instruct-2507 +50
Risk20%205055Qwen3-30B-A3B-Instruct-2507 +5
Agent interface10%106575Qwen3-30B-A3B-Instruct-2507 +10
Documentation and upkeep10%105126Kimi K3.1 Pro +25
Negative events≤1500
TotalD 48.6/100C 56.6/100

Facts side by side

FactKimi K3.1 ProQwen3-30B-A3B-Instruct-2507
KindOpen-weight modelOpen-weight model
VendorMoonshot AIAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceKimi K3.1 Pro License (modified MIT)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-052025-09-17
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/5 (4)

Verdicts

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.

Qwen3-30B-A3B-Instruct-2507

A general-purpose instruct model with 3.3B of 30.5B parameters active per token, for instruction following, tool calling and long documents without a thinking step. It needs about 21 to 23 GB at 4 bits under Apache 2.0, and providers host it. Its files haven't changed in over a year, Alibaba hasn't answered its discussions, and no safety results are published.

Before you call either

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

Qwen3-30B-A3B-Instruct-2507

  1. Quickest start is ollama run qwen3:30b-instruct, 19 GB. Plain qwen3:30b and qwen3:30b-a3b are the Thinking-2507 edition, not this one
  2. On our reference machine use BF16 with vllm serve Qwen/Qwen3-30B-A3B-Instruct-2507 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser hermes, 61 GB of weights fits the GPU share
  3. Use the hermes parser in vLLM or qwen25 in SGLang, the template emits JSON inside tool_call tags
  4. Don't pass enable_thinking, this edition never thinks and the card says the flag isn't needed
  5. Sampling per the card is temperature 0.7, top_p 0.8, top_k 20 and min_p 0, with presence_penalty up to 2 against repetition
  6. Leave config.json as it is unless you need more than 262,144 tokens, the 1M mode swaps in config_1m.json and runs one sequence at a time
  7. Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented

Questions

Which is better for AI agents, Kimi K3.1 Pro or Qwen3-30B-A3B-Instruct-2507?

Qwen3-30B-A3B-Instruct-2507 scores 56.6 (C) on agent readiness against Kimi K3.1 Pro's 48.6 (D), and leads in 3 of 4 scored categories. Kimi K3.1 Pro leads on documentation and upkeep.

Other comparisons with Kimi K3.1 Pro or Qwen3-30B-A3B-Instruct-2507

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.

Get an auditSee a sample report