Model limit probe

MiniMax: MiniMax M1 | reset window

MiniMax: MiniMax M1 reset window decides whether a key can enter a production route. TestKey reads model ID minimax/minimax-m1, provider MiniMax, catalog context, real-key headers, 429 errors, and region signals together.

Model

minimax/minimax-m1

MiniMax: MiniMax M1

Provider

MiniMax

8 models in catalog

Limit dimension

reset window

reset-window

Visible signal

real key probe required

Context window: 1,000,000

Limit matrix summary

Model

minimax/minimax-m1

Limit dimension

reset-window

Visible signal

real key probe required

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

Why this limit matters

MiniMax: MiniMax M1 reset window decides whether a key can enter a production route. TestKey reads model ID minimax/minimax-m1, provider MiniMax, catalog context, real-key headers, 429 errors, and region signals together.

Model: minimax/minimax-m1
Provider: MiniMax
Limit dimension: reset window

How to prove it

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

Start with the visible signal: real key probe required, then read headers and error bodies with read-only requests.
reset window must bind model ID minimax/minimax-m1; limits from another model at the same provider cannot be reused.
reset window · real key probe required · 1,000,000

Operator action

MiniMax: MiniMax M1 reset window 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: real key probe required
Context window: 1,000,000

Open key checker

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