Why $100 of subscription usage may not mean a $100 bill
Keep list-price activity, subscription fees, and any additional vendor charges separate in your AI cost reports.
A subscription Agent's activity can be priced at public API rates even though the work ran under a subscription. That number is useful for comparing workload intensity. Treating it as a new invoice produces an accounting error before any arithmetic begins.
A team needs to know what it paid, what it consumed, and what it can still use. These are related questions with different sources of evidence.
Give the usage number an honest name
List-price usage is a valuation of observed tokens using a rate table. It is not a promise that the vendor would have invoiced exactly that amount under another commercial arrangement. Model versions, caching, special rates, and usage coverage can all affect the comparison.
Anthropic makes a similar distinction in its Claude Code documentation: session token costs are estimates, and subscription users should distinguish those figures from billing. Provider billing remains authoritative for the vendor's charges.
Reference: Anthropic: managing Claude Code costs
Keep an illustrative month in separate columns
Suppose a team pays an illustrative $200 subscription charge and records $350 of list-price activity through its tracked Agents. It should not report $550 as the subscription's cost. The $200 is the expense; the $350 is a measured usage valuation. If an additional usage charge appears on the vendor's bill, record that charge on its own terms.
The comparison can help a team discuss whether a plan is heavily used, but it is not a realized saving of $150. That claim would require a credible alternative purchase scenario, comparable rates, and the same workload. A number labelled “value” should not quietly become a financial outcome in a slide deck.
Understand the tab behavior
FlockTab records subscription passthrough calls with list-price usage while keeping them out of the tab's metered spending balance. The tab still supplies a stop control and applicable policies. Its API-key budget is not a measurement of the vendor's subscription allowance.
This separation matters when one project uses both API Agents and subscription Agents. The project report should retain the distinction rather than adding all displayed dollar amounts into a single total. An API cost, a subscription fee, and a subscription usage valuation have different meanings even when they share a currency symbol.
Make the finance handoff reproducible
For each report, include the period, currency, account, valuation basis, and coverage. Specify whether the number is an invoice charge, a contracted rate estimate, or list-price activity. Document what happens when a model's price changes and keep the source usage available for explanation.
Before exporting, choose one subscription and reconcile the report to its vendor bill. The check should explain why activity and charges differ, not force them to match. A report that preserves that difference gives engineering and finance something they can both use.
Sources checked 23 September 2026. Numerical scenarios are illustrative unless explicitly identified as provider data. Vendor limits and interfaces can change; consult the linked documentation for current details.