Key error diagnosis

Moonshot AI | unsupported capability

Diagnose Moonshot AI unsupported capability (400) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

Provider

Moonshot AI

China provider route

Error type

unsupported capability

medium

Status code

400

unsupported-capability

Sample models

Kimi K2 0711 · Kimi K2 0905 · Kimi K2.5

Error route summary

Error type

unsupported-capability

medium

Provider

Moonshot AI

Status code

400

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

What this error usually means

Diagnose Moonshot AI unsupported capability (400) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

Provider: Moonshot AI
Error type: unsupported capability
Status code: 400

How to prove it during checking

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

Run read-only identity first: confirm whether the key really belongs to Moonshot AI, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Kimi K2 0711 · Kimi K2 0905 · Kimi K2.5 are visible and return stable evidence.
Finally record 400, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

unsupported capability should not only show failed. The console should return the next move: refill balance, change Base URL, switch model, add permission, change egress IP, hold listing, or monitor.

Read-only check. Detection data burns after 5 minutes.
China provider route
Kimi K2 0711 · Kimi K2 0905 · Kimi K2.5

Open key check

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

Open providers

Moonshot AI

Open models

Kimi K2 0711 · Kimi K2 0905 · Kimi K2.5

Return to Kimi K2.5

After clarifying this error, jump back to the newest model and decide whether the failure changes how far you keep following it.