Usage Radar

Simple setup. Every available feature free.

From local logs to a clearer picture.

Claude Code, Codex and Gemini already record their activity. Usage Radar brings the supported counters into one private dashboard. No account, payment details or provider API keys needed for local use.

  1. 01

    Explore the sample

    See the real dashboard with clearly labelled example data. Try the filters and session details before you install anything.

  2. 02

    Connect your machine

    Install the local connector, then open Connect. It reads supported agent logs and serves normalized usage to your browser over loopback.

  3. 03

    Understand your usage

    Check token counts, model costs, cache usage and coverage gaps. Connection status and pricing sources help you judge what each number means.

Install once

A small connector.
Your own machine.

On macOS and Linux, the installer below downloads the standalone build, checks its published SHA-256 and sets up the local connector. No Node or npm installation is needed. Windows downloads and step-by-step help are on the connection page.

curl -fsSL https://autopayradar.com/install.sh | sh

The current downloads are not notarized or publisher-signed. Review the installation and verification guide before running them.

Included, free

The tools to understand your usage.

  • Local usage dashboard for Claude Code, Codex and Gemini
  • Token counts, model breakdowns and cache accounting
  • Estimated costs with visible pricing sources
  • Your available local history, with coverage gaps labelled
  • JSON export of normalized usage records
  • Live connection status and refreshed telemetry

Usage Radar does not charge for these features. Your AI providers still bill you under their own plans.

Your work stays yours

The connector processes logs locally. The website receives normalized usage counters, not raw prompts, responses or source files. Public model-price updates may use the network; your local agent logs are not uploaded for those updates.

An estimate, with context

Costs combine observed token counts with model rates, unless a source records its own cost. Cache reads and writes have separate treatment. Your provider invoice remains the authority on what you were charged.

Gaps stay visible

Coverage depends on the logs available on your machine. Cloud-hosted Codex work leaves no local token log; it is shown as unobservable. Missing usage or an unknown model rate is not presented as a known zero.