Model error diagnosis

DeepSeek: R1 | model capability unsupported

DeepSeek: R1 returning 400 / model capability unsupported means you should first confirm whether model ID deepseek/deepseek-r1 is visible for this DeepSeek key, then separate permission, context, capability, rate limit, or route issues.

Model

deepseek/deepseek-r1

DeepSeek: R1

Provider

DeepSeek

11 models in catalog

Error type

model capability unsupported

capability-unsupported

Status code

400

China model route

Model error summary

Model

deepseek/deepseek-r1

Error type

capability-unsupported

Status code

400

Read-only check. Detection data burns after 5 minutes.

What this model error usually means

DeepSeek: R1 returning 400 / model capability unsupported means you should first confirm whether model ID deepseek/deepseek-r1 is visible for this DeepSeek key, then separate permission, context, capability, rate limit, or route issues.

Model: deepseek/deepseek-r1
Provider: DeepSeek
Status code: 400

How to prove it during checking

Read-only check. Detection data burns after 5 minutes.

List models: confirm whether deepseek/deepseek-r1 is actually visible instead of guessing from the display name.
Light probe: use minimal input to verify whether DeepSeek returns the same 400, then record the error body.
Compare model facts: context 64,000, input $0.700, output $2.5.
supports frequency_penalty
supports include_reasoning
supports max_completion_tokens
supports max_tokens

Next action

DeepSeek: R1 model capability unsupported should not end at failed. Return the next move: change model ID, add permission, reduce context, disable unsupported capability, change route, monitor, or hold listing.

Context: 64,000
Price: $0.700 / $2.5
Read-only check. Detection data burns after 5 minutes.

Open key check

Read-only check. Detection data burns after 5 minutes.