MiniMax usage not showing; test script reports “no result returned” (cc-switch)
Quick fix
MiniMax changed its balance endpoint, breaking the old parser. Upgrade to cc-switch v3.16.2 or later; older versions can temporarily use a custom query…
Symptom
Section titled “Symptom”打开 CC switch，minimax 没有用量显示，点击配置用量查询，选 token plan、minimax 点击测试脚本，报错，未返回结果Open CC switch; MiniMax usage is not showing. Click “Configure Usage Query,” select token plan and minimax, then click “Test Script”; it reports an error and no result is returned.
Starting 2026-06-01, MiniMax changed the response structure of its usage endpoint /v1/api/openplatform/coding_plan/remains: the old fields current_interval_total_count / current_interval_usage_count are always 0. Use current_interval_remaining_percent directly for the remaining percentage instead. The response also added a model_name field (the array includes entries such as general / video, so video must be filtered out). The built-in Token Plan - MiniMax preset in cc-switch still parsed the old fields, causing usage queries to report “no result returned,” show blank tray/cards, or return 0/empty (#3516, #3568, #3676, #3858). Fix PR #3518 (commit 43ae1e5) adapted to the new endpoint, but was initially merged into main without a release, so users continued seeing errors despite reports that it was “fixed.” The fix was eventually released in v3.16.2 (2026-06-07). Two related display variants have been reported in later versions: in v3.16.2, a user reported that the page showed usage at 100% while it was still usable (#3955; no conclusion provided); in v4.0.8, when the endpoint returns current_weekly_status = 2 (weekly quota exhausted while the window is still counting down), the weekly limit row is skipped as “no weekly limit,” leaving only the 5-hour bucket and showing “100% remaining,” contrary to the actual rate-limit status (#8123, still open; the reporter submitted a fix PR proposing that status ∈ {1, 2} display the weekly bucket, and only status = 3 skip it).
Upgrade cc-switch to v3.16.2 or later. The maintainer confirmed that the fix in #3518 (adaptation to the new MiniMax balance query endpoint, filtering non-coding models, handling plans with no weekly limit, and adding default MiniMax M3 pricing) is included in the v3.16.2 release (2026-06-07). Retest the usage query after upgrading.
If you cannot upgrade yet and are on v3.16.1, select a custom template under “Usage Query” and paste this community-verified script as a temporary workaround: request https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains（GET (GET, with Authorization: Bearer ${apiKey} in the Header). In the extractor, select the entry in response.model_remains where model_name is "general", read current_interval_remaining_percent, remains_time, current_weekly_remaining_percent, and weekly_remains_time, and return { isValid: true, remaining, unit, extra }. The full script is in the comments on issues #3568 and #3676.
Note: several users reported that the {{apiKey}} / ${apiKey} variable in custom templates may not be replaced with the actual key. If it does not work, temporarily enter your API Key in plain text directly in the Header to verify (take care not to expose it when sharing the configuration).
If the display is still abnormal after upgrading: “usage at 100% but still usable” in v3.16.2 is a known unresolved report (#3955); the weekly limit disappearing after the weekly quota is exhausted, leaving only “5 hours remaining 100%,” is a known v4.0.8 bug (#8123). Wait for its fix PR to be merged and released. In the meantime, use the “Plan Usage” page in the official MiniMax console as the reference.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 6 real issues
- The comments say #3518 was fixed. Why am I still getting an error?
- At the time, #3518 had only been merged into the main branch and was not included in any released tag (git tag --contains 43ae1e5 returned no results). The fix was not in the release unless you forked, merged, and built it yourself. It was officially released with v3.16.2 (2026-06-07); upgrade to that version or later.
- Why does the {{apiKey}} variable in the custom template not work?
- Users reported that the {{apiKey}} variable in the official preset template did not replace the actual key, causing the query to fail. As a temporary workaround, enter your API Key in plain text directly in the Authorization header of the custom template (Bearer your-key); multiple users confirmed this works.
- After upgrading to v3.16.2, usage shows 100%, but I can still use the service. Why?
- This is the known behavior reported in #3955. The issue is closed, but the discussion did not reach a clear conclusion. If the service is still usable, refer to the plan usage shown in the official MiniMax console and add details in #3955.
- After the weekly quota is used up, the weekly limit row disappears from the card and it only shows “5 hours remaining 100%.” Has the quota been restored?
- No. This is a v4.0.8 bug (#8123): when the weekly quota is exhausted, the endpoint returns current_weekly_status = 2, but the current parsing logic only recognizes status = 1 and incorrectly skips status = 2 as “no weekly limit.” The account is still rate-limited by the weekly quota. The reporter submitted a fix PR to display the weekly bucket for status ∈ {1, 2}; it is awaiting merge and release.
- Why are neither the 5-hour limit nor the weekly limit showing?
- If you are on v3.16.1 or earlier, the MiniMax endpoint field changes broke the old parser (the returned fields changed from total/usage counts to remaining_percent percentages). Upgrade to v3.16.2+ to restore the display of both quota windows.
Related problems
Section titled “Related problems”This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.