Model limit probe

WizardLM-2 8x22B | context window limit

WizardLM-2 8x22B context window limit decides whether a key can enter a production route. TestKey reads model ID microsoft/wizardlm-2-8x22b, provider Microsoft, catalog context, real-key headers, 429 errors, and region signals together.

Model

microsoft/wizardlm-2-8x22b

WizardLM-2 8x22B

Provider

Microsoft

2 models in catalog

Limit dimension

context window limit

context-window

Visible signal

catalog visible

Context window: 65,535

Limit matrix summary

Model

microsoft/wizardlm-2-8x22b

Limit dimension

context-window

Visible signal

catalog visible

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

Why this limit matters

WizardLM-2 8x22B context window limit decides whether a key can enter a production route. TestKey reads model ID microsoft/wizardlm-2-8x22b, provider Microsoft, catalog context, real-key headers, 429 errors, and region signals together.

Model: microsoft/wizardlm-2-8x22b
Provider: Microsoft
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 microsoft/wizardlm-2-8x22b; limits from another model at the same provider cannot be reused.
context window limit · catalog visible · 65,535

Operator action

WizardLM-2 8x22B 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: 65,535

Open key checker

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