Qwen3.5 35B A3B Base vs Kimi K3
At a Glance
| Compare | Kimi K3Moonshot AI | |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| IntelligenceHigher is better · MM Intelligence v2.5 | UnrankedNot in the 46-model eligible cohort | #17 of 4670.3 score · 3/3 sources · complete |
| CostLower is better · Published-token output estimate | UnrankedNot in the 44-model eligible cohort | #30 of 44$0.194 per LiveBench case |
| EfficiencyHigher is better · MM Efficiency v1.5 | UnrankedNot in the 38-model eligible cohort | #21 of 3852.5 score · 3/3 sources · complete |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $2.85Deepinfra ↗ · Sep 22, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $14.25Deepinfra ↗ · Sep 22, 2026 |
| Context windowMaximum documented tokens | 262K | 1,049K |
| Model facts checked | Aug 28, 2026View model evidence → | Aug 28, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | Qwen3.5-35B-A3B-Base | Kimi-K3 |
|---|---|---|
| Developer | Qwen | Moonshot AI |
| Family | Qwen3 5 35b A3b Base | Kimi K3 |
| Model | Qwen3.5-35B-A3B-Base | Kimi-K3 |
| Version | Qwen3.5-35B-A3B-Base | Kimi-K3 |
| Lifecycle | active | active |
| Released | Unknown | 2026-07-16 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image | Text, Image |
| Output modalities | Text | Text |
| Context window | 262K | 1,049K |
| Total parameters | 36B | 2.8T |
| Active parameters | 3B | 104B |
| License | apache-2.0 | other |
| Open weights | Yes | Yes |
| API available | Unknown | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Unknown | Deepinfra (Standard), Fireworks Ai (Standard), Hugging Face (Standard), Openrouter (Standard), Together Ai (Standard) |
| Capabilities | chat, generation, tools | chat, generation, reasoning |
Qwen3.5 35B A3B Base Capabilities
Kimi K3 Capabilities
Primary Evidence
Sources and Freshness
Questions
Qwen3.5 35B A3B Base vs Kimi K3 FAQs
Is Qwen3.5 35B A3B Base or Kimi K3 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Qwen3.5 35B A3B Base and Kimi K3, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Qwen3.5 35B A3B Base or Kimi K3?+
Only Kimi K3 has a directly sourced input price: $2.85 per million tokens. Only Kimi K3 has a directly sourced output price: $14.25 per million tokens.
Which has a larger context window, Qwen3.5 35B A3B Base or Kimi K3?+
Kimi K3 has the larger sourced context window. Qwen3.5 35B A3B Base supports 262K and Kimi K3 supports 1,049K.
Which performs better in benchmarks, Qwen3.5 35B A3B Base or Kimi K3?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Qwen3.5 35B A3B Base or Kimi K3 be self-hosted?+
Both models have the same recorded self-hosting status: supported. Qwen3.5 35B A3B Base is open weight; Kimi K3 is open weight.
Can Qwen3.5 35B A3B Base and Kimi K3 understand images?+
Qwen3.5 35B A3B Base is documented with image input; Kimi K3 is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Qwen3.5 35B A3B Base or Kimi K3?+
Neither has a larger sourced maximum output. Qwen3.5 35B A3B Base is — and Kimi K3 is —.
Do Qwen3.5 35B A3B Base and Kimi K3 support reasoning and tool use?+
Qwen3.5 35B A3B Base: tool calling and image input. Kimi K3: reasoning and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Qwen3.5 35B A3B Base or Kimi K3?+
Qwen3.5 35B A3B Base has 0 sourced provider routes; Kimi K3 has 5, so Kimi K3 has broader tracked availability.
Which offers better value, Qwen3.5 35B A3B Base or Kimi K3?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.