> For the complete documentation index, see [llms.txt](https://docs.trycaliber.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trycaliber.ai/using-caliber/how-the-numbers-are-calculated.md). # How the numbers are calculated Definitions for all-in spend, seats, active AI users, sessions, and percent AI-assisted. ## All-in spend **All-in spend** prefers each provider’s **billed** ledger (cost reports / invoices) when Caliber has it. If billed data is missing, Caliber falls back to **usage estimates**, then adds configured **seat fees**. Coverage labels you may see: `billed`, `estimated`, `partial`, or `none`. Week-over-week comparisons are **billed-first**. Estimated series can have ingestion gaps; do not treat estimated-only spikes as invoice truth without checking coverage. ## Seats * Seat price defaults to a per-tool monthly amount (configurable in **Settings → General**; product default is commonly $20/mo unless you change it). * Paid seats come from the vendor **license / roster** sources Caliber syncs, not only from “used the tool in the last 90 days.” * Having a seat is not the same as being an active AI user. ## Active AI user A human user counts as active in a window when canonical surface usage marks them active **or** they have billed spend greater than zero in that window. Machine / `api:…` synthetic users are excluded from people-facing lists. Adoption-style habit questions often use a **rolling 30 days**, which may differ from the spend range picker on a given page. ## Sessions “Session” means a provider session or Caliber session rollup for the tool in context (Claude from Anthropic, Cursor, and so on). Exact boundaries follow each provider’s telemetry. ## Percent AI-assisted (Code attribution) Line-grade AI assistance uses authorship notes in git (`refs/notes/ai` from Caliber Code): `ai / (ai + human + unknown)` on measured lines. Commit-level `Co-Authored-By` signals are secondary and are not blended into the line-grade percentage. Coverage is attested / shipped lines on measured repos; bots and service accounts are excluded from the coverage denominator. Prompt bodies are **not** stored inside git notes. Full methodology details for operators live in Caliber’s internal AI code methodology doc; this page is the customer-safe summary. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.trycaliber.ai/using-caliber/how-the-numbers-are-calculated.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.