What this error usually means
Diagnose Anthracite Org access forbidden (403) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
- Provider: Anthracite Org
- Error type: access forbidden
- Status code: 403
Key error diagnosis
Anthracite Org | access forbidden
Diagnose Anthracite Org access forbidden (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
access forbidden
high
Status code
403
access-forbidden
Sample models
1
Magnum v4 72B
Error route summary
Error type
access-forbidden
high
Provider
Anthracite Org
Status code
403
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.
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
access forbidden 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