Know what your AI
coding tools cost.
Tokenbase reads the session logs your terminal coding agents already write to disk, normalizes them, and shows engineering leaders team-level spend and utilization. Never in the model request path. Metadata-only by default.
Reads the logs your agents already write
Every developer runs several AI coding tools, and nobody can say what they cost or whether they pay off. The data already sits on every developer's disk — siloed per vendor, per machine. Tokenbase collects it safely and makes it legible by team.
Collected on the device. Analyzed in the cloud.
Not local-first — source-side collection with configurable residency. The collector buffers locally; analysis is cloud-side, or your VPC, or a local model for zero egress.
A signed, device-scoped collector tails local session logs — read-only, checkpointed, never the request path.
One adapter per tool, each versioned with golden fixtures, maps every harness into one schema with coverage stats.
Facts roll up into team-level spend and utilization — aggregate only, behind a cohort threshold.
You choose what leaves the device.
The deployment matrix is the first thing security asks for, so it leads. By default raw transcripts never leave the machine — only structured metadata does.
| Mode | Leaves the device | LLM analysis | Buyer fit |
|---|---|---|---|
| SaaS · metadata-only | Structured metadata only | Cloud (no transcript) | SMB / midmarket |
| SaaS · redacted text | Redacted excerpts, opt-in | Cloud or customer LLM key | Less sensitive orgs |
| VPC / on-prem | Configurable | Customer VPC / local model | Enterprise / security |
| Local-only pilot | Nothing | Local model or no LLM | Security evaluation |
Token counts answer “how much,” not “was it worth it.”
Tokenbase labels every number by confidence tier and never prints an inferred figure without saying so. Spend is a fact from the logs — not a guess dressed up as one.
Factual. Tokens, models, session counts, tool calls, estimated cost — straight from the logs.
Inferred. Abandonment, retry loops, likely workflow type — heuristics on local data, labeled as such.
Never in the request path
Tokenbase reads logs the tools already write. It never proxies or intercepts live model traffic.
Metadata-only by default
Message bodies are an explicit org unlock — admin opt-in, developer-visible, with a redaction report.
No individual surveillance
Aggregate-only manager views, cohort thresholds, no leaderboards, no drill-down to a person.
Adapter health, surfaced
Parse-success and unknown-record rates per tool version — Tokenbase knows when a vendor update breaks coverage.
Signed, device-scoped collection
Each collector enrolls as a device with its own scoped token and signs every batch — no shared keys, no live browser session.
Coverage stated, not hidden
Per-tool, per-metric coverage labels. Cursor is sold as visibility, not precise spend — honestly tiered.
See where the spend goes.
Two inspectable agents, collected safely, with team-level spend and no source exposure. Start with a metadata-only pilot.