model_not_found 🔌 API

LLM API: The model `x` does not exist or you do not have access to it (model_not_found / not_found_error)

The model name is wrong, deprecated/retired, or not available to your account/region.

Seen on: REST API

Meaning

Model IDs change with new releases and old ones are retired. Typos, using a display name instead of the API ID, or models not enabled for your org/cloud region cause it.

Common causes

  • Typo or display name instead of API model ID
  • Model retired/deprecated
  • Model not enabled for your account, org or cloud region
  • Using a model from another provider’s naming

⚡ Quick fix

  1. List available models via the API
  2. Update to a current model ID
  3. Check access/region availability (Bedrock/Vertex model access)

Detailed fix by platform

Shell

  1. curl -s https://api.anthropic.com/v1/models -H "x-api-key: $ANTHROPIC_API_KEY" -H "anthropic-version: 2023-06-01" | jq '.data[].id'

How to diagnose

  1. ID — Exact string
  2. Availability — Listed for your key/region?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.