Suspected GPT-5.6 Cache Billing Anomaly
ClassicMain · reddit · 2026-07-11
A developer noticed a potential anomaly with prompt caching in the GPT-5.6 family:
- Using two identical requests on the original api.openai.com, cachewritetokens appear on the first request, but cachedtokens remains 0 for subsequent ones.
- This implies the system recognizes the cached prefix and avoids duplicate writes, but the read side isn't receiving the expected cache deduction.
- They noted that comparing GPT-5.5 within the same organization shows normal cache read billing.
- The post includes a minimal reproduction: two curl commands spaced 30 seconds apart reveal the issue.
The author concludes that if this isn't just a usage stats display bug, enabling caching on GPT-5.6 might be worse than not using it, prompting them to roll back to GPT-5.5 in their production routing for now.
More from Models
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- giffmana: the env being used in training is part of the point — giffmana · 2026-09-11
- awesome-llm-leaderboards: an open-source directory of LLM leaderboards, pricing tables, comparison tools — Last_Establishment_1 · 2026-09-11
- Anthropic claims it works to keep eval environments unidentifiable to models — MaxKannen · 2026-09-11
- Nex N2.5 Pro released on Hugging Face with 407GB of weights — jinnyjuice · 2026-09-11
- RoMa v2 image matching model unveiled in the usual black poster — ducha_aiki · 2026-09-11