Key error diagnosis

Thedrummer | unsupported capability

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

Provider

Thedrummer

global provider route

Error type

unsupported capability

medium

Status code

400

unsupported-capability

Sample models

Cydonia 24B V4.1 · Rocinante 12B · Skyfall 36B V2

Error route summary

Error type

unsupported-capability

medium

Provider

Thedrummer

Status code

400

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

What this error usually means

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

Provider: Thedrummer
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 Thedrummer, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Cydonia 24B V4.1 · Rocinante 12B · Skyfall 36B V2 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.
global provider route
Cydonia 24B V4.1 · Rocinante 12B · Skyfall 36B V2

Open key check

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

Open providers

Thedrummer

Open models

Cydonia 24B V4.1 · Rocinante 12B · Skyfall 36B V2