Model limit probe

ReMM SLERP 13B | concurrency limit

ReMM SLERP 13B concurrency limit decides whether a key can enter a production route. TestKey reads model ID undi95/remm-slerp-l2-13b, provider Undi95, catalog context, real-key headers, 429 errors, and region signals together.

Model

undi95/remm-slerp-l2-13b

ReMM SLERP 13B

Provider

Undi95

1 models in catalog

Limit dimension

concurrency limit

concurrency

Visible signal

real key probe required

Context window: 6,144

Limit matrix summary

Model

undi95/remm-slerp-l2-13b

Limit dimension

concurrency

Visible signal

real key probe required

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

Why this limit matters

ReMM SLERP 13B concurrency limit decides whether a key can enter a production route. TestKey reads model ID undi95/remm-slerp-l2-13b, provider Undi95, catalog context, real-key headers, 429 errors, and region signals together.

Model: undi95/remm-slerp-l2-13b
Provider: Undi95
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 undi95/remm-slerp-l2-13b; limits from another model at the same provider cannot be reused.
concurrency limit · real key probe required · 6,144

Operator action

ReMM SLERP 13B 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: 6,144

Open key checker

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