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

Kimi K3 vs Qwen3.6-35B-A3B

Qwen3.6-35B-A3B and Kimi K3 score within a point of each other on agent readiness, 63.2 (B) and 62.4 (B). Kimi K3 leads on capability, risk and documentation and upkeep. 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

Kimi K3 B

Best for Teams with a multi-node GPU cluster who want an open 1M-context agent model for long coding and research work

Ahead on

  • Capability, 75 against 58
  • Risk, 65 against 55
  • Documentation and upkeep, 41 against 36

Watch for

1,561 GB of files at its smallest publisher build, far beyond any single machine

Qwen3.6-35B-A3B B

Best for Agents with a 32 GB or larger machine that want a quick, permissively licensed coding and tool-calling cousin with vision.

Ahead on

  • Reach, 85 against 50
  • Agent interface, 70 against 65

Also in its favour

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

Watch for

No safety evaluation, no agent-use guidance and no way to report a security flaw

Score by category

CategoryWeight this runKimi K3Qwen3.6-35B-A3BEdge
Capability35%357558Kimi K3 +17
Reach25%255085Qwen3.6-35B-A3B +35
Risk20%206555Kimi K3 +10
Agent interface10%106570Qwen3.6-35B-A3B +5
Documentation and upkeep10%104136Kimi K3 +5
Negative events≤1500
TotalB 62.4/100B 63.2/100

Facts side by side

FactKimi K3Qwen3.6-35B-A3B
KindOpen-weight modelOpen-weight model
VendorMoonshot AIAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceKimi K3 License (modified MIT)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-09-022026-04-16
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)2.8/5 (4)

Verdicts

Kimi K3

Kimi K3 is a 2.8T multimodal agent model with a 1M-token context, parallel tool calls and per-request effort, for long coding and research sessions. Its 1,561 GB of files need a multi-node GPU cluster, so most agents will call a hosted copy. The main risks are Moonshot's Python running at load and prompt time, and no answers in its repository.

Qwen3.6-35B-A3B

A fast mixture-of-experts cousin with 3B active parameters for coding and tool calling, with image and video input, in every major runtime under plain Apache 2.0. Ollama's 4-bit build needs about 28 GB. The main risk is that nobody at Alibaba maintains it, with no safety results, no security contact and no replies to tool-calling reports.

Before you call either

Kimi K3

  1. Start it with SGLang on a node of 8 B300s, sglang serve --trust-remote-code --model-path moonshotai/Kimi-K3 --tp-size 8 --context-length 65536 --mem-fraction-static 0.82 --reasoning-parser kimi_k3 --tool-call-parser kimi_k3 --port 30000
  2. Use the kimi_k3 tool-call and reasoning parsers in vLLM or SGLang, and validate tool-call arguments against the schema, since vLLM's recipe says K3 sometimes emits a format its parser doesn't expect
  3. Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
  4. Thinking is always on; set reasoning_effort to low or high when max is too slow
  5. Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
  6. Don't hand an ongoing session from another model to K3, and state boundaries in the system prompt, since Moonshot warns it can act on its own when intent is unclear
  7. Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page

Qwen3.6-35B-A3B

  1. Start it with ollama run qwen3.6:35b (Q4_K_M, 23 to 24 GB on disk, about 28 GB in memory)
  2. On the reference machine use vllm serve Qwen/Qwen3.6-35B-A3B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, BF16, since vLLM doesn't document FP8 compute on gfx1151
  3. Use the qwen3_coder tool-call parser and the qwen3 reasoning parser in vLLM 0.19.0 or SGLang 0.5.10 or later
  4. Thinking is on by default and /nothink isn't supported, so pass enable_thinking as false in chat_template_kwargs for short tasks, or preserve_thinking as true to keep earlier reasoning
  5. Card sampling for thinking is temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5, and for non-thinking temperature 0.7, top_p 0.8
  6. Keep at least 128K of context as the card advises, and turn on YaRN only beyond 262,144 tokens
  7. Validate JSON output yourself or use the runtime's guided decoding, since the model card documents none

Questions

Which is better for AI agents, Kimi K3 or Qwen3.6-35B-A3B?

Qwen3.6-35B-A3B and Kimi K3 score within a point of each other on agent readiness, 63.2 (B) and 62.4 (B). Kimi K3 leads on capability, risk and documentation and upkeep.

Other comparisons with Kimi K3 or Qwen3.6-35B-A3B

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.