Cost evidence
Estimates and charges are shown separately. Effective cost uses an invoice allocation first, then a provider-reported charge, then an estimate. These columns are never added together. Currencies stay separate.
Cost and provider units follow the attempt start date, using its latest settlement. Request and reply activity use their own event dates.
| Currency | Estimated | Provider reported | Invoice allocation | Effective known cost | Covered attempts |
|---|
Invoice comparison details (up to 100 allocations)
| Reference | Attempt | Currency | Actual allocated | Original estimate | Difference |
|---|
Measured units
Unknown measurements are not zero. Audio duration is shown only if a source measures it.
| Unit | Measured total | Measured attempts | Unknown attempts |
|---|
Refusals
Collection health
Tracking coverage
| Service | Observation in this report | Last observed | Reliable from |
|---|
Daily activity
| Date | Eligible | Admitted | Attempts | Replies | Refusals |
|---|
Budget warnings
Reporting only. Existing request allowances remain unchanged. This page does not activate a monetary hard cap.
Add a warning policy
Rates & invoice reconciliation
Rates are versioned snapshots with a dated public source. No provider prices are preloaded. Invoice allocations must identify an existing attempt; they replace its estimate and cannot be allocated twice.
Add an immutable rate version
For tokens, enter output and total input prices. To price cache separately, use uncached and cached input prices instead of total input. Leave unrelated units blank; do not assume a missing price is zero.
Allocate an invoice amount
Requests & attempts
Open a request for event, attempt, model, measurement and rate-version details. Prompts, replies and visitor addresses are not collected.