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`, `cache_write_tokens` appear on the first request, but `cached_tokens` 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
- Claude 20x users report sharply tighter limits and faster quota burn — MarcJSchmidt · 2026-07-21
- Cola launches July, the latest model jokingly billed as “second only to Fable” — oran_ge · 2026-07-21
- Kimi K3 looks stronger and about 5× cheaper on a frontend dashboard task — OwariDa · 2026-07-21
- Last Week in AI recap: Anthropic’s $65B round, IPO filing, and Microsoft’s MAI push — Last Week in AI · 2026-07-21
- A user says Claude 4.6 felt worse yesterday and asks whether model quality can drift over time — Rahios · 2026-07-21
- Kimi K3 hits 89.4% peak on software tasks while Fable 5 is slightly steadier — FinanceYF5 · 2026-07-21