Model limit probe

Upstage: Solar Pro 3 | concurrency limit

Upstage: Solar Pro 3 concurrency limit decides whether a key can enter a production route. TestKey reads model ID upstage/solar-pro-3, provider Upstage, catalog context, real-key headers, 429 errors, and region signals together.

Model

upstage/solar-pro-3

Upstage: Solar Pro 3

Provider

Upstage

1 models in catalog

Limit dimension

concurrency limit

concurrency

Visible signal

real key probe required

Context window: 128,000

Limit matrix summary

Model

upstage/solar-pro-3

Limit dimension

concurrency

Visible signal

real key probe required

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

Why this limit matters

Upstage: Solar Pro 3 concurrency limit decides whether a key can enter a production route. TestKey reads model ID upstage/solar-pro-3, provider Upstage, catalog context, real-key headers, 429 errors, and region signals together.

Model: upstage/solar-pro-3
Provider: Upstage
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 upstage/solar-pro-3; limits from another model at the same provider cannot be reused.
concurrency limit · real key probe required · 128,000

Operator action

Upstage: Solar Pro 3 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: 128,000

Open key checker

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