Halton Meter Docs

Know exactly what your
AI tools are spending.

Halton Meter is a local proxy that meters every LLM request (tokens, model, and real cost) straight to a SQLite file on your machine. Set it up in a minute.

4
Providers metered
~60s
To first capture
0
Bytes leave your box

Meter every token. Locally.

The documentation for Halton Meter, the proxy that turns invisible LLM spend into a cost report you actually read. Everything runs on your machine.

v0.4.1 · public beta 4 providers metered 0 bytes leave your box
01 Quickstart

From zero to a cost report in 60 seconds

Full guide →
1

Install the package

uvx runs the latest wheel with zero Python prerequisite. macOS is stable; Linux and Windows are in public beta.

$ uvx halton-meter init --apps
$ uv tool install halton-meter
$ pipx install halton-meter
2

Initialise your meter

Pick how much to capture. --apps covers your IDEs without touching the browser. Start there if unsure.

init
$ halton-meter init --apps
  1/8 Generating mitmproxy CA certificate…   
  2/8 Trusting cert in Keychain…             
  4/8 Installing launchd supervisor…         
  7/8 Daemon healthy  127.0.0.1:8081          
 init complete   mode: apps
3

Read your first report

Open a new terminal, run any prompt through your tools, then pull the numbers.

report
$ halton-meter report --today
02 Browse

Everything, by topic

Getting started
3 pages

Install, send your first metered request, and configure projects.

Concepts
6 pages

How the proxy works, project tagging, the SQLite schema, and pricing.

CLI reference
9 pages

Every command, flag, and exit code for the halton-meter binary.

Providers
4 pages

Per-provider coverage: Anthropic, OpenAI, Gemini, and Grok.

Operations
5 pages

Day-two running: logs, TLS trust, upgrades, and troubleshooting.

Security & privacy
2 pages

What stays local, the threat model, and how cert trust is scoped.

Halton Meter Cloud
10 pages
Cloud

Optional sync for 90-day trends, team views, and cross-machine rollups.