PROVIDER-SPECIFIC ACCOUNTING · ONE ZERO IS NOT A GENERAL RULE
Cached Input: Preserve the Provider’s Separate Usage Field
A long-scroll visual companion to the article. It summarizes the article evidence boundary and method; it does not extend the underlying result.
At a glance
Evidence in scope
- One canary: 0 cached input
- Provider definitions vary
- Do not infer cache eligibility from prompt reuse
Evidence boundary: Zero cached input is specific to the single canary; this is not evidence that cache never occurs or is free.
How to use the diagram
Record returned fields, model/version, pricing source date, cache eligibility, and any separate cache-write category.
What this visual explains: Keep cached input distinct from uncached input and output so provider accounting is not double-counted.
What it does not establish
No universal caching behavior or allowance-efficiency correlation is established.