GPT-6 Sol vs Luna: which one to choose and for which jobs
GPT-6 Sol vs Luna: the same 1.05 million token context window with a 20-fold price difference. Official benchmarks, cost examples and a decision table.
Reading time: 12 min

GPT-6 Sol and GPT-6 Luna are the two models that OpenAI added to GPT-6 Astra on September 22, 2026. The choice between the two boils down to a question: does work have an answer that you can quickly control? If yes, like when you extract the fields of an invoice or summarize an email, start from Luna. If the task asks to reason on several steps, such as writing or reviewing code or building an analysis, start from Sol.
The comparison is unusual because on paper the two models are almost twin: same 1.050,000 token context window, same maximum output, same levels of reasoning, same tools. Change the price, Twenty times on each line of the price list, and changes what OpenAI promises on each. Verified data on September 23, 2026 on OpenAI API documentation: before budgeting a project always double-check the official page.
In summary
- Sol and Luna have the same context window (1,050,000 tokens), the same maximum output and the same six levels of reasoning, from none to max.
- Luna costs a twentieth of Sol on each entry: $0.10 versus $2 on input and $0.50 versus $10 on output, per million tokens.
- OpenAI presents Sol for the complex code and agent flows, Luna for high volume targeted tasks.
- The only test in which OpenAI writes a score for both is DeepSWE v1.1: a little more than two points distance, both at maximum effort.
- Curiosity: Luna has a most recent date of knowledge by Sol, May 18 against April 20, 2026.
- Practice rule: Luna where error is seen immediately, Sol where an unseen error costs you dearly.
What GPT-6 Sol and Luna have in common, and what not
In the official cards of GPT-6 Sol and of GPT-6 Luna The differences lie in a few lines: price, stated level of reasoning and limits of demands.
| Voice | GPT-6 Sol | GPT-6 Luna |
|---|---|---|
| API ID | gpt-6-sol |
gpt-6-luna |
| What OpenAI Presents It For | complex code and agent flows | high volume targeted tasks |
| Reasoning (card label) | the highest | high |
| Speed (card label) | fast | fast |
| Context Window | 1,050,000 tokens | 1,050,000 tokens |
| Maximum Output | 128,000 tokens | 128,000 tokens |
| Levels of reasoning | none, low, medium (default), high, xhigh, max | the same |
| Date limit of knowledge | 20 April 2026 | 18 May 2026 |
| Price input and output, per million tokens | $2 and $10 | $0.10 and $0.50 |
| Token per minute, Tier 2 usage level | 1 million | 2 million |
| Tokens per minute, Tier 5 usage level | 40 million | 180 million |
Two details of the cards say how OpenAI imagines the use of the two models. Both have the same speed label, so speed is not the reason to choose Luna. And the limits of Luna are wider: already at Tier 2 it accepts twice the tokens per minute of Sol, at Tier 5 more than quadruple, consistent with a model designed for large volumes. Those who start from scratch find the overall picture, including ChatGPT plans, in What are GPT-6 Sol and Luna.
Twenty times less: where you see it on the price list
The ratio of the two prices is the same on each row of the official pricing: input, read and write cache, output, long context, and also Batch, Flex and Fast modes. For a reference, the predecessor GPT-5.6 Luna cost $0.20 and $1.20 and we had put it next to Claude Haiku 4.5 in this comparison.
Two rules apply to both and move the account more than the choice of the model. Above 272,000 input tokens the entire request is paid double the input and one and a half times the output, as indicated by the model cards: Sol goes to $4 and $15, Luna to $0.20 and $0.75. And the reasoning tokens, even if you don't see them, are paid as output tokens. Raising the effort on Luna costs less than on Sol, but it is not free.
How far is Luna from Sol in OpenAI tests
The numbers come from the September 22 announcement and it measured them OpenAI itself. In each line look at the level of effort: the same model, at different effort, gives different results.
| Tests and what it measures | GPT-6 Sol | GPT-6 Luna |
|---|---|---|
| DeepSWE v1.1: Software engineering tasks on real codebases | 68.8% at max effort | 66.6% at max effort |
| AutomationBench 1.0.6: business flows with 47 tools | 33.2% xhigh effort, $0.27 per asset | 5.4 points above GPT-5.6 Luna at high effort, with a cost per task 58% lower |
| OSWorld 2.0 offline, partial score: computer use | 60.5% xhigh effort | Max effort exceeds GPT-5.6 Sol (medium) at one-tenth the cost |
| Agents' Last Exam V1: professional work in 55 sub-sectors | 56.4% to max effort | not published |
| FrontierCode 1.1 Main: Merge-ready code | no number, only "equal to Claude Fable 5.1 xhigh" at lowest cost | not published |
| Internal fact assessment | about half of GPT-5.6 Sol errors | at high effort equal to GPT-5.6 Sol, at about one hundredth of the cost |
| Source | OpenAI announcement | same page |
The line that really answers the "Sol or Luna" question is one, DeepSWE v1.1: 68.8 versus 66.6, same test, same effort. Just over two points away with a price per token twenty times lower. It's a software development test, so it doesn't say anything direct on invoices or emails, but it suggests that there's less distance between the two than the list shows.
The other lines should be read more carefully. For Luna OpenAI it measures the jump over the GPT-5.6 models, not the distance from GPT-6 Sol. And the fact assessment uses conversations where users had reported an error, which OpenAI itself declares non-representative of normal use. The reason for this caution is in because vendor benchmarks are not comparable, the weight of effort in reasoning effort: what changes with regard to.
Curiosity: Luna knows more recent things than Sol
In the previous family the three variants of GPT-5.6 had the same limit date, February 16, 2026, as we had reported in GPT-5.6 Sol vs Terra. With GPT-6 dates separate, and contrary to what would be expected: knowledge of Luna arrives May 18, 2026, that of Sol stops at April 20, 2026. The cheapest model is the most up-to-date, and OpenAI does not explain the reason.
For an SME it weighs little: four more weeks are not enough to trust the model's memory on prices, rules or deadlines. For recent facts you pass the right documents or activate web search, available for both. The theme is deepened in knowledge cutoff: what it means in practice.
How much does the same job cost with Sol and Luna
Three examples with Standard prices, required below 272,000 tokens and no cache. Volumes and tokens are assumptions to show the order of magnitude, not measurements made on a company.
| Example (supposed volumes) | Tokens per month | GPT-6 Luna | GPT-6 Sol |
|---|---|---|---|
| 3,000 invoices and DDT, 4,000 incoming tokens and 400 outgoing each | 12 million in, 1.2 million out | 1,80 $ | 36,00 $ |
| 60,000 support emails to be summarized and sorted, 1,500 in and 250 out | 90 million in, 15 million out | 16,50 $ | 330,00 $ |
| 120 code revisions, 80,000 in and 12,000 out including reasoning | 9.6 million in, 1.44 million out | 1,68 $ | 33,60 $ |
The first and third cases say the same thing: when the bill is below $40 a month, between the two models they dance a few tens of dollars, and weighs more the quality of the result. There you choose on that. The second case is the one where the list really decides: in a year they make about $200 with Luna and almost $4,000 with Sol, for a job that Luna is built to do.
Two fixes bring examples closer to the real account. Repeated fixed instructions at each call, cached, cost one tenth of the entry price, according to the Luna's card. The raised effort adds reasoning tokens to the exit. With Luna the two effects shift cents, with Sol tens of dollars.
The work of an SME, divided between Luna and Sol
The table starts from jobs, not models. The right column says which signal, measured on your cases, justifies a change.
| Work | Start from | When to Change |
|---|---|---|
| Extract fields from invoices, DDTs and orders | Luna | Sol if it misses the wrong scans or formats never seen |
| Summarize emails, tickets and minutes | Luna | Sol if he loses the detail he decides, a date or amount |
| Classify and sort incoming requests | Luna | Sol if too many requests end up in the wrong queue |
| Answering questions about your documents | Luna | Sol if it mixes two documents or adds details |
| Translate and adapt product cards | Luna | Sol if technical terminology is to be corrected by hand |
| Review the code before merge | Sol | Luna only for style controls |
| Develop features and debug | Sol | Never: A bug costs more than saving |
| Analyses crossing multiple sources, reports for direction | Sol | Luna if the report is always the same |
| Agent working between CRM, management software and mail | Sol to decide, Luna for simple steps | Luna on each pass passing the test |
A distributor of electrical equipment with 150 orders per day. Think of a company receiving orders by email, half in PDFs and half written in the message. Luna reads each order and fills in codes, quantities and delivery dates in the business management software. Orders with a code absent from the price list or an out-of-range quantity go into a separate queue, where Sol compares them with the customer’s historical records and proposes a correction to the approver. The first half of the workflow is shown in the demo by automatic data entry.
A software house of six people. This is where the report flips. Sol works in Codex on new features and revisions before merge, where an escaped bug costs more than a month's consumption. Luna makes the outline: summarizes the open issues, writes the release notes, generates test data. Details are in Codex with GPT-6 Sol and Luna.
When Luna is not enough, and how to notice it first
You need a brief test on your worst cases. Take thirty real cases per stream, with crooked scans and hastily written emails, and spin Luna with production instructions. Then raise the effort and repeat: only what remains wrong is matter for Sol.
Stay on Luna if
- errors are rare and can be seen in a sample check
- by raising the effort to high the residual errors disappear
- when an information is missing, the model says it instead of inventing it
- the task is always the same and the volume is high
Switch to Sol if
- errors remain even at max effort and touch the cases that matter
- the task asks to link information from multiple sources
- you need to write or edit code that will go into production
- an error not seen costs more than a month of consumption
There is a third road, often the cheapest: Luna makes the big one and passes to Sol only the uncertain cases. Here it works well because the two models share context, APIs and tools, so moving a step does not change the architecture: the schema is in Mixed Model Strategy. If even Sol is not enough, above is GPT-6 Astra, the best model of OpenAI, compared to the direct rival in GPT-6 Astra vs Fable 5.1.
Five mistakes that inflate the bill
- Put Sol everywhere out of caution. On extraction and summaries you pay twenty times as much for a margin that in your cases may not be there.
- Compare the two models to different efforts. Luna at none versus Sol at medium tests effort, not the models. Set the same level and increase it only for the model that loses.
- Forget the reasoning tokens. They are paid as output even if they do not appear in the answer: measure them on your cases before the quote.
- Exceed the 272,000 tokens without realizing it. One attachment too many and all the request passes to the price of the long context. With huge documents only sends the useful parts.
- Try only on clean documents. The distance between the two models is seen on scans, broken tables and ambiguous requests. They are the ones to put in the test.
Sol or Luna: the rule to take away
Luna for what is repeated and controlled, Sol for what needs to be reasoned and then signed. With the same context, the same tools and a different price twenty times, the useful question is not which of the two is better, but how many of your steps can go down to Luna without losing quality. The answer comes from a test on your cases, not from the list.
If you also evaluate the Anthropic alternative released on the same day, the comparison is in GPT-6 Sol vs Claude Opus 5.5. And if you want to put Luna and Sol in the right place inside a stream that already exists, orders, tickets or code revisions, with Giallo Studio Let's start with your real papers and measure before we decide.
Giallo Studio guides: methodology and sources
How we apply it in the company
Related resources
GPT-6 Sol and Luna: what they are, where they are used and what changes
GPT-6 Sol and Luna pricing: API rates, sample calculations and ChatGPT plans
GPT-6 Sol vs Claude Opus 5.5: the official numbers and when to use which
Mixed model strategy: light and powerful
Claude Haiku 4.5 vs GPT-5.6 Luna
GPT-5.6 Sol vs Terra: which makes sense?Other direct comparisons
The same criteria applied to other model pairs.
- GPT-6 Sol vs Claude Opus 5.5: the official numbers and when to use which
- Claude Haiku 4.5 vs Gemini Flash-Lite
- GPT-6 Astra vs GPT-5.6 Sol
- Claude Haiku 4.5 vs GPT-5.6 Luna
- GPT-6 Astra vs Claude Fable 5.1
- Jev AI vs LLM: how to choose the right model
- GPT-5.6 Sol vs Terra: which makes sense?
- Kimi AI vs ChatGPT: which to choose for work?
- Gemini vs Copilot: Which to Choose
- Kimi AI vs Claude: documents, code and costs
- ChatGPT vs Gemini: which subscription is worthwhile in October 2026?
- Make vs Zapier vs n8n: which one to choose for your company
FAQ
What is the difference between GPT-6 Sol and GPT-6 Luna?
They have the same 1,050,000-token context window, the same maximum output of 128,000 tokens and the same reasoning levels. Their capabilities and prices differ: OpenAI presents Sol for complex coding and agentic workflows, and Luna for focused, high-volume tasks at one twentieth of the price per token.
How much do GPT-6 Sol and GPT-6 Luna cost via API?
Sol costs $2 per million input tokens and $10 per million output tokens; Luna costs $0.10 and $0.50, for requests up to 272,000 input tokens. Above that threshold, the entire request costs twice as much for input and one and a half times as much for output, with the same twenty-to-one ratio between the two models.
Why does GPT-6 Luna have a more recent knowledge cutoff than Sol?
The official model cards specify May 18, 2026 for Luna and April 20, 2026 for Sol, and OpenAI does not explain why. For an SME, it matters little: for recent facts, it is still worth giving the model the right documents or enabling web search.
Is GPT-6 Luna good for programming?
For narrowly defined tasks, yes. On DeepSWE v1.1, the only test for which OpenAI gives a score for both, Luna is just over two points behind Sol, both at maximum effort. For complex coding and agentic workflows, OpenAI recommends Sol.
Is it better to start with Luna or Sol?
Start with Luna when the result is quick to check: extracting fields, summarising and classifying. Switch to Sol only for cases that Luna gets wrong even with more reasoning. For coding and complex analysis, the reverse applies: start with Sol and try Luna on the simple steps.
Can GPT-6 Sol and Luna be used together?
Yes, and it is often the most economical choice. Luna routes, extracts and prepares; Sol handles uncertain cases or the final review. Since they have the same context window and tools, moving a step from one to the other does not require a change in architecture.
Are GPT-6 Sol and Luna available in ChatGPT?
Yes, in ChatGPT Work and Codex for Plus, Pro, Business, Enterprise and Edu subscriptions. Free and Go plans only have Luna, in the desktop app. The API identifiers are gpt-6-sol and gpt-6-luna.