Model limit probe

IBM: Granite 4.0 Micro | context window limit

IBM: Granite 4.0 Micro context window limit decides whether a key can enter a production route. TestKey reads model ID ibm-granite/granite-4.0-h-micro, provider Ibm Granite, catalog context, real-key headers, 429 errors, and region signals together.

Model

ibm-granite/granite-4.0-h-micro

IBM: Granite 4.0 Micro

Provider

Ibm Granite

1 models in catalog

Limit dimension

context window limit

context-window

Visible signal

catalog visible

Context window: 131,000

Limit matrix summary

Model

ibm-granite/granite-4.0-h-micro

Limit dimension

context-window

Visible signal

catalog visible

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

Why this limit matters

IBM: Granite 4.0 Micro context window limit decides whether a key can enter a production route. TestKey reads model ID ibm-granite/granite-4.0-h-micro, provider Ibm Granite, catalog context, real-key headers, 429 errors, and region signals together.

Model: ibm-granite/granite-4.0-h-micro
Provider: Ibm Granite
Limit dimension: context window limit

How to prove it

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

Start with the visible signal: catalog visible, then read headers and error bodies with read-only requests.
context window limit must bind model ID ibm-granite/granite-4.0-h-micro; limits from another model at the same provider cannot be reused.
context window limit · catalog visible · 131,000

Operator action

IBM: Granite 4.0 Micro context window 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 visible
Context window: 131,000

Open key checker

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

Open models

IBM: Granite 4.0 Micro

Open providers

Ibm Granite