Where should new teams begin?

Start at quickstart, then move to configuration and API reference once baseline tracking is confirmed.

Do docs cover operations and troubleshooting?

Yes. Dedicated sections explain diagnostics, alerting behavior, and common setup failure recovery steps.

Can docs support production rollout?

The docs include configuration and integration guidance designed for shared team environments and repeatable deployment.

What are the system requirements for the CLI?

The CLI runs on macOS and Linux. It requires a shell environment, internet access for authentication, and read access to Claude Code session logs.

How do we configure tracking for multiple projects?

Use the configuration guide to set project-level metadata and environment tags that flow through to attribution and reporting views.

Is there an API for programmatic access to usage data?

Yes. The API reference documents endpoints for querying usage events, cost summaries, and attribution data programmatically.

Glossary | TokenUse Docs

Read TokenUse docs for glossary and implementation guidance.

TokenUse provides per-model, per-project, and per-session visibility with alerts, reporting, and budget controls for developers and teams using AI coding agents.

Quick Answer

Follow step-by-step documentation to install TokenUse, configure tracking, and troubleshoot with minimal setup time.

What You Can Do With TokenUse

Start with quickstart and installation instructions.
Use command and API references for implementation details.
Follow troubleshooting paths to resolve setup and runtime issues.

Implementation Checklist

Confirm the owner and measurable outcome for this workflow.
Verify instrumentation captures model, project, and environment dimensions.
Define alert and escalation rules before broad rollout.
Link implementation docs and pricing assumptions for team review.

How It Works

Follow the quickstart guide to install and authenticate the CLI.
Run the tracker to begin collecting token usage data.
Configure environment tags and attribution keys for your projects.
Use API and CLI references for advanced workflows.
Check troubleshooting guides if collection or reporting issues arise.

Who It's For

Engineering Leaders — Track AI usage across teams and prioritize optimization work.
Platform Teams — Instrument AI operations with consistent telemetry and budget controls.
Finance & FinOps — Forecast AI spend, allocate costs, and maintain budget discipline.

Implementation Context

Operational Snapshot

Documentation provides implementation-first guidance for onboarding, CLI usage, API access, and operational troubleshooting.

Use docs sections to reduce setup time, validate instrumentation quality, and standardize team rollout patterns.

Common Workflows

Start with quickstart to install and authenticate the tracker.
Use CLI and API references to automate monitoring workflows.
Follow troubleshooting paths to resolve collection and reporting issues.

Common Questions

Where should new teams begin?: Start at quickstart, then move to configuration and API reference once baseline tracking is confirmed.
Do docs cover operations and troubleshooting?: Yes. Dedicated sections explain diagnostics, alerting behavior, and common setup failure recovery steps.
Can docs support production rollout?: The docs include configuration and integration guidance designed for shared team environments and repeatable deployment.
What are the system requirements for the CLI?: The CLI runs on macOS and Linux. It requires a shell environment, internet access for authentication, and read access to Claude Code session logs.
How do we configure tracking for multiple projects?: Use the configuration guide to set project-level metadata and environment tags that flow through to attribution and reporting views.
Is there an API for programmatic access to usage data?: Yes. The API reference documents endpoints for querying usage events, cost summaries, and attribution data programmatically.

Docs: Quickstart: Install and start tracking token usage in minutes.
Docs: CLI Commands: Reference for setup, tracking, diagnostics, and exports.
Docs: API Reference: Programmatic access to usage and cost analytics.
Help Center: Support articles for setup, billing, security, and troubleshooting.