ClawRouter

CodexBar reads the policy attached to a ClawRouter API key. The menu card shows its monthly budget, spend, requests, tokens, and provider breakdown. Provider rows come directly from ClawRouter, so the integration works with any routed model provider configured there; CodexBar does not need a separate provider plugin for each route.

Setup

Create a ClawRouter key with access to the routes you want, then store it in CodexBar:

printf '%s' "$CLAWROUTER_API_KEY" | codexbar config set-api-key --provider clawrouter --stdin

You can also paste the key in CodexBar Settings → Providers → ClawRouter. The hosted service is used by default:

https://clawrouter.openclaw.ai

For another deployment, set the Base URL in Settings or use CLAWROUTER_BASE_URL. The value may point to the service root or /v1; CodexBar normalizes both to /v1/usage. Overrides must be HTTPS URLs or bare hosts normalized to HTTPS.

Display

• Monthly budget meter and reset date when the policy has a budget.
• This-month spend against the configured limit.
• Request count and total token usage.
• Up to five routed-provider rows, ordered by spend and request count.
• Unmetered policy status and spend when no monthly limit is configured.

ClawRouter usage is policy-wide. If one key can route OpenAI, Anthropic, Google, OpenRouter, or non-model services, the same CodexBar card aggregates them and lists the provider identifiers returned by /v1/usage.

Environment variables

CodexBar sends the key only to the validated ClawRouter endpoint. /v1/usage returns accounting metadata; CodexBar never receives routed prompts or model responses.