Loading the catalogue…
Loading the catalogue…
Alibaba's open-weight, always-reasoning Qwen3.8 Max-class mixture-of-experts model with a 262K-token native context window.
Key strengths. The 512-expert MoE design (10 routed plus 1 shared expert per token) gives the model a large parameter capacity dedicated to reasoning-heavy work while keeping the active compute path smaller than the full parameter count. Thinking mode is mandatory and exposes a reasoning_effort control, marking this as a dedicated deep-reasoning model rather than a general-purpose chat model. Its native 262,144-token context window, extensible to roughly one million tokens, supports long documents and extended chains of thought within a single session. Independent benchmarks are now available for this checkpoint: Artificial Analysis scores it 47 on its Intelligence Index, well above the open-weight-model median of 22, with strong showings on research- and coding-oriented evals such as PaperBench (93.0) and Terminal Bench 2.1 (86.6).
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L0 | €1.81 / 5.44 | Online |
12 use cases classified by the curator. The note says why.
General-purpose LLMs with tool-calling typically handle classification adequately; no benchmark data exists to differentiate further.
Qwen models generally target conversational use cases and tool-calling aids backend integration, though this variant has no curated description or benchmarks to confirm quality.
Function-calling support implies capacity for structured entity output, though this remains an inference without task-specific scores.
Tool-calling capability directly supports function-calling app patterns, though draft status and absent benchmarks limit confidence beyond a baseline fit.
Tool-calling models typically handle structured output tasks reasonably well, though no extraction-specific benchmarks are published for this variant.
Baseline text-generation task expected of any general LLM in this family; no evidence disqualifies it, but no benchmarks confirm strength either.
Tool-calling is present but no code-specific benchmarks, context window, or parameter count are documented, making agentic coding performance uncertain.
Tool-calling support is present but no browsing-specific benchmarks or agentic scores are available; draft status further limits confidence for this workflow.
Tool-calling suggests some agentic capability, but no reasoning benchmarks or context window are published to substantiate multi-step planning performance.
Sourced numbers, not our own evaluations. Percentiles are against the whole Stav catalogue.
Computed from aa-intelligence-index, gpqa-diamond, aa-engineering-index, aa-coding-index, livecodebench, terminal-bench-v4, aa-lcr.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "qwen/qwen3-8-max",
"reasoning_effort": "high",
"messages": [{"role": "user", "content": "Hello!"}]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at