Receipts for your robots.
See token usage from Claude Code, Codex, Gemini CLI and OpenCode on your machine. Save an SVG in your repo, or choose to publish a hosted card and join the board.
$ npx -y @tokenchit/cli@latest generate --no-publishFree and MIT · Node.js 22+ · Local stats need no account.
This command sends nothing: --no-publish returns before any networking code loads. Bare generate ends by publishing — at a terminal it asks first, in a script or CI it does not. Publishing sends daily totals by agent and model, plus your handle, and never prompts, replies or file paths.
35 developers on the board · 729B tokens
Everything below the first command is optional. Reading your logs and rendering a card happen entirely on your machine, and --no-publish guarantees that is all that happens. Bare generate finishes by publishing: at a terminal it asks first, but a script or a CI job has nobody to ask, so it uploads. Keep the flag and the choice stays yours.
The card is a file you own, in a repo you control.
$ npx -y @tokenchit/cli@latest generate --no-publishwhat you get
what it costs
A hosted card that updates itself, and a row on the board.
$ npx -y @tokenchit/cli@latest publishwhat you get
what it costs
The local path, end to end. Five steps, none of which need an account.
Detects which agents you have, writes .tokenchit.json, and renders the card from the transcripts already on your disk. No account and no sign-in — this command has no networking code in it at all.
$ npx -y @tokenchit/cli@latest generate --no-publishtokenchit.svg is a plain SVG in your working directory. Every figure on it came from your own logs, and if an agent you use is missing, doctor says which one and why.
$ tokenchit doctorGitHub serves a committed SVG directly rather than through its image proxy, so the card renders even for readers your network never reaches.
$ git add tokenchit.svg && git commit -m "chore: update tokenchit"A Markdown image resolves against the file it sits in. Beside the card that is ./, from a README one directory down it is ../ — the path the CLI prints is the first form, and pasting it into the second is how a working card becomes a broken image.
The card is a snapshot, so it ages. A pre-commit hook re-renders and stages it every time you commit. The GitHub Action can also refresh a card, but only a published one: a runner has no access to your ~/.claude or ~/.codex.
$ tokenchit hook install[](https://tokenchit.app/u/your-handle)A profile README is its own repository, so the card has to be committed to that repo for GitHub to serve it. Pointing at an SVG in a different repository renders as a broken image.
Public ranking of everyone who has published. Run tokenchit publish — or a bare tokenchit generate, which ends by calling it — and you are on it. Stop publishing and your row goes stale, then falls out of the window on its own.
| rank | developer | agent mix | tokens | equiv. cost | streak |
|---|---|---|---|---|---|
| 1 |  @bucharitesh3w✓ | 364B | $660,707 | 0d | |
| 2 |  @Rupam-M✓ | 149B | $69,363 | 0d | |
| 3 |  @VinayakRai5✓ | 47.0B | $20,359 | 44d | |
| 4 |  @iyashjayesh✓ | 26.4B | $12,084 | 0d | |
| 5 |  @manishreddy123✓ | 25.1B | $10,484 | 0d |
Rank is total tokens over the selected window; cost and agent mix cover the same window. Streak is the current run of active days, which is not a windowed figure. A cli badge means the numbers were self-reported without a GitHub sign-in.
SVG from the embed endpoint, shown at actual size. Default is 495 × 195; layout=compact is 340 wide so two cards fit on one README line. Theme follows GitHub's dark mode via a media query. Every card carries the timestamp of its last sync, because the endpoint caches for four hours.
[](https://tokenchit.app/u/your-handle)<img height="195" src="…/card/your-handle.svg">
<img height="195" src="…/card/your-handle.svg?layout=compact">Markdown will not place two images on one line. The HTML form is the only way to sit cards side by side in a README, which is why the compact width exists.
Equiv. cost is not what you paid. It is what these tokens would cost at list API rates. Most agent usage runs under a subscription where no per-token charge ever happens, and models with no public price — bundled or self-hosted ones — are counted in the token total but left out of the figure.
The lime ✓ GITHUB mark means the account is real and the handle is theirs. It says nothing about the numbers. That is what the tier below is for.
| tier | method | proves | does not prove |
|---|---|---|---|
| ○ cli · self-reported | one-shot upload of a locally parsed summary | The file was produced by the CLI on some machine, at the stated time. | Nothing about the numbers. Logs can be edited before parsing. Treat as a claim. |
| ✓ github verified | GitHub device flow, then an API key bound to that account | The handle on the row belongs to the GitHub account that authorised it. Nobody else can publish under it. | Anything about the figures. It is an identity check, not an audit — the numbers are still self-reported. |
Not yet: signed daily deltas would prove the numbers arrived in order and were never edited after the fact, and a read-only provider analytics API would match them against real billing records. Neither is built, so neither is claimed — and neither would fix the ceiling below.
Ceiling: no tier distinguishes tokens spent on work from tokens spent on nothing. The card measures usage, not output.
Not a policy page. These are real tests in packages/cli/test/privacy.test.js, run on every push. Each one fails if the guarantee it names stops holding.
tokenchit recap renders this as a second committable SVG. Same data, no card constraints.
| agent | share | tokens | cost |
|---|---|---|---|
| claude-code | 52% | 2.46B | $742.10 |
| codex | 19% | 890M | $268.40 |
| opencode | 19% | 902M | — |
| gemini | 10% | 471M | — |
Peak block: Tue–Thu, 14:00–19:00 local. Derived from log timestamps only.
supported by
Neon backs tokenchit through their Open Source programme, and is the Postgres this project documents as its default. That choice came first and on its own merits: their idle behaviour is scale-to-zero with automatic resume, where the alternative needed a human in a dashboard to bring a quiet board back.
One command. It finds your agents, prints your stats and writes the card. The command shown cannot publish. Bare generate can, and in a script or CI it does so without asking, so keep the flag for a guaranteed local run.
$ npx -y @tokenchit/cli@latest generate --no-publishOr tokenchit sync to see the figures without writing anything. It makes no network request.
