OpenAI adds 12-hour prompt caching, with a higher write price

Single-vendor news analysis; not independent corroboration.

OpenAI’s API changelog dated October 20, 2026, announces a 12-hour prompt-caching option for reuse of shared instructions, tools and context across longer gaps between requests. The changelog lists cache writes at 2.5 times the input-token price. This is a feature announcement, not a general reduction in every API request’s cost. OpenAI API changelog

The documentation describes a minimum cache lifetime, not a deletion deadline. For supported GPT-5.6 and later Responses API models, developers select the lifetime through prompt_cache_options.ttl. The guide also says the write multiplier is the total write rate, not an additional surcharge, and that the lifetime does not guarantee lower latency on every request. OpenAI prompt-caching guide

Analysis: longer reuse could be useful for an application that repeatedly sends a stable reference pack, but the traffic pattern is the key question. A team that uses the same material in the morning and again in the afternoon has a different problem from a tool that submits unrelated documents each time. Treating both workloads as identical would conceal the reason to choose a longer cache window.

A practical evaluation should begin with representative request logs rather than a promised percentage saving. Separate material that stays unchanged from the parts that vary with each question. Then compare the total bill for the existing configuration and the proposed one, including writes, reads and output. Record actual elapsed time as a separate metric so an accounting improvement is not mistaken for a speed improvement.

Editors building research assistants should also keep source freshness separate from cache reuse. Before composing an article, confirm that the underlying document still supports the claim. Reusing context is an efficiency choice; deciding whether a price, availability statement or announcement remains current is an editorial responsibility.

ChipLyric has checked the official announcement and documentation, but has not run a billing or latency experiment. Both sources come from OpenAI and represent one vendor’s account, not independent corroboration. The value of this option remains workload-specific; a controlled comparison is more informative than assuming that a longer window automatically produces a cheaper workflow.