Stripe billing context
Paid invoice
in_example_001 · USD · customer ID available. This invoice is not counted as AI margin.
Fictional example. This static presentation does not run a scan, upload files, save data, connect accounts or accept payment. Figures illustrate how evidence and limits can be shown.
Synthetic Integrity Scan · August 2026 UTC
Aster AI · example read
Three source views for one closed period. Revenue remains billing context; the findings below are about reported provider spend and comparable usage.
Sources in this example
Internal usage ledger
8,640,000 tokens
Customer-linked usage events in a fictional closed period.
Provider usage and cost
$2,455.75
9,020,000 tokens · reported cost · one shared project remains unattributed.
Attribution coverage
Only supported links count.
74.95%
Reported provider cost
$2,455.75
Linked to an exclusive project
$1,840.50
Without a reliable customer link
$615.25
This fraction covers the fictional provider report shown here. It is not a claim about all AI costs or customer margin.
Review items
Two differences, two separate meanings.
Observed cost · coverage gap
Spend without a customer link
$615.25
Reported provider cost minus cost linked to an exclusive project: $2,455.75 − $1,840.50. A shared project cannot identify the consuming customer. Review mappings before attribution.
Not confirmed loss, waste or underbilling.
Calculated quantity · comparison
Usage differs between sources
+380,000 tokens
Provider tokens minus internal ledger tokens: 9,020,000 − 8,640,000 in the same fictional period and unit. Check logging, retries and period closure before treating this as a defect.
No dollar exposure is calculated from this token difference.
What remains unknown
This example does not establish net collected revenue, customer-level AI cost, credits, margin or financial leakage. The real product is still being validated. Customer-data scans and connected monitoring are unavailable in this public preview.
Read the preview scope →