`current_interval_usage_count` field is mislabeled — returns remaining quota, not consumed usage

[allenwlee]

The MiniMax API endpoint /coding_plan/remains returns fields current_interval_usage_count and current_weekly_usage_count which are misleadingly named. They actually return the remaining quota available, not the amount consumed.

Correct Interpretation:

Plaintext

+------------------------------+-------------------------------------------+
|            Field             |              Actual Meaning               |
+------------------------------+-------------------------------------------+
| current_interval_usage_count | Remaining requests in current 5hr window  |
+------------------------------+-------------------------------------------+
| current_weekly_usage_count   | Remaining requests in current weekly      |
|                              | window                                    |
+------------------------------+-------------------------------------------+
| current_interval_total_count | Total requests in 5hr window              |
+------------------------------+-------------------------------------------+
| current_weekly_total_count   | Total requests in weekly window           |
+------------------------------+-------------------------------------------+

Consumed Usage Calculation:

To get the actual consumed usage, it must be calculated as follows:

Go

used_5hr    = current_interval_total_count - current_interval_usage_count
used_weekly = current_weekly_total_count   - current_weekly_usage_count

This naming has caused confusion for developers integrating with the API. Suggest renaming these fields to current_interval_remaining_count and current_weekly_remaining_count for clarity, or adding documentation notes clarifying the field semantics.