Know where every number stops.

With your onboarding contact, record the workspace, connected accounts, currency, inclusive UTC dates, source freshness and known missing days. Confirm source-specific administrative permissions before connecting; do not send provider keys in email or chat.

• OpenAI and Anthropic API costs: invited setup, subject to accessible provider records and retained history. Project detail depends on what those records contain.
• Historical limits: available history varies by connected source. Check coverage before treating a subtotal as a complete-period answer, and do not add overlapping records.
• Coding activity: optional Claude Code and Codex sharing needs explicit setup and consent. Sessions and repository labels do not allocate the provider bill.
• Cursor and Copilot: separate pilot checks are required. Broad real-account coverage is not established; do not depend on these facets without explicit acceptance for your setup.

If the requested period is incomplete, keep the gap visible. Agree a narrower useful review explicitly or pause that question. An unavailable answer is not zero spend. Prepare the review →

A live-verified local reader still produces API-equivalent estimated values, not billed spend. Approving a folder is a separate read boundary and verifies neither the reader nor the money.

In CLI output, verified means provider-reported and source-authoritative; it does not guarantee a final invoice. estimated states a calculation or qualified billing basis, detected_unverified is an unreconciled signal, and missing means a supported cost basis is absent. Workspace reports use their displayed source labels and coverage.

Workspace access is invitation-only. Source setup and availability are confirmed during assisted onboarding; a published CLI connector does not automatically enable that provider in Workspace.

Jev, Kimi and other planned integrations are not included as supported Workspace sources here. Historical availability depends on each connected source; there is no promise of complete account history.

The following entries describe the local aibill CLI and local MCP. The public CLI version is v0.9.12, checked October 3, 2026.

These are optional local CLI connectors. The Workspace setup above is separate. CLI connection registration and an explicit provider sync are also separate steps.

Connector validation never makes every returned row verified. The endpoint, record, coverage window, and final invoice boundary still determine the label. Open provider setup → · Review the versioned provider contracts ↗

Cursor local session storage, Cline, Aider, and other long-tail local formats do not currently produce financial rows. The investigated Cursor local store did not provide sufficiently stable evidence for routed model, billing mode, token semantics, adjustments, or reconciled spend, so a speculative local financial parser is not currently planned; official admin APIs remain the financial path unless a stable, versioned local format emerges.

New local formats enter through the public parser registry with a descriptor, synthetic recorded fixtures, conservative evidence defaults, generated source documentation, and privacy checks. Unknown models or token shapes stay missing, never estimated as zero.