API endpoint /coding_plan/remains requires cookie session instead of API Key

[jooey]

Issue Description

The API endpoint https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains documented for checking Token Plan usage does not work with API Key authentication.

Documentation Says

According to the documentation (https://platform.minimaxi.com/docs/token-plan/faq):

curl --location 'https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains' \
--header 'Authorization: Bearer <API Key>' \
--header 'Content-Type: application/json'

Actual Behavior

When calling with a valid API Key:

curl --location 'https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains' \
--header 'Authorization: Bearer sk-cp-...' \
--header 'Content-Type: application/json'

Response:

{
  "base_resp": {
    "status_code": 1004,
    "status_msg": "cookie is missing, log in again"
  }
}

Expected Behavior

Either:

1. The endpoint should accept API Key authentication like other MiniMax API endpoints
2. OR the documentation should clarify this is a web-only endpoint requiring session cookie

Additional Context

• Other MiniMax API endpoints (e.g., /v1/text/chatcompletion_v2) work correctly with MiniMax-API-Key header
• This appears to be a web platform endpoint that requires browser session authentication
• Users need programmatic access to check Token Plan usage without manual web login

Suggested Fix

Please either:

1. Enable API Key authentication for this endpoint
2. Create a new endpoint that supports API Key authentication for Token Plan usage queries
3. Update documentation to clarify authentication requirements