Skip to content
Browse docsOverview

Documentation Overview

Know where your AI spend goes.

Tilden gives you a shared Workspace, a local CLI and a read-only MCP connection for supported AI clients. Start with the guide for your job, then check the sources and coverage behind the answer.

Updated October 7, 2026

Choose how you want to work

Invited onboarding

Workspace

Review supported provider costs, project and model breakdowns, briefings and budgets. Add explicitly shared coding-agent activity when your team wants that context.

Open guide →

Announcement · ChatGPT Pilot →
We’re building a ChatGPT plugin for read-only Workspace spending reviews. Public availability is planned.

Public · runs locally

CLI

Use aibill to inspect Claude Code and Codex evidence on your machine, understand estimates and coverage, and prepare a bounded improvement test. No Workspace account is required.

Open guide →

Assisted invited setup

Workspace MCP

Let a supported AI client read your Workspace spend, projects, briefing and budget settings with owner or admin consent. Client setup is checked during onboarding.

Open guide →

Start with the evidence on your machine

With Node 22 or newer, run these commands inside a project. The local CLI needs no account or provider key. Tilden is the product; aibill remains the published command and package name.

Terminal
npx aibill@latest init
npx aibill@latest

Init reads supported local metadata and creates or preserves local state. It does not connect the machine to Workspace. Empty evidence stays empty; use --sample only when you want a labeled demonstration. See the CLI guide for commands, telemetry controls and the optional Claude Code statusline.

Cost, usage and activity answer different questions

Provider-reported cost
Amounts returned by a supported provider cost source. These can be a known subtotal with missing or pending days, and can differ from the final invoice after credits, taxes or adjustments.
Estimated value
A value with a stated calculation or incomplete billing basis. Local tokens priced at API list rates are API-equivalent estimates, not subscription charges. Estimates do not become provider-reported costs when shared.
Shared activity
Supported machine-reported sessions, tokens and repository context. This can help you investigate work, but does not prove which person or agent caused a bill, whether a task was accepted, or its ROI.

Missing data is never silently treated as zero. Source availability, reader validation and the basis of a number stay separate. Read the source and evidence guide →

Understand what you connect

The default CLI analysis runs on your machine. Optional provider requests, Workspace sharing and MCP connections are separate choices. Workspace is hosted and stores the supported records you connect or explicitly share; a local-first claim about the CLI does not describe Workspace.

CLI usage telemetry is disclosed before sending and can be disabled with aibill telemetry off. A configured MCP client receives the tool results it requests, which then follow that client's data policy. Read the privacy policy for the full data flows.

Go deeper when you need it