What counts as a cache hitRepeated context can be reused
Cache reuse can improve response speed and reduce usage cost, especially in multi-turn chats, repeated workflow calls, and code-completion loops.
- Normal input: billed at the model multiplier.
- Repeated cached input: billed from 0.1x.
- For high-cost models, cache multipliers may rise to 0.2x or be paused during extreme upstream volatility.
Simple exampleIf you repeatedly include a large shared context across a long conversation, the matched repeated portion can be charged at a lower multiplier.
Cache hits start at 0.1xMatched cached input is billed at only 10% of the regular input cost.
Longer sessions can cost lessFollow-up chats, workflow calls, and code-completion loops are more likely to reuse repeated context.
Premium models may adjustWhen upstream costs move sharply, cache multipliers may change and can be paused in extreme cases.