MiniMax CN active Token Plan not detected in v0.47.0 (legacy remains endpoint returns 2062)

[liujianhao1226-beep]

Bug description

After upgrading to Win-CodexBar 0.47.0, the MiniMax China-mainland web/manual-cookie source still cannot fetch usage for an active Token Plan.

The previous 404 reported in #253 is gone, but the provider now reports:

no active token plan subscription

The same authenticated browser session clearly shows an active annual Token Plan and current quota usage.

Environment

• OS: Windows
• Win-CodexBar: 0.47.0
• Provider: MiniMax
• Region: China mainland (cn)
• Source: Web
• Cookie source: Manual

Reproduction

1. Log in to https://platform.minimaxi.com/console/usage?cycle_type=3.
2. Confirm the account has an active Token Plan.
3. Save a fresh Cookie header from that same authenticated session in CodexBar.
4. Run:

codexbar-cli.exe diagnose --provider minimax --source web --pretty --no-color --web-timeout 30

Actual result

{
  "provider": "minimax",
  "source_mode": "web",
  "auth": {
    "configured": true
  },
  "usage": null,
  "error": {
    "category": "unknown",
    "message": "no active token plan subscription"
  },
  "settings": {
    "cookie_source": "manual",
    "api_region": "cn"
  }
}

This is deterministic and reproduces in about 1–2 seconds.

Evidence from the same Cookie

Using the exact same freshly captured Cookie:

• GET https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains

  • HTTP 200
  • base_resp.status_code = 2062
  • base_resp.status_msg = "no active token plan subscription"

• GET https://www.minimaxi.com/backend/account/token_plan/usage_summary

  • HTTP 200
  • Returns valid usage data, including total_days, total_token_consumed, active_days, and daily usage.

The authenticated console page shows:

• Current subscription: Token Plan · TokenPlanPlus annual membership
• 5-hour quota: 2% used at verification time
• Weekly quota: unlimited

Browser network inspection shows the current console uses these endpoints:

• /backend/account/token_plan/usage_summary
• /v1/api/openplatform/charge/token_plan/usage
• /backend/account/token_plan_credit

This rules out an expired Cookie or an account without a subscription. The legacy remains endpoint itself no longer reflects the active plan for this account.

Relevant v0.47.0 implementation

The v0.47.0 provider still falls back to /v1/api/openplatform/coding_plan/remains on the platform host and then the www host:

https://github.com/nesszer/Win-CodexBar/blob/v0.47.0/rust/src/providers/minimax/mod.rs

Expected result

The MiniMax web/manual-cookie flow should use the current Token Plan endpoints used by the console, or fall back to them when the legacy remains endpoint returns status code 2062 despite an authenticated active subscription.

CodexBar should display the active 5-hour and weekly quota instead of reporting that no Token Plan exists.

Relation to #253

#253 fixed the China-host /account/amount 404 in v0.47.0 by making billing history best-effort and adding the remains fallback. This report is the follow-up behavior observed after installing that fix: the 404 is resolved, but the legacy remains endpoint now returns a false “no active subscription” result for a valid CN Token Plan.

No Cookie, API key, or account identifier is included in this report.

[Finesssee]

Thanks for the issue, I will fix this ASAP.

[Finesssee]

Fixed and merged as #262.

Root cause: your Token Plan has no coding-plan subscription, so the legacy /v1/api/openplatform/coding_plan/remains correctly answers base_resp 2062 (no active token plan subscription) — our 0.47.0 provider surfaced that as fatal instead of switching plan families.

The web/manual-cookie flow now detects the 2062 class and falls through to the console token-plan endpoints you identified: /v1/api/openplatform/charge/token_plan/usage (parsed with the shared quota schema — 5-hour and weekly lanes land exactly as your console shows, including unlimited weekly), plus best-effort enrichment from /backend/account/token_plan/usage_summary (summary row: tokens consumed + active days) and /backend/account/token_plan_credit (plan title, e.g. 'TokenPlanPlus annual membership'). Billing history stays best-effort. Your exact message strings and endpoint set drive the fixtures — thank you for the precise evidence; it made this a one-shot fix.

The merge is on main now and ships in the next 0.47.x patch release. When you upgrade, verify with codexbar-cli diagnose --provider minimax --source web --pretty — you should see quotaUsage instead of no active token plan subscription. Reopen if the real payload shape diverges from what these endpoints return (a redacted JSON snippet from /v1/api/openplatform/charge/token_plan/usage would settle it instantly if anything is off).