Failures and billing boundaries
Which failures are uncharged and which interruptions may still incur costs.
On this page
Reconcile the outcome
An upstream failure without a billable result normally records upstream_error at zero cost. HTTP status or a client error alone does not determine billing: partial delivered streams, client aborts and response translation failures after settlement may still be charged. Reconcile by request ID.
Records and diagnosis
Admission rejections such as authentication or model lookup may have no usage row. A nonexistent model does not test upstream failure accounting. Latency alone is inconclusive. Keep request ID, time, model, HTTP status and machine code for ledger and log reconciliation.