Key error diagnosis

Anthracite Org | model permission denied

Diagnose Anthracite Org model permission denied (403) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

Provider

Anthracite Org

global provider route

Error type

model permission denied

high

Status code

403

permission-denied-model

Sample models

Magnum v4 72B

Error route summary

Error type

permission-denied-model

high

Provider

Anthracite Org

Status code

403

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

What this error usually means

Diagnose Anthracite Org model permission denied (403) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

Provider: Anthracite Org
Error type: model permission denied
Status code: 403

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 Anthracite Org, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Magnum v4 72B are visible and return stable evidence.
Finally record 403, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

model permission denied 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
Magnum v4 72B

Open key check

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