Model not found and /v1/v1 error troubleshooting

model not found and /v1/v1 They are all configuration errors. Repeatedly recharging, rebuilding the key or increasing the number of retries is usually useless. You should first check the model ID and final request address.

Quick conclusion

call first /v1/models and copy the returned id, and then view the full URL in the client log. There are no models in the list usually due to account permissions or open status issues; /v1/v1 The client and configuration repeatedly append the version path; returning HTML 404 means that the request does not enter the API route.

Check before you start

Log the full URL and model fields that the client actually sent. Don't just look at what is filled in the settings page, because the client may automatically append paths or replace model aliases.

When you are not sure how the addresses will be spliced, you can use Base URL online checkerGenerate recommended values and final request path. This tool only analyzes the URL string in the browser, does not request the target API, and does not require an API Key.

Configuration steps

Get the real model ID

curl https://www.aifast.club/v1/models \
  -H "Authorization: Bearer $AIFAST_API_KEY"

Copy from returned results id field. The following content usually cannot be used directly as model ID:

• Web card title.
• Chinese model name.
• Manufacturer name.
• Marketing labels such as “latest”, “flagship” and “high-speed”.

Check final URL

A correct Chat Completions request usually looks like:

https://www.aifast.club/v1/chat/completions

Error example:

https://www.aifast.club/v1/v1/chat/completions
https://www.aifast.club/chat/completions
https://www.aifast.club/v1/models/chat/completions

If the client automatically appends /v1, Base URL fills in the root domain name; if the client requires a complete compatible address, keep it /v1。

FAQ

It is in the model list, but the call still does not exist

The model may only support specific APIs or the current account permissions may be different. Check whether the model supports Chat Completions, Responses, image or video tasks, and do not use text APIs to call non-text models.

404 returns the web page HTML

This indicates that the request may have landed on the front-end site rather than the API route. Check the host, path and reverse proxy and do not return HTML error pages as models.

The tool automatically changes the model name

Some clients only allow built-in models or map display names to fixed IDs. Check the request log to confirm the final sent value; use the custom model function provided by the client if necessary.

Next step

After correcting the model name and address, use non-streaming short request verification. After the short request succeeds, tool calls, long context, and streaming output are resumed.

If it still returns 401, 429, or 5xx, continue checking API error troubleshooting; If the address is correct but the real model and protocol need to be verified, runFree model checking。

When converting a project using a community protocol such as Cursor2API, the model directory may also change with the upstream entry. Please combine Cursor2API Risk Check and Migration GuideDetermine whether the model ID configuration is incorrect or the upstream model has been adjusted.