Model limit probe

MoonshotAI: Kimi K2.5 | concurrency limit

MoonshotAI: Kimi K2.5 concurrency limit decides whether a key can enter a production route. TestKey reads model ID moonshotai/kimi-k2.5, provider Moonshot AI, catalog context, real-key headers, 429 errors, and region signals together.

Model

moonshotai/kimi-k2.5

MoonshotAI: Kimi K2.5

Provider

Moonshot AI

4 models in catalog

Limit dimension

concurrency limit

concurrency

Visible signal

real key probe required

Context window: 262,144

Limit matrix summary

Model

moonshotai/kimi-k2.5

Limit dimension

concurrency

Visible signal

real key probe required

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

Why this limit matters

MoonshotAI: Kimi K2.5 concurrency limit decides whether a key can enter a production route. TestKey reads model ID moonshotai/kimi-k2.5, provider Moonshot AI, catalog context, real-key headers, 429 errors, and region signals together.

Model: moonshotai/kimi-k2.5
Provider: Moonshot AI
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 moonshotai/kimi-k2.5; limits from another model at the same provider cannot be reused.
concurrency limit · real key probe required · 262,144

Operator action

MoonshotAI: Kimi K2.5 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: 262,144

Open key checker

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

Open models

MoonshotAI: Kimi K2.5

Open providers

Moonshot AI