Model error diagnosis

Mancer: Weaver (alpha) | model capability unsupported

Mancer: Weaver (alpha) returning 400 / model capability unsupported means you should first confirm whether model ID mancer/weaver is visible for this Mancer key, then separate permission, context, capability, rate limit, or route issues.

Model

mancer/weaver

Mancer: Weaver (alpha)

Provider

Mancer

1 models in catalog

Error type

model capability unsupported

capability-unsupported

Status code

400

global model route

Model error summary

Model

mancer/weaver

Error type

capability-unsupported

Status code

400

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

What this model error usually means

Mancer: Weaver (alpha) returning 400 / model capability unsupported means you should first confirm whether model ID mancer/weaver is visible for this Mancer key, then separate permission, context, capability, rate limit, or route issues.

Model: mancer/weaver
Provider: Mancer
Status code: 400

How to prove it during checking

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

List models: confirm whether mancer/weaver is actually visible instead of guessing from the display name.
Light probe: use minimal input to verify whether Mancer returns the same 400, then record the error body.
Compare model facts: context 8,000, input $0.750, output $1.
supports frequency_penalty
supports logit_bias
supports logprobs
supports max_tokens

Next action

Mancer: Weaver (alpha) model capability unsupported should not end at failed. Return the next move: change model ID, add permission, reduce context, disable unsupported capability, change route, monitor, or hold listing.

Context: 8,000
Price: $0.750 / $1
Read-only check. Detection data burns after 5 minutes.

Open key checker

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

Open models

Mancer: Weaver (alpha)

Open providers

Mancer