Skip to content
Qwen/Qwen3.5-397B-A17B-TEE

Qwen3.5-397B-A17B

Qwen/Qwen3.5-397B-A17B-TEE

HotPublicTEELLM
75.52Kinvocations
3active instances
$0.45 in / $3.00 out /M
256Kcontext
h200
Read the docs

Sign in to use the playground

Run this model with your Chutes account, quota, and API access.

Model facts & API quick start

Qwen3.5-397B-A17B (Qwen/Qwen3.5-397B-A17B-TEE) is served on Chutes inside a Trusted Execution Environment (TEE). Call it through the OpenAI-compatible API at https://llm.chutes.ai/v1 with a Chutes API key and "model": "Qwen/Qwen3.5-397B-A17B-TEE".

Qwen3.5-397B-A17B at a glance

Model ID
Qwen/Qwen3.5-397B-A17B-TEE
Developer
Qwen
Deployed by
chutes
Type
LLM
Input price
$0.45 per 1M tokens
Output price
$3.00 per 1M tokens
Cached input price
$0.045 per 1M tokens
Context length
262,144 tokens
Modalities
text, image in → text out
Precision
FP8 (as served on Chutes; upstream weights BF16)
Parameters
397B total
Active parameters
17B per token
Architecture
Hybrid vision-language MoE: Gated DeltaNet linear attention interleaved with gated attention (layout 15 x (3 x (Gated DeltaNet -> MoE) -> 1 x (Gated Attention -> MoE))), 512 experts, plus a vision encoder with early-fusion multimodal training
License
Apache-2.0
Released
2026-02
Experts
512 total; 10 routed + 1 shared activated per token
Layers / hidden size
60 / 4096
Context extension
262,144 native, extensible up to 1,010,000 tokens
Languages
201 languages and dialects
Vocabulary
248,320 tokens (padded)

API quick start

Base URL
https://llm.chutes.ai/v1
model
Qwen/Qwen3.5-397B-A17B-TEE
Endpoint
POST /v1/chat/completions
Auth header
Authorization: Bearer $CHUTES_API_KEY

OpenAI-compatible: point any OpenAI SDK at the base URL above and pass your Chutes API key as the API key.

cURL
bash
curl -X POST "https://llm.chutes.ai/v1/chat/completions" \
  -H "Authorization: Bearer $CHUTES_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "Qwen/Qwen3.5-397B-A17B-TEE",
  "messages": [
    {
      "role": "user",
      "content": "Hello!"
    }
  ],
  "stream": true,
  "max_tokens": 1024,
  "temperature": 0.7
}'

Qwen3.5-397B-A17B FAQ

What does 397B-A17B mean?

397B total parameters with 17B activated per token. It is a sparse Mixture-of-Experts model: each MoE layer holds 512 experts but routes each token through only 10 routed plus 1 shared expert, so you get large-model quality at a fraction of the per-token compute.

Can it process images?

Yes. Qwen3.5 is a unified vision-language model with a vision encoder trained by early fusion, and its card reports results on visual reasoning and video benchmarks. Send OpenAI-style multimodal content parts (image_url) in your chat messages.

What context window does it support?

262,144 tokens natively, extensible up to 1,010,000 per the model card. The chute's default max_tokens is 1,024; the card recommends 32,768-token outputs for most queries and up to 81,920 for hard math and coding.

What sampling settings should I use?

For thinking mode: temperature 0.6, top_p 0.95, top_k 20, min_p 0 (also the generation_config.json defaults). For non-thinking mode: temperature 0.7, top_p 0.8, top_k 20. presence_penalty between 0 and 2 reduces endless repetition, at some risk of language mixing.

Can I use it commercially?

Yes. The model is released under the Apache-2.0 license, which permits commercial use, modification, and redistribution.

What does the TEE suffix mean?

TEE stands for Trusted Execution Environment. Inference runs inside attested confidential-compute hardware, so your prompts and the model's outputs are processed within a hardware-isolated enclave rather than on an open host.

How do I call it from the OpenAI SDK?

Set base_url to https://llm.chutes.ai/v1 with your Chutes API key and model to Qwen/Qwen3.5-397B-A17B-TEE. Chat completions, raw completions, and streaming work through the standard SDK methods.

Should I keep thinking content in multi-turn history?

No. The model card's best practices say historical turns should contain only the final output, not the thinking content. The official chat template handles this automatically; if you manage history yourself, strip reasoning blocks before resending.