Model Deprecation

With the continuous iteration of the MiMo model, the new version has comprehensively outperformed the old version in terms of effectiveness and performance. We will gradually deprecate the legacy models, and the specific plan will be announced in advance via SMS, email, website announcements, etc. Please pay attention to the relevant messages and complete the switch in a timely manner.

Time Definition

• System replacement time: The time when the offline model is automatically switched to the new version model. After this time, requests using the old version model name will be automatically replaced with the corresponding new version model and billed according to the new version model. View Pricing

• Deprecation Time: The time when the name of the old model expires. After this time, requests using the name of the old model version will receive an error message. Please ensure that the model replacement is completed before this time.

Operational Recommendations

• Access Bill Details , check if there are any models pending offline;

• Refer to the system replacement model in the table below to complete your code self-check and replacement. It is recommended to fully test and verify before the official switch.

Deprecated model on 2026.6.30

Note:

Starting from 00:00 on June 18, 2026, Beijing time, requests for mimo-v2-flash will be automatically routed to mimo-v2.5. The relevant parameter processing rules are as follows:

• mimo-v2.5 does not support customizing temperature and top_p in thinking mode. The actual parameters passed to the model are temperature: 1.0 and top_p: 0.95

• If parameters are customized when using mimo-v2-flash, the parameters passed to mimo-v2-flash will be inherited when automatically routing to mimo-v2.5

• If thinking, temperature, or max_completion_tokens are not specified in the request, the system will automatically use mimo-v2.5 default values , as shown in the following table: