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

Kimi K3 vs ThinkingCap (Qwen3.8 27B)

Kimi K3 scores 62.4 (B) on agent readiness against ThinkingCap (Qwen3.8 27B)'s 61 (C), and leads in 1 of 4 scored categories. ThinkingCap (Qwen3.8 27B) leads on reach, agent interface 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

  • Risk, 65 against 45

Watch for

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

ThinkingCap (Qwen3.8 27B) C

Best for Small teams and individuals running Qwen3.8-27B for agent or reasoning work who want shorter thinking traces on one 24 GB GPU or Mac.

Ahead on

  • Reach, 75 against 50
  • Agent interface, 70 against 65
  • Documentation and upkeep, 53 against 41

Watch for

PolyForm Small Business licence, free commercially only below 100 people and 1,000,000 USD (2019) revenue

Score by category

CategoryWeight this runKimi K3ThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255075ThinkingCap (Qwen3.8 27B) +25
Risk20%206545Kimi K3 +20
Agent interface10%106570ThinkingCap (Qwen3.8 27B) +5
Documentation and upkeep10%104153ThinkingCap (Qwen3.8 27B) +12
Negative events≤1500
TotalB 62.4/100C 61/100

Facts side by side

FactKimi K3ThinkingCap (Qwen3.8 27B)
KindOpen-weight modelOpen-weight model
VendorMoonshot AIBottleCap AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceKimi K3 License (modified MIT)PolyForm-Small-Business-1.0.0
Read-only variant documentednono
llms.txtnono
Last release2026-09-022026-10-06
Terms last updatedno document linkedno document linked
Privacy policy last updatedno 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.5/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.

ThinkingCap (Qwen3.8 27B)

A Qwen3.8-27B with shorter reasoning, for agent work where thinking tokens cost time, and BottleCap's 4-bit GGUF runs in about 19 GB. The main limits are the licence, which needs a paid licence above 100 people or 1,000,000 USD revenue, a gated main repository, and no safety results or training-data description.

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

ThinkingCap (Qwen3.8 27B)

  1. Check the licence first, an organisation with 100 or more people or 1,000,000 USD (2019) revenue needs a commercial licence from BottleCap
  2. For files without the gate use llama-server -hf bottlecapai/ThinkingCap-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 17.4 GB
  3. On vLLM use --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_xml, and on SGLang --tool-call-parser qwen3_coder
  4. Set reasoning_effort (xhigh, medium or low) in chat_template_kwargs, any other value makes the template raise an error
  5. Keep the base's sampling (temperature 1.0, top_p 0.95, top_k 20), the GGUF card says greedy decoding can loop
  6. The GGUFs carry an MTP head, and llama.cpp builds without MTP support for this architecture may refuse to load them with a missing blk.64 tensor

Questions

Which is better for AI agents, Kimi K3 or ThinkingCap (Qwen3.8 27B)?

Kimi K3 scores 62.4 (B) on agent readiness against ThinkingCap (Qwen3.8 27B)'s 61 (C), and leads in 1 of 4 scored categories. ThinkingCap (Qwen3.8 27B) leads on reach, agent interface and documentation and upkeep.

Other comparisons with Kimi K3 or ThinkingCap (Qwen3.8 27B)

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.