dify - 💡(How to fix) Fix [Xiaomi MiMo] Credentials validation fails with 400 "Not supported model mimo-v2-flash" when using Token Plan endpoint (v0.0.7)

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.14.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When configuring the Xiaomi MiMo plugin with the Token Plan - China API endpoint, credentials validation always fails immediately after clicking "Save", with the following error toast:

Credentials validation failed with status code 400 and response body {"error": {"code": "400", "message": "Not supported model mimo-v2-flash", "param": "Param Incorrect"}}

This issue was present in v0.0.5 remains unresolved in v0.0.7. The root cause appears to be that the credential validation logic is hardcoded to call the API using mimo-v2-flash as the probe model, but this model name is not supported on the Token Plan cluster (token-plan-cn.xiaomimimo.com). As a result, it is impossible to successfully configure the plugin with a Token Plan API key, regardless of whether the key itself is valid.

1. In Dify, go to Settings → Model Provider and locate Xiaomi MiMo (plugin version 0.0.7).
2. Click Add API Key / Configure.
3. In the "API Key Authorization Configuration" dialog, enter a valid Xiaomi MiMo API key obtained from the Token Plan (China) account.
4. Set API Endpoint to Token Plan - China.
5. Click Save.
6. Observe the error toast in the top-right corner.

<img width="2516" height="1291" alt="Image" src="https://github.com/user-attachments/assets/c9d9ebb3-8f60-4f93-bb68-d1d0720b4e68" />

✔️ Expected Behavior

Credentials validation should succeed when a valid Token Plan API key is provided. If the validation requires a probe/test call to the MiMo API, the plugin should use a model name that is actually supported by the selected endpoint cluster. For the Token Plan endpoint, supported models include mimo-v2.5-pro、mimo-v2.5、mimo-v2.5-tts-voiceclone、mimo-v2.5-tts-voicedesign、mimo-v2.5-tts、mimo-v2-pro、mimo-v2-omni、mimo-v2-tts, etc. — not the legacy mimo-v2-flash identifier.

Ideally, the validation probe model should be dynamically derived from the model list associated with the chosen endpoint, or at minimum use a model name known to be valid on each respective cluster.

❌ Actual Behavior

No response