TokenReply

Loading…

Reload

Model not found

The supplied model ID does not match a currently published TokenReply catalog route.

Last checked · Sources: TokenReply code and documentation review; upstream wording may vary

Area
Model routing
Typical response
Error code `model_not_found`
Retry?
No, correct the model ID

Symptoms

  • Only one model name fails while other models authenticate normally.
  • The configured value resembles a display name or stale alias.

Likely causes

  • The model ID is misspelled, renamed, removed, or copied from another provider.
  • Case, punctuation, or a provider prefix differs from the published ID.

How to diagnose

  • Search the live models page for the exact raw ID.
  • Compare punctuation and provider prefixes character by character.
  • Confirm the client did not silently rewrite the model name.

Fixes

  • Replace the value with an exact current catalog ID.
  • Store model IDs in configuration so they can be changed without code edits.
  • Remove stale hard-coded aliases from fallbacks and scheduled jobs.

How to verify

The corrected ID appears in the live catalog and succeeds in a minimal request.

Resources