Opens in a new tab
News

Sol and Luna make repeated context cheaper. Count the corrections too.

In brief

Saving the unchanged beginning of a prompt can cut the bill for later updates. A summary that drops an important dependency can still leave the reviewer with more work.

5 min read

Is this the right starting point?
Before you read
Basic model-API and token-billing familiarity; cache-prefix behavior and cost arithmetic are explained.
What you will take away
Calculate matching-prefix charges and compare model migration costs using accepted tasks, retries and correction time.
Sources
Two people sit with laptops at a café table beside a clipped stack of papers and three small slips; one holds a sheet and marks it with a red pencil.
On this page3 sections

The next incident update starts with the same instructions and background as the last one. Only the new findings have changed. Making the model service process that beginning again feels wasteful, and prompt caching offers another route: save work from the unchanged opening and reuse it later. With Sol and Luna, writing it to the cache costs more than ordinary input, while reading it back costs much less. The first update is paying ahead for the next ones.

OpenAI announced the models alongside prompt-caching changes. Applications call them through the API as gpt-6-sol and gpt-6-luna; the announcement also described a gradual rollout in ChatGPT Work and Codex. For a team already generating summaries, the comparison should follow the same cases through any corrections needed to restore omitted facts, as in our agent observability analysis.

Four prices belong to different parts of the request

The table lists standard dollars per million tokens, the pieces of text the model processes or produces, rechecked October 20, 2026 and again November 2. The Sol and Luna model pages separate ordinary input, cache writes, cache reads and output. These rates belong to the exact model identifiers above. A newer Sol or Luna release is a different comparison.

ModelOrdinary inputWrite to cache (30m)Read from cacheGenerated output
GPT-6 Sol$2.00$2.50$0.20$10.00
GPT-6 Luna$0.10$0.125$0.01$0.50

Those cells are a starting point, not a quote for every call. Both model pages describe higher rates above 272,000 input tokens, regional premiums and differences among processing tiers. Tools can add charges as well. Match the price to the actual request before deciding which number belongs in the comparison.

Pay once for a beginning you will actually reuse

The unchanged opening has a name: the prompt's prefix. OpenAI’s caching documentation describes matching-prefix reuse. Put stable instructions and background first, followed by the new incident material; an explicit breakpoint marks the end of the reusable portion. For these models, a default 30-minute write costs 1.25 times ordinary input and a read costs 0.1 times. The write replaces the ordinary-input charge for those tokens, rather than adding a surcharge. Changed input and newly generated output still have their own charges.

The Responses API also offers a 12-hour minimum cache lifetime. Its write costs 2.5 times ordinary input, with the same read rate. That can suit updates separated by hours, but doubles the write cost in the example below. A minimum lifetime is not a promise to delete the cached material when that time ends.

Try an illustrative 10,000-token Sol prefix with the default 30-minute lifetime. Ordinary input costs $0.02; writing the cache costs $0.025; a complete read costs $0.002. One write and nine full reads add up to $0.043, instead of $0.20 for ten ordinary-input charges. That comparison assumes all nine later reads match the whole prefix. Changing input, output, tools and failed attempts are outside it. We have priced a repeated beginning, not ten finished tasks.

The extra write cost earns its place only if later requests match what was saved. Rewrite that beginning each time and this ten-request comparison falls apart. Leave it stable but keep correcting missing facts, and the cache can do its job perfectly while the overall task still takes too much work.

Ten ordinary 10,000-token gpt-6-sol prefix charges cost $0.20; one cache write plus nine full reads costs $0.043.
Illustrative matching-prefix arithmetic at the listed gpt-6-sol standard rates with a 30-minute write. Other usage and correction work remain outside these amounts; they are not completed-task prices.

The missing dependency still needs someone's time

In a hypothetical incident-summary pilot, two models receive the same bundle of facts. One repeatedly leaves out an unresolved dependency. Its provider bill is smaller. The reviewer nevertheless has to notice what vanished, repair the summary and check the next update. The token saving can be genuine while the human part of the handoff gets harder.

Suppose the reviewer returns that summary with the missing dependency marked. The next answer may reuse the background and still incur new input and output charges. It is another attempt at the same update, not another completed handoff. Record the model, cached and uncached input, output, retry, accepted result and correction minutes together. Compare repeated-background cases with genuinely new material while holding the acceptance and service checks steady.

Once the corrected summary preserves the dependency, count one accepted task. Include both attempts in provider spending, divide by accepted tasks and show that count alongside the result. A still-unacceptable summary adds nothing to the accepted count; with no accepted tasks, cost per success is undefined. Keep repair minutes separate unless you explicitly assign a labor cost. The token bill cannot price that extra effort by itself.

For this handoff, acceptance is concrete: the update must retain the unresolved dependency and the other facts the next responder needs. Exploratory work may not offer such a fixed test. Useful findings and reviewer effort can then be more honest comparisons than forcing a yes-or-no success score. Here, the reviewer's correction tells us exactly what the smaller bill left unfinished.

The next responder finally gets the summary with the dependency still open. Beside it is a usage record that includes both attempts and the extra review. Now the team can judge whether the cheaper model improved the route to that usable handoff. The cache gets credit for saving repeated processing, while the person who repaired the update stays in the calculation.

Sources & context

Sources linked in this article. Read alongside the author’s analysis; a citation does not independently verify a publisher’s claims.

Report an error or outdated detail

More on OpenAI

All OpenAI coverage

Keep reading

Where to go next