Model limit probe

Xiaomi: MiMo-V2-Omni | max output limit

Xiaomi: MiMo-V2-Omni max output limit decides whether a key can enter a production route. TestKey reads model ID xiaomi/mimo-v2-omni, provider Xiaomi, catalog context, real-key headers, 429 errors, and region signals together.

Model

xiaomi/mimo-v2-omni

Xiaomi: MiMo-V2-Omni

Provider

Xiaomi

3 models in catalog

Limit dimension

max output limit

max-output

Visible signal

catalog visible

Context window: 262,144

Limit matrix summary

Model

xiaomi/mimo-v2-omni

Limit dimension

max-output

Visible signal

catalog visible

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

Why this limit matters

Xiaomi: MiMo-V2-Omni max output limit decides whether a key can enter a production route. TestKey reads model ID xiaomi/mimo-v2-omni, provider Xiaomi, catalog context, real-key headers, 429 errors, and region signals together.

Model: xiaomi/mimo-v2-omni
Provider: Xiaomi
Limit dimension: max output 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.
max output limit must bind model ID xiaomi/mimo-v2-omni; limits from another model at the same provider cannot be reused.
max output limit · catalog visible · 262,144

Operator action

Xiaomi: MiMo-V2-Omni max output 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: 262,144

Open key checker

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