Bug description
MiniMax usage cannot be fetched through the web/manual-cookie source on Windows. With the China mainland region selected, CodexBar always reports:
MiniMax billing returned status 404 Not Found
This appears to be caused by the MiniMax provider requesting the billing-history endpoint /account/amount, which returns 404 for the China mainland host. The request fails the entire provider refresh, even though the Coding Plan page itself is reachable.
Environment
- OS: Windows
- Win-CodexBar: 0.46.0
- Provider: MiniMax
- Region: China mainland (
cn)
- Source: Web
- Cookie source: Manual
Reproduction
- Enable MiniMax in Settings -> Providers.
- Set region to China mainland.
- Set Cookie source to Manual and save a valid MiniMax session Cookie.
- Run:
codexbar-cli.exe diagnose --provider minimax --source web --pretty --no-color --web-timeout 30
Actual result
{
"error": {
"category": "unknown",
"message": "MiniMax billing returned status 404 Not Found"
}
}
Direct request results observed on the same machine:
https://platform.minimaxi.com/account/amount?page=1&limit=100&aggregate=false -> HTTP 404
https://platform.minimaxi.com/user-center/payment/coding-plan -> HTTP 200
The relevant implementation in v0.46.0 builds the cookie billing URL as {region.base_url}/account/amount and treats any non-2xx response as a provider failure:
https://github.com/nesszer/Win-CodexBar/blob/v0.46.0/rust/src/providers/minimax/mod.rs#L320-L346
Expected result
A 404 from the optional billing-history endpoint should not make the whole MiniMax provider unavailable. The provider should either:
- Fetch Coding Plan quota from the current remains endpoint and treat billing history as optional; or
- Fall back gracefully when billing history is unavailable.
The original CodexBar MiniMax documentation references the Coding Plan remains endpoint:
https://github.com/steipete/CodexBar/blob/main/docs/minimax.md
No Cookie, API key, or account identifier is included in this report.
Bug description
MiniMax usage cannot be fetched through the web/manual-cookie source on Windows. With the China mainland region selected, CodexBar always reports:
MiniMax billing returned status 404 Not FoundThis appears to be caused by the MiniMax provider requesting the billing-history endpoint
/account/amount, which returns 404 for the China mainland host. The request fails the entire provider refresh, even though the Coding Plan page itself is reachable.Environment
cn)Reproduction
Actual result
{ "error": { "category": "unknown", "message": "MiniMax billing returned status 404 Not Found" } }Direct request results observed on the same machine:
https://platform.minimaxi.com/account/amount?page=1&limit=100&aggregate=false-> HTTP 404https://platform.minimaxi.com/user-center/payment/coding-plan-> HTTP 200The relevant implementation in v0.46.0 builds the cookie billing URL as
{region.base_url}/account/amountand treats any non-2xx response as a provider failure:https://github.com/nesszer/Win-CodexBar/blob/v0.46.0/rust/src/providers/minimax/mod.rs#L320-L346
Expected result
A 404 from the optional billing-history endpoint should not make the whole MiniMax provider unavailable. The provider should either:
The original CodexBar MiniMax documentation references the Coding Plan remains endpoint:
https://github.com/steipete/CodexBar/blob/main/docs/minimax.md
No Cookie, API key, or account identifier is included in this report.