romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92697edb7c
openclaw/docs/concepts/usage-tracking.md
Jon Shapiro 92697edb7c fix(venice): add compat settings to prevent HTTP 400 errors 
Venice's API doesn't support certain OpenAI-compatible parameters that
Clawdbot sends by default:

- `store`: Venice returns HTTP 400 with no body when this is present
- `developer` role: Not supported by Venice's API

This adds VENICE_COMPAT settings (supportsStore: false,
supportsDeveloperRole: false) to all Venice model definitions, both
from the static catalog and dynamically discovered models.

Fixes issues reported in PR #1666 where users experienced silent
failures (HTTP 400, no body) when using Venice models.

Co-authored-by: jonisjongithub <jonisjongithub@users.noreply.github.com>
Co-authored-by: Clawdbot <bot@clawd.bot>
2026-01-26 17:56:01 -08:00

1.5 KiB
Raw Blame History

summary read_when
Usage tracking surfaces and credential requirements
You are wiring provider usage/quota surfaces
You need to explain usage tracking behavior or auth requirements

Usage tracking

What it is

  • Pulls provider usage/quota directly from their usage endpoints.
  • No estimated costs; only the provider-reported windows.

Where it shows up

  • /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.
  • /usage off|tokens|full in chats: per-response usage footer (OAuth shows tokens only).
  • /usage cost in chats: local cost summary aggregated from Clawdbot session logs.
  • CLI: clawdbot status --usage prints a full per-provider breakdown.
  • CLI: clawdbot channels list prints the same usage snapshot alongside provider config (use --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.
  • Antigravity: OAuth tokens in auth profiles.
  • OpenAI Codex: OAuth tokens in auth profiles (accountId used when present).
  • MiniMax: API key (coding plan key; MINIMAX_CODE_PLAN_KEY or MINIMAX_API_KEY); uses the 5‑hour coding plan window.
  • z.ai: API key via env/config/auth store.

Usage is hidden if no matching OAuth/API credentials exist.