Description
The quota API response fields `current_interval_usage_count` and `current_weekly_usage_count` are named as if they represent used amounts, but they actually return the remaining counts.
Current Behavior
Example response for `MiniMax-M*`:
```json
{
"current_interval_total_count": 1500,
"current_interval_usage_count": 1444
}
```
The field is named `usage_count`, suggesting 1444 requests have been consumed. In reality, 1444 requests are remaining, and only 56 have been used (1500 - 1444 = 56).
Expected Behavior
The field should be renamed to one of:
- `current_interval_remaining_count` / `current_weekly_remaining_count`
- `current_interval_remains_count` / `current_weekly_remains_count`
Or alternatively, the API should return actual usage counts and add separate `remaining_count` fields.
Impact
This misnaming causes confusion when reading quota responses — both for CLI users and for developers integrating the API directly. Consumers need to know the counterintuitive rule that `usage_count` means remaining, not used.
Environment
- mmx-cli version: 1.0.5
- Region: CN (`api.minimaxi.com`)
Description
The quota API response fields `current_interval_usage_count` and `current_weekly_usage_count` are named as if they represent used amounts, but they actually return the remaining counts.
Current Behavior
Example response for `MiniMax-M*`:
```json
{
"current_interval_total_count": 1500,
"current_interval_usage_count": 1444
}
```
The field is named `usage_count`, suggesting 1444 requests have been consumed. In reality, 1444 requests are remaining, and only 56 have been used (1500 - 1444 = 56).
Expected Behavior
The field should be renamed to one of:
Or alternatively, the API should return actual usage counts and add separate `remaining_count` fields.
Impact
This misnaming causes confusion when reading quota responses — both for CLI users and for developers integrating the API directly. Consumers need to know the counterintuitive rule that `usage_count` means remaining, not used.
Environment