Model limit probe

Mancer: Weaver (alpha) | concurrency limit

Mancer: Weaver (alpha) concurrency limit decides whether a key can enter a production route. TestKey reads model ID mancer/weaver, provider Mancer, catalog context, real-key headers, 429 errors, and region signals together.

Model

mancer/weaver

Mancer: Weaver (alpha)

Provider

Mancer

1 models in catalog

Limit dimension

concurrency limit

concurrency

Visible signal

real key probe required

Context window: 8,000

Limit matrix summary

Model

mancer/weaver

Limit dimension

concurrency

Visible signal

real key probe required

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

Why this limit matters

Mancer: Weaver (alpha) concurrency limit decides whether a key can enter a production route. TestKey reads model ID mancer/weaver, provider Mancer, catalog context, real-key headers, 429 errors, and region signals together.

Model: mancer/weaver
Provider: Mancer
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 mancer/weaver; limits from another model at the same provider cannot be reused.
concurrency limit · real key probe required · 8,000

Operator action

Mancer: Weaver (alpha) 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: 8,000

Open key checker

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

Open models

Mancer: Weaver (alpha)

Open providers

Mancer