Usage tracking

What it is

• Pulls provider usage/quota directly from their usage endpoints.
• No estimated costs; only the provider-reported windows.
• Human-readable status output is normalized to
  text

  Copy

  X% left
  , even when an upstream API reports consumed quota, remaining quota, or only raw counts.
• Session-level
  text

  Copy

  /status
  and
  text

  Copy

  session_status
  can fall back to the latest transcript usage entry when the live session snapshot is sparse. That fallback fills missing token/cache counters, can recover the active runtime model label, and prefers the larger prompt-oriented total when session metadata is missing or smaller. Existing nonzero live values still win.

Where it shows up

• text

  Copy

  /status
  in chats: emoji‑rich status card with session tokens + estimated cost (API key only). Provider usage shows for the current model provider when available as a normalized
  text

  Copy

  X% left
  window.
• text

  Copy

  /usage off|tokens|full
  in chats: per-response usage footer (OAuth shows tokens only).
• text

  Copy

  /usage cost
  in chats: local cost summary aggregated from OpenClaw session logs.
• CLI:
  text

  Copy

  openclaw status --usage
  prints a full per-provider breakdown.
• CLI:
  text

  Copy

  openclaw channels list
  prints the same usage snapshot alongside provider config (use
  text

  Copy

  --no-usage
  to skip).
• macOS menu bar: “Usage” section under Context (only if available).

Providers + credentials

• Anthropic (Claude): OAuth tokens in auth profiles.
• GitHub Copilot: OAuth tokens in auth profiles.
• Gemini CLI: OAuth tokens in auth profiles.
  • JSON usage falls back to
    text

    Copy

    stats
    ;
    text

    Copy

    stats.cached
    is normalized into
    text

    Copy

    cacheRead
    .
• OpenAI Codex: OAuth tokens in auth profiles (accountId used when present).
• MiniMax: API key or MiniMax OAuth auth profile. OpenClaw treats
  text

  Copy

  minimax
  ,
  text

  Copy

  minimax-cn
  , and
  text

  Copy

  minimax-portal
  as the same MiniMax quota surface, prefers stored MiniMax OAuth when present, and otherwise falls back to
  text

  Copy

  MINIMAX_CODE_PLAN_KEY
  ,
  text

  Copy

  MINIMAX_CODING_API_KEY
  , or
  text

  Copy

  MINIMAX_API_KEY
  . MiniMax's raw
  text

  Copy

  usage_percent
  /
  text

  Copy

  usagePercent
  fields mean remaining quota, so OpenClaw inverts them before display; count-based fields win when present.
  • Coding-plan window labels come from provider hours/minutes fields when present, then fall back to the
    text

    Copy

    start_time
    /
    text

    Copy

    end_time
    span.
  • If the coding-plan endpoint returns
    text

    Copy

    model_remains
    , OpenClaw prefers the chat-model entry, derives the window label from timestamps when explicit
    text

    Copy

    window_hours
    /
    text

    Copy

    window_minutes
    fields are absent, and includes the model name in the plan label.
• Xiaomi MiMo: API key via env/config/auth store (
  text

  Copy

  XIAOMI_API_KEY
  ).
• z.ai: API key via env/config/auth store.

Usage is hidden when no usable provider usage auth can be resolved. Providers can supply plugin-specific usage auth logic; otherwise OpenClaw falls back to matching OAuth/API-key credentials from auth profiles, environment variables, or config.

Related

• Token use and costs
• API usage and costs
• Prompt caching