Key error diagnosis

Anthracite Org | context length exceeded

Anthracite Org returning 400 / context length exceeded should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider

Anthracite Org

global provider route

Error type

context length exceeded

medium

Status code

400

context-length-exceeded

Sample models

Magnum v4 72B

Error route summary

Error type

context-length-exceeded

medium

Provider

Anthracite Org

Status code

400

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

What this error usually means

Anthracite Org returning 400 / context length exceeded should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider: Anthracite Org
Error type: context length exceeded
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 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 400, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

context length exceeded 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 checker

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