Qwen3.5 35B A3B vs Grok Build 0.1
At a Glance
| Compare | Qwen3.5 35B A3BQwen | |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| CostLower is better · Published-token output estimate | UnrankedNot in the 44-model eligible cohort | #1 of 44$0.0020 per LiveBench case |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.14Deepinfra ↗ · Sep 21, 2026 | $1.00Xai ↗ · Sep 3, 2026 |
| Output priceFrom · USD / 1M tokens | $1.00Deepinfra ↗ · Sep 21, 2026 | $2.00Xai ↗ · Sep 3, 2026 |
| Context windowMaximum documented tokens | 262K | 256K |
| Model facts checked | Aug 28, 2026View model evidence → | Sep 3, 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 | Grok Build 0.1 |
|---|---|---|
| Developer | Qwen | xAI |
| Family | Qwen3 5 35b A3b | Grok Build |
| Model | Qwen3.5-35B-A3B | Grok Build 0.1 |
| Version | Qwen3.5-35B-A3B | Grok Build 0.1 |
| Lifecycle | active | preview |
| Released | Unknown | 2026-05-29 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image | Text, Image |
| Output modalities | Text | Text |
| Context window | 262K | 256K |
| Total parameters | 36B | Unknown |
| Active parameters | 3B | Unknown |
| License | apache-2.0 | Unknown |
| Open weights | Yes | No |
| API available | Yes | Yes |
| Self-hostable | Yes | No |
| Provider access | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard), Together Ai (Standard) | Xai (Standard) |
| Capabilities | chat, generation, reasoning, tools | chat, generation, reasoning, structured_outputs, tools |
Qwen3.5 35B A3B Capabilities
Grok Build 0.1 Capabilities
Primary Evidence
Sources and Freshness
Questions
Qwen3.5 35B A3B vs Grok Build 0.1 FAQs
Is Qwen3.5 35B A3B or Grok Build 0.1 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Qwen3.5 35B A3B and Grok Build 0.1, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Qwen3.5 35B A3B or Grok Build 0.1?+
Qwen3.5 35B A3B is $0.14 and Grok Build 0.1 is $1.00 per million tokens, so Qwen3.5 35B A3B is cheaper on this metric. Qwen3.5 35B A3B is $1.00 and Grok Build 0.1 is $2.00 per million tokens, so Qwen3.5 35B A3B is cheaper on this metric.
Which has a larger context window, Qwen3.5 35B A3B or Grok Build 0.1?+
Qwen3.5 35B A3B has the larger sourced context window. Qwen3.5 35B A3B supports 262K and Grok Build 0.1 supports 256K.
Which performs better in benchmarks, Qwen3.5 35B A3B or Grok Build 0.1?+
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 or Grok Build 0.1 be self-hosted?+
Qwen3.5 35B A3B is the only model in this pair currently marked as self-hostable. Qwen3.5 35B A3B is open weight; Grok Build 0.1 is not marked open weight.
Can Qwen3.5 35B A3B and Grok Build 0.1 understand images?+
Qwen3.5 35B A3B is documented with image input; Grok Build 0.1 is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Qwen3.5 35B A3B or Grok Build 0.1?+
Neither has a larger sourced maximum output. Qwen3.5 35B A3B is — and Grok Build 0.1 is —.
Do Qwen3.5 35B A3B and Grok Build 0.1 support reasoning and tool use?+
Qwen3.5 35B A3B: reasoning, tool calling, and image input. Grok Build 0.1: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Qwen3.5 35B A3B or Grok Build 0.1?+
Qwen3.5 35B A3B has 4 sourced provider routes; Grok Build 0.1 has 1, so Qwen3.5 35B A3B has broader tracked availability.
Which offers better value, Qwen3.5 35B A3B or Grok Build 0.1?+
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.