AI usage and estimated spend
Review AI usage evidence and estimated spend.
Claude Code and Codex telemetry, broken down by user, model, repo, tool, skill and session. You get a number you can act on, the play-by-play behind it, and you choose what is ever stored.
estimated spend · trend
~$2,000
Trending up as adoption grows
projectedOne connected loop, held on the stage this capability serves. The other stages stay as context so you can see what feeds in and what comes next.
Prove what happened.
Review AI usage evidence and estimated spend.
Review every workspace change and who made it.
How we get to a number
We price the tokens your agents reported against a dated public price catalog, split four ways: input, output, cache read, cache write. Read-time and backfill use identical logic, so the number is stable. It is a fast, dated estimate you can check, not your provider's invoice.
Read spend by team and model at a glance. Each cell fills by its share, so a heavy team or an expensive model stands out.
estimated spend · darker fill means more
Open any session and see the whole run: an activity strip across its span, one swimlane per tool, and every failed call flagged in place.
flagged call · a tool call that failed or timed out
Per-tool event counts, cache hit rate, reasoning-effort mix, and time to first token — the fine-grained signals a per-seat spend report can never produce.
events by tool
71%
cache hit rate
p95 3.4s
time to first token
38%
high reasoning effort
Break it down, then drill in
Group spend and usage by user, model, client, repo, tool, slash-command skill, or session — then open a leaderboard and drill into a single user, repo, or session. Save the cuts you check often as segments, scoped to you or the whole org.
Send OTLP or a custom JSON envelope. Each event carries tokens, duration, and git context, keyed so retries never double-count.
Emit
OTLP or JSON envelope
Dedupe
by idempotency key
Cost
tokens x dated price
Rollup
hourly and daily
Spend is grouped by the provider behind each model, computed from public token prices applied to reported tokens. The total counts up from the parts.
estimated · this month
$3,020
Cost comes from a dated price catalog, split four ways: input, output, cache read, and cache write. Read-time and backfill use identical logic.
Every event carries its duration, time-to-first-token percentiles, and an exit status, so a slow or failing agent shows up beside its bill.
The published CLI wires Claude Code, Codex, Cursor and OpenCode to your workspace, backfills history from local transcripts, and tails events live.
Install
npm i -g @lubed/cli
Connect
lube ai connect
Emit
agents send telemetry
See it
spend in the dashboard
Privacy is a control
Four ranked levels decide what a payload keeps, from metadata_only structural telemetry up to opt-in full_content. Gitleaks and redaction tripwires reject any batch that leaks secrets, and every privacy toggle is written to the audit log.
Four privacy levels. You pick what gets stored.