docs: clarify minimax usage window semantics

This commit is contained in:
Peter Steinberger
2026-04-04 11:25:39 +01:00
parent 01a24c20bf
commit 2c36ca562d
8 changed files with 21 additions and 7 deletions

View File

@@ -34,6 +34,10 @@ per-message dollar estimate that OpenClaw can show in `/usage full`.
- `openclaw status --usage` and `openclaw channels list` show provider **usage windows**
(quota snapshots, not per-message costs).
- Human output is normalized to `X% left` across providers.
- MiniMax note: its raw `usage_percent` / `usagePercent` fields mean remaining
quota, so OpenClaw inverts them before display. Count-based fields still win
when present.
See [Token use & costs](/reference/token-use) for details and examples.

View File

@@ -59,7 +59,7 @@ Other surfaces:
- **TUI/Web TUI:** `/status` + `/usage` are supported.
- **CLI:** `openclaw status --usage` and `openclaw channels list` show
provider quota windows (not per-response costs).
normalized provider quota windows (`X% left`, not per-response costs).
## Cost estimation (when shown)