use case · Engineering managers and FinOps

See what every agent costs before the invoice lands

Ringlet parses the token-usage events every agent emits and writes them to a per-profile SQLite ledger. `ringlet usage` aggregates spend across every agent and provider, with CSV export for billing reconciliation.

The problem

  • Token spend across several agents and providers is invisible until the monthly invoice arrives.
  • Each agent reports usage in its own format, if at all.
  • Finance wants a per-project cost breakdown; engineering has no easy way to produce one.

How Ringlet handles it

One ledger across every agent

Ringlet parses the input/output token counts that Anthropic, OpenAI, and MiniMax expose in their streaming responses and writes them to a SQLite ledger in each profile's HOME, tagged with timestamp, model, and provider.

Aggregate and export

`ringlet usage` rolls up spend per profile, per day, per model. `ringlet usage --export csv` dumps the ledger for billing reconciliation and FinOps spreadsheets.

Alert on thresholds

Wire a `cost-threshold` or `daily-rollup` hook to a webhook so a Slack channel gets the day's spend automatically — no waiting for the invoice.

The commands

terminal
ringlet usage
# NAME       AGENT    PROVIDER   TOKENS      COST
# work       claude   anthropic  4,120,880   ...
# scripts    codex    openai       842,110   ...

ringlet usage --export csv > agent-spend.csv

ringlet hooks add --all-profiles --on daily-rollup \
  --webhook 'https://hooks.slack.com/services/...'

Keep reading

faq

Questions

In a SQLite database inside each profile's HOME directory. Nothing is sent to a Ringlet server — there is no Ringlet server. The data stays on your machine.

ship it

Set this up in under a minute.

Ringlet is a single Rust binary, open source under MIT. Install pulls the right build for your OS and runs ringlet init.