Availability
Published, experimental, beta, planned, or unavailable in the version you are running.
Documentation
Published · npm latest v0.9.7
Gemini CLI · experimental, fixture-verified, financial-only
aibill documentation
Availability, reader validation, and financial evidence are independent. This page keeps all three visible so a supported source is never mistaken for a verified bill.
Updated August 27, 2026
01 · Read the labels
Published, experimental, beta, planned, or unavailable in the version you are running.
live_verified, fixture_verified, untested, or failed—the path’s test coverage.
verified, estimated, detected_unverified, or missing—the basis of a particular number.
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.
02 · Local coding agents
Anthropic
Published in v0.9.7
Reads supported local transcript metadata. API-equivalent values are estimates, never subscription charges or billed spend.
OpenAI
Published in v0.9.7
Reads root-session-aware rollout metadata with fork accounting and snapshot deduplication. Unsupported rows remain missing.
Published experimental in v0.9.7
Experimental, fixture-verified reader for supported chats JSON/JSONL token records. logs.json is detection-only and creates no financial row.
03 · Provider reports
Published in v0.9.7
Published in v0.9.7
Beta in v0.9.7
Beta in v0.9.7
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 ↗
04 · Coverage gaps
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.