> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nemu.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# When a provider rejects a request

> What the errors from your own provider keys mean and how to fix them

Requests to your own models go straight to your provider with your key, so when
the provider refuses one, nemu passes the reason on instead of hiding it. In
chat the message appears on the failed reply. Through the API it is the body of
the error response, and the `x-nemu-error-origin` header says `provider` when the
refusal came from your provider and `nemu` when it came from us.

## Anthropic: the key is not scoped to a workspace

The message reads like this:

> This API key is not scoped to a workspace, so this request must include the
> anthropic-workspace-id header with the ID of the workspace to use.

Anthropic accepts two kinds of key, the long `sk-ant-api03` form and the
`sk-ant-usr` form. Either works. What matters is the **scope** the key was
created with, and it has to be a workspace, for example **Default workspace**.
A key created with the **Organization** scope does not say which workspace to
bill, so Anthropic refuses it.

There are two ways to fix it.

1. Create a new key in the Anthropic console with the scope set to a workspace,
   then replace the key on the provider in the [console](/console/providers).
2. Keep the key and add a header. Open the provider, choose **Customize
   headers**, and add `anthropic-workspace-id` with the ID of the workspace you
   want to use. See [custom headers](/console/providers#custom-headers).

A key scoped to a workspace cannot use Anthropic's Admin API.

## Other refusals

| Status | What it usually means | What to do |
| - | - | - |
| 400 | One or more parameters are not supported by this model | Check the model's settings or try another model |
| 401 | The provider could not authenticate the key | Replace the key on the provider |
| 402 | The provider account has no balance or a billing limit | Top up at the provider, nemu credits are not involved |
| 403 | The key may not use this model | Check the key's permissions at the provider |
| 404 | The provider does not know this model | Check the model ID on the model in the console |
| 429 | The provider is rate limiting this model | Wait a moment, or use another model |

A 429 that comes from nemu rather than the provider is a plan limit instead, and
is described under [plans](/plans).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.