Skip to main content

AI_MODEL_NOT_FOUND

Encountering an error? Get help with AI tools

Error Cause​

The specified model provider was not found. This usually happens when the provider name passed to createModel("xxx") does not exist, is misspelled, or has been discontinued. This error is unrelated to Token quota.

Identify Your Provider​

Check the first argument of createModel("xxx") or createImageModel("xxx") in your code — the argument value is your current provider. For example:

const model = ai.createModel("cloudbase");              // Provider is cloudbase (text)
const model = ai.createModel("hunyuan-v3");             // Provider is hunyuan-v3 (text)
const imageModel = ai.createImageModel("hunyuan-image"); // Provider is hunyuan-image (image)

The provider name also appears in the request URL path:

https://cloud1-xxx.api.tcloudbasegateway.com/v1/ai/{provider}/chat/completions

The {provider} in the path is your current provider. If this name does not exist or has been discontinued, this error will be triggered.

Provider Status​

ProviderStatusDescription
cloudbase✅ SupportedOfficial provider. Automatically uses plan quota after free quota is exhausted; returns error when plan quota is exhausted
hunyuan-v3✅ SupportedMini Program Growth Plan text provider. Only consumes free quota; returns error when exhausted
hunyuan-image✅ SupportedMini Program Growth Plan image provider, called via createImageModel("hunyuan-image")
hunyuan-exp❌ DiscontinuedHistorical provider, removed from the server, unusable
deepseek❌ DiscontinuedHistorical provider, removed from the server, unusable
Misspelled name❌ Not foundCheck if the createModel() argument is correctly spelled (case-sensitive)
Improperly configured custom provider❌ Not foundComplete the custom model group configuration in the console first, then use the corresponding provider name

Solution​

  1. Check the provider name: Review the argument of createModel("xxx") in your code and verify the spelling.
  2. Check the table above: If you are using a discontinued provider (e.g., hunyuan-exp, deepseek), switch to a resource point plan and change the provider to cloudbase.
  3. If using a custom provider: Complete the custom model group configuration in the CloudBase Console first. Once configured, you can use the corresponding provider name.
  4. Newly created groups: If you just created a custom model group, please wait a moment (configuration takes approximately 1-2 minutes to take effect) and try again.