Model limit probe

MiniMax: MiniMax M2.7 | concurrency limit

MiniMax: MiniMax M2.7 concurrency limit decides whether a key can enter a production route. TestKey reads model ID minimax/minimax-m2.7, provider MiniMax, catalog context, real-key headers, 429 errors, and region signals together.

Model

minimax/minimax-m2.7

MiniMax: MiniMax M2.7

Provider

MiniMax

8 models in catalog

Limit dimension

concurrency limit

concurrency

Visible signal

real key probe required

Context window: 204,800

Limit matrix summary

Model

minimax/minimax-m2.7

Limit dimension

concurrency

Visible signal

real key probe required

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

Why this limit matters

MiniMax: MiniMax M2.7 concurrency limit decides whether a key can enter a production route. TestKey reads model ID minimax/minimax-m2.7, provider MiniMax, catalog context, real-key headers, 429 errors, and region signals together.

Model: minimax/minimax-m2.7
Provider: MiniMax
Limit dimension: concurrency limit

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.
concurrency limit must bind model ID minimax/minimax-m2.7; limits from another model at the same provider cannot be reused.
concurrency limit · real key probe required · 204,800

Operator action

MiniMax: MiniMax M2.7 concurrency 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: real key probe required
Context window: 204,800

Open key checker

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

Open models

MiniMax: MiniMax M2.7

Open providers

MiniMax