Model limit probe

Magnum v4 72B | region and IP limit

Magnum v4 72B region and IP limit decides whether a key can enter a production route. TestKey reads model ID anthracite-org/magnum-v4-72b, provider Anthracite Org, catalog context, real-key headers, 429 errors, and region signals together.

Model

anthracite-org/magnum-v4-72b

Magnum v4 72B

Provider

Anthracite Org

1 models in catalog

Limit dimension

region and IP limit

region-ip

Visible signal

catalog plus runtime

Context window: 16,384

Limit matrix summary

Model

anthracite-org/magnum-v4-72b

Limit dimension

region-ip

Visible signal

catalog plus runtime

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

Why this limit matters

Magnum v4 72B region and IP limit decides whether a key can enter a production route. TestKey reads model ID anthracite-org/magnum-v4-72b, provider Anthracite Org, catalog context, real-key headers, 429 errors, and region signals together.

Model: anthracite-org/magnum-v4-72b
Provider: Anthracite Org
Limit dimension: region and IP limit

How to prove it

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

Start with the visible signal: catalog plus runtime, then read headers and error bodies with read-only requests.
region and IP limit must bind model ID anthracite-org/magnum-v4-72b; limits from another model at the same provider cannot be reused.
region and IP limit · catalog plus runtime · 16,384

Operator action

Magnum v4 72B region and IP limit is not just a number. It should become route throttling, sale tags, headroom alerts, fallback model suggestions, and price protection.

Read-only check. Detection data burns after 5 minutes.
Visible signal: catalog plus runtime
Context window: 16,384

Open key checker

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