308 points meetpateltech 2 hours ago 163 comments
A_D_E_P_T 2 hours ago | parent
tristanj 2 hours ago | parent
user43928 1 hour ago | parent
fallingbananna 1 hour ago | parent
The pelicans place it nicely between Sol and Luna in terms of both pricing and results.
vdfs 1 hour ago | parent
SomeonesAccount 1 hour ago | parent
vdfs 6 minutes ago | parent
The only thing that pelican have is "models where not trained on this" maybe that true months (or years ago) now it's on every HN post and these AI labs are monitoring HN
enraged_camel 2 hours ago | parent
babelfish 2 hours ago | parent
enraged_camel 1 hour ago | parent
mwigdahl 1 hour ago | parent
babelfish 1 hour ago | parent
cbg0 1 hour ago | parent
rfgplk 1 hour ago | parent
mwigdahl 13 minutes ago | parent
entrope 1 hour ago | parent
hansonkd 1 hour ago | parent
user43928 1 hour ago | parent
At least unless the Terminal Bench 4.0 score is more indicative than the other ones, because that one shows it clearly worse than 6.1 Sol for both performance and cost.
cloverich 1 hour ago | parent
My expectation is Fable 5.5 is next overall improvement, and my bet is OpenAI's "Bel" will be the next competitive one (or, their lack of safety culture will bite them/us in the process).
laurels-marts 1 hour ago | parent
simianwords 2 hours ago | parent
Archit3ch 1 hour ago | parent
I'm optimistic about them tackling frontier intelligence next. Astra 6.1 please?
mapontosevenths 37 minutes ago | parent
The "cost per task" metric is just a weaselly way to sound like they didn't just double the cost for most users, and aren't having their proverbial lunch money stolen. They can no longer claim to provide more tokens, more capable models, or more usage in general. So they made up a new metric where "task" could be defined to mean whatever they need it to mean.
They had to become VERY specific in their wording to present any kind of value proposition that will entice people.
[0] https://newsletter.semianalysis.com/p/anthropic-subscription...
_aavaa_ 13 minutes ago | parent
Archit3ch 5 minutes ago | parent
5x is calculated in terms of API costs, nobody pays those extreme Anthropic prices outside enterprise users.
> like they didn't just double the cost for most users
Most users aren't on their $200 plan. Most users (including on the $200 plan) continue being subsidized.
Starlevel004 1 hour ago | parent
It's very likely this is a next checkpoint of GPT-6 "Sol", over-optimised for the web chat and offered to Codex subscribers as a "please go away" offering.
If this was half the price, I'd be very interested, but at 1/5/0.05? Feels like another panic release because they can't get Astra 6.1 out of the door...
minimaxir 1 hour ago | parent
But like the original release of Terra, it's still a weird middle child between the small-model-that-got-substantially-better (Luna) and the large-model-that-got-significiantly-cheaper (Sol). The TerminalBench 4.0 cost-per-task results are a bit confusing and I'm not sure why you would pick Terra over Sol in that case. Overall this release seems like a flex on Sonnet 5.5: a model which is having its own middle child problems between the godly Opus 5.5 and the surprisingly capable Haiku 5.5.
Someone1234 1 hour ago | parent
First we had:
> Luna (Small), Terra (Medium), Sol (Big).
Which was fairly smooth after you got used to their planets.
But then they added Astra as the "Bigger," which was mostly still self-coherent:
> Luna (Small), Terra (Medium), Sol (Big), Astra (Bigger)
But then things go confusing, they released Sol-6.1 which sometimes is superior to Astra, and discontinued Terra which made it look like this:
> Luna (Small), Sol-6.1 == Astra
But with Sol-6.1 costing the old Terra-6.0 price, while, as I said performing as good as the old "Bigger" model in many non-3D/UI situations.
Now they're re-introduced Terra, as a 6.1 release, making this even more confusing.
Did Microsoft's chief branding officer move over to OpenAI?
bananaflag 1 hour ago | parent
Someone1234 1 hour ago | parent
But minor credit to Anthropic, at least they've mostly stuck to their four model names (Haiku, Sonnet, Opus, and Fable). You mostly know where a model is MEANT to be positioned from the name alone. OpenAI cannot keep it consistent from release to release.
But, yes, currently Opus Vs. Fable has the same issue as Sol-6.1 Vs. Astra.
bluerooibos 1 hour ago | parent
Both companies have screwed up their naming royally. Maybe that's intentional - I'm sure it doesn't hurt Anthropic to have people using Fable a bit longer than they need to and racking up a huge bill in the process.
cesarvarela 53 minutes ago | parent
pants2 1 hour ago | parent
It's like iPhone 17 being faster than iPhone 16 Pro. Because it's newer and benefits from advances in chip architecture, despite being a lower model tier. Sometimes different iPhone models are released at different times.
dukeyukey 1 hour ago | parent
setgree 1 hour ago | parent
QuesnayJr 1 hour ago | parent
jedberg 1 hour ago | parent
I think the names are more of a reference to price. Luna is always cheaper than terra which is cheaper than Sol which is cheaper than Astra (for the same model number).
stymaar 1 hour ago | parent
Per token, yes. But per task it's not even necessarily the case depending on how much thinking is needed.
meerita 1 hour ago | parent
redox99 1 hour ago | parent
Yes, a more modern smaller model can beat an older bigger model at some tasks, that's what can be confusing.
risyachka 1 hour ago | parent
“Test them all”
mediaman 1 hour ago | parent
The lineup of models is still the same.
There are four models: luna, terra, sol, and astra.
Pricing increases for each level. This new 6.1 Terra is 50% cheaper than Sol 6.1.
They are lowering prices for newer releases, so yes if you compare Sol 6.1 to 5.6 Terra it won't look right, but why are you doing that? Look at the same release version for comparable numbers.
Each model improves in successive releases but they maintain pricing and capability coherency within a release version.
Yes, Sol 6.1 is supposed to rival Astra for some work, which is what you'd expect from a later versioned release model against a prior release bigger model.
Assuming they release Astra 6.1 at some point, I expect it'll be better than Sol 6.1, at a higher price.
I don't understand what people are asking for here? No reductions in pricing? Different model names on every version release? Not releasing any models for a version number until they're all ready?
the__alchemist 1 hour ago | parent
- Model name
- Version number
- Effort level
All 3 of these are a one-dimensional balance of price/speed, and capability (Loose terms). The confusion is in how these overlap, how they're announced/marketed etc. So you go from 1 dimensions to 3; you can visualize it as a box. For a given task, how do you choose where in this box you select? Which regions are your favorite? Can you map each region of this 3D space to specific tasks? Label them with intuitive names?Given the operations of the model are opaque, can you see how someone (most people?) might be confused?
Y_Y 1 hour ago | parent
After that you just have model "strength" and version number. But of course strength is only comparable at equal version number and the two axes are almost parallel.
Anthropic also does this, perhaps to a lesser extent.
BoorishBears 1 hour ago | parent
Luna doesn't exist anymore (it's not updated)
Larger models solve harder problems, higher effort makes models work more throughly.
mediaman 1 hour ago | parent
I see a ton of criticism and not a single person coming up with anything better, unless it's to take away options, like removing effort level.
What about buying Intel CPUs? A car? Electrical components?
If you're not just using this at a consumer level to ask about cooking recipes (and if that's your use case, you really don't care about API pricing, or any of this, and can just use the default), and are using it professionally, then this seems like a low bar of effort to understand what you're buying.
I do grant you the relationship between model and effort level has an unclear relationship, but there are also tradeoffs in most complex technical products that are not always clear; this is exacerbated by the fact that this product is stochastic.
Why are engineers using this as a professional tool expecting this to be bought like a consumer gadget and then blaming the maker?
brianpan 45 minutes ago | parent
Why is it ok for engineers to have confusing names and ways to interact with something?
How am I supposed to decide between these options: https://imgur.com/a/bXHWowL
How am I supposed to keep up with the changes every few months?
mediaman 18 minutes ago | parent
Are you presenting this as evidence that OpenAI's naming scheme is bad?
If you don't want to spend the time to know the difference between all these different suppliers and their models, then why are you using whatever this program is that gives you so many choices, most of which are bad? Why is this OpenAI's fault?
margalabargala 47 minutes ago | parent
Let's say I have some task that Luna 6.1 cannot do, but Terra 6.1 can. So I build my product around that. In a month when Luna 6.2 is released, then I have to figure out whether it's worth to evaluate and swap or just wait for Terra 6.2.
thomasahle 1 hour ago | parent
If you scale a model down, or switch out attention with linear attention, or introduce KV-compression, etc., you don't really know how it will affect model performance before you've trained the model.
And once you've spent millions training it, you might as well make it available if it's pareto optimal for some tasks. It also gives you more insight seeing how people use it in practice.
rao-v 1 hour ago | parent
You are also rolling the training of your models by size and the lat est small model can sometimes beat an older model.
For a while we thought you just train the big model first then distill smaller models from it but since we've learnt the importance of on policy RL (basically the way a small model figures out a problem is very diff from a big model so it's best to RL optimize each model distinctly)
fallingbananna 1 hour ago | parent
And some variants (e.g., the medium one) being skipped or delayed for a certain generation doesn't really change the overall size branding.
onlyrealcuzzo 1 hour ago | parent
It's nice that they have Terra which seems to fill a void that's been needed since Sol 6 focused on cost (at the expense of quality), Sol 6.1 got a huge boost in quality, but became unusably slow unless you paid Astra prices - at which point, why not just use Astra?
Now at least we have a viable other option again.
trollbridge 1 hour ago | parent
tedsanders 1 hour ago | parent
In general, LLM performance is incredibly multidimensional. There's no guarantee of a fixed ordering where the model that is best at math is also the model that's best at jokes. Despite that complexity, much of the variation in performance is explained by just a single variable: model size. In general, models that are bigger will (a) be more performant / reliable, (b) cost more per token, and (c) have better recall of esoteric facts. As you note, our models are ordered:
Luna < Terra < Sol < Astra
Even today, I'd recommend this as a general starting point for picking models. If you care about quality only, pick Astra. If you're a bit price sensitive, pick Sol. If you're very price sensitive, pick Terra or Luna.
Of course, model size doesn't capture all variation. Models that are trained later might have new data or new techniques or new architectures that earlier models lack. You can see this with models from all providers - Sonnet 5.5 outperforms Fable 5.1 in ways, and Gemini 3.8 Flash outperforms 3.1 Pro in ways.
In the case of GPT-6.1 Terra, I'd say Terra is probably better than Astra and Sol at technical communication, similar on vision and computer use (while being faster / cheaper), and a bit worse on most other things. For API developers, it's a nice midrange option if you want something cheaper than Sol but a lot smarter than Luna (especially for vision / computer use / communication). For subscribers, it's not a bombshell release - if you're hitting usage limits, maybe it helps you go a bit further, and if you want clearer communication or faster computer use, it can be a nice option to select.
If you have suggestions on how to name our products better, I'm all ears. Our intention is to make things clear and simple, even if we miss the mark sometimes.
Unfortunately, a lot of the complexity is somewhat irreducible and due to to the actual complexity of the products. Scaling model size is different from scaling reasoning effort which is different from scaling multi-agent count. So if we just swept all of those under a single name of "more IQ", it would make the naming simpler but the experience much worse, as important details would be obfuscated from end users.
Iolaum 1 hour ago | parent
> Despite that complexity, much of the variation in performance is explained by just a single variable: model size.
please release model size :p
halfmatthalfcat 1 hour ago | parent
For some reason, this is just hilarious to me. Idk if you're being serious or if this is passive aggressive but the thought of OAI actually taking advice from a random HNer and basing their naming scheme off that is peak.
jaggederest 1 hour ago | parent
Where else would you go? I'm honestly scratching my head thinking of someplace that wouldn't run you out on a rail, but that would give serious feedback. Kernel mailing lists are out, maybe there's something like that which I can't remember off the top of my head, but...
Also, nomenclature is incredibly hard. There are only two hard problems in computer science: cache expiration and naming things.
halfmatthalfcat 19 minutes ago | parent
qhwudbebd 1 hour ago | parent
torben-friis 1 hour ago | parent
- Understanding how effort and class interact (Is a high effort terra above a low effort Sol? Are larger models mostly always better regardless of effort?)
- understanding when (if ever) a new model tends to be better than an older but higher class one. Is an old astra better than a new terra?
If increasing effort and increasing model class produce improved results in a different way, I miss making it explicit in which way. In other words: What kind of issue warrants going up in effort? what kind of issue warrants going up in model class? What kind of issue is unlikely to be solved by either?
mckirk 1 hour ago | parent
That could solve the 'more IQ' problem, because you'd actually have different dimensions (e.g. for 'raw intelligence', technical writing, emotional understanding, etc) that you could use to communicate the differences in models better.
(Of course people would instantly start complaining that the benchmarks numbers are probably fake etc, but it is what it is.)
NikolaNovak 1 hour ago | parent
I.e. are all version numbers independent and Model X 7.5 is not necessarily of the same generation or cut off as Model Y 7.5? Or do all of your 6.1 models have something in common - cut off data, generation, baseline technology, approach, architecture, or something else?
Thanks! :)
elxr 1 hour ago | parent
Terra and Luna are dirt cheap and good enough for 50% (or more) of the typical junior dev's workload, and great for routine work. Sol and Astra have so much written about them at this point that it should be obvious what those are good at. The large/gigantic models for things that need full intelligence and slightly more branching thinking.
margalabargala 50 minutes ago | parent
Luna < Terra < Sol < Astra, fine. But does Terra 6.1 beat Sol 6? Does Fable 5.1 beat Opus 5.5? If I build something around this Terra 6.1 release, then when Luna 6.2 is released in a month, should I swap?
cdirkx 30 minutes ago | parent
nailer 13 minutes ago | parent
elxr 26 minutes ago | parent
I'll just stick to mostly Sol on low/medium/high and start experimenting with Terra tomorrow onward to see what it does noticeably better than Luna/Deepseek flash.
Any pareto frontier model, especially from the leading labs is guarnateed to be good enough for whatever your expectations are at this point. A quick few day test should be enough for anyone to make their own conclusions.
nailer 14 minutes ago | parent
> Run your own evals then if you have this much of a need to "correctly" choose.
No. OpenAI want my money, it's on them to communicate properly.
ceroxylon 57 minutes ago | parent
CompoundEyes 30 minutes ago | parent
When I was first learning to have agents interact I had a little script to orchestrate a model telling a joke, a critic collaborator helping develop material and an audience emoji rank them.
A favorite…
Prompt: “Tell a joke about mother in laws”
Gemma2 response: “What’s the best kind of mother in law? A dead one.”
6thbit 51 minutes ago | parent
We're probably headed to further specialized agents where a single ordering or even model size won't mean a lot.
atombender 50 minutes ago | parent
What's confusing to me in addition to the naming is that there are no published guidelines I can use, as far as I can see. Put yourself in the user's shoes. On what basis should one pick a model for a given task?
I can understand smaller models being dumber and faster. That aligns well with scenarios where you are willing to compromise; e.g. you're classifying content or asking a model to format text into a table.
But when you want "maximum intelligence, cost and time be damned", there's the implication that bigger models are smarter on a linear scale, and every provider's model release naming is currently conflicting with that expectation.
This isn't just a naming problem, but a communication problem. If I knew that Astra was the best at coding but a bit bad at writing, and Sol was almost as smart but better at technical writing, then that's the kind of thing I expect to be documented.
One possible way: A simple matrix with horizontal columns like "writing", "coding", "math", rows are the models, and each box is a number of stars from 1-5.
Instead, this sort of thing becomes lore, shared by word of mouth.
ilaksh 20 minutes ago | parent
GodelNumbering 47 minutes ago | parent
Thanks. I think the very response you wrote here is a better form of marketing for the software engineers than what openAI puts out there. When everything is groundbreaking and everything tops charts, nothing is.
I suspect a lot of target demographic (developers) prefer simpler and honest communication about not just the models high points but low points too. With the linked Terra post, if I saw 1 chart that clearly highlighted the usecases for which Terra is _worse_ than higher tier models, I would be more convinced overall.
Everything trying to occupy the top spot in my brain's limited "top model" representation space is not helpful.
jonplackett 40 minutes ago | parent
It’s probably just unavoidable. Like when Apple release a new MacBook Air first and it is (in some ways) faster than the old MacBook Pro.
I think the planets thing is a bit confusing though. I hadn’t really thought about it being based on the size of the planet. I assumed it was based on how far away they were with terra therefore being the base one.
mi_lk 35 minutes ago | parent
Instead, we got Opus 5.5, Sonnet 5.5 and Haiku 5.5 released weeks apart, and so are Sol 6.1 and Terra 6.1?
__jl__ 24 minutes ago | parent
Personally, I pretty much exclusively use claude for coding work (sorry!). Our application is running almost 100% on OpenAI API (except for some fallback models). It is the best API on the market. The models are excellent particularly for any application that is cost sensitive.
thejazzman 20 minutes ago | parent
it's almost like ya'll let the AI name it ;)
pietz 11 minutes ago | parent
Ntrails 10 minutes ago | parent
I don't expect the vast majority of your users care. I would guess they want a rough proxy for "cost" and will assume cost=>capability are roughly linked in a linear fashion.
it is very possible that the users weighted by spend do, and I'm therefore simply wrong. But, 2c
avaer 7 minutes ago | parent
Have a model alias called "math", another "jokes". Quality labels/date suffixes to these obvious label. Repoint as needed.
Something for people who don't want to play the cute "which part of the solar system is trending this week" game.
Closi 5 minutes ago | parent
> [broadly the logic is that four effectively random words have been chosen to represent parameter count]
> If you have suggestions on how to name our products better, I'm all ears. Our intention is to make things clear and simple, even if we miss the mark sometimes.
How about:
"Small", "Medium", "Large" and "Very Large"
baby 1 hour ago | parent
elxr 1 hour ago | parent
Sure Sol 6.1 on low/medium can be considered "cheap" considering its abilities, but it's clearly not meant for the same type of tasks as Luna. You just grow an intuition for when something is solvable with a Luna-sized model. I'm guessing Terra is good for the tasks that you'd typically use Sol 6.1-low for, or for Luna type tasks (or other not-novel problem) where you want to reduce the risks of suboptimal decision making. It's exactly what I'd go with for feature additions where the correct solution is already mostly designed/specced-out.
lbreakjai 47 minutes ago | parent
Obviously not, otherwise the four models would be called Copilot, as well as the harness.
InsideOutSanta 34 minutes ago | parent
iAMkenough 22 minutes ago | parent
dev_l1x_be 20 minutes ago | parent
oh_no 19 minutes ago | parent
Luna (Small), Terra (Medium), Sol (Big), Astra (Bigger)
is perfectly clear, sol beats astra sometimes because Astra 6.1 was scrapped. and note that opus 5.5 beats fable 5.1 most of the time too without a skipped model.
kwinkunks 19 minutes ago | parent
"Speed, quality, price: pick two". I think I'd rather see a choice like that than the current convolution of $-per-token, sub quota, latency, simulated reasoning level, model size, context size, etc, etc.
hadlock 11 minutes ago | parent
I don't want to rush to their defense here, but, when model families are getting refreshed every 6 weeks, there is going to be significant overlap, particularly with these staggered releases
paulpauper 1 hour ago | parent
let's see if it can pass the Pangram test. Many services purport to fool it, but fail.
Silagi 1 hour ago | parent
Virtually every task I give to either is better served by going up a tier and down a reasoning level, or down a tier and up a reasoning level. I simply don't understand their use case. No testing I've done has shown them to have a niche where there isn't a cheaper-with-equal-results or more-performant-at-same-cost option.
eknkc 1 hour ago | parent
On subscription for coding and stuff I am basically on Astra Ultra all day long.
nfw2 1 hour ago | parent
datadrivenangel 1 hour ago | parent
nfw2 36 minutes ago | parent
2. There are rote or simple tasks where higher reasoning isn't needed and one model vs the other wouldn't even be distinguishable.
3. How many tokens are used during reasoning depends as much on the task as the reasoning level.
4. Sonnet is faster and half the price per token, so Opus will only be cheaper if it can spend fewer tokens. This won't be the case for all tasks. Opus and Sonnet will also consume the same number of tokens to load context, so the relative price comparison depends a lot on where the task is context-heavy or reasoning-heavy.
datadrivenangel 32 minutes ago | parent
What are you smoking and can I have some?
datadrivenangel 1 hour ago | parent
I think it's also a fake lever to give to finops / it teams to try and keep costs down.
rfgplk 1 hour ago | parent
Silagi 1 hour ago | parent
rfgplk 1 hour ago | parent
notatoad 1 hour ago | parent
if you're just talking about use in codex or claude code, then sure, leave it on opus all the time. but for running routine api requests, sonnet is great.
h14h 1 hour ago | parent
If you pay API prices for inference in your product stack & have specific use-cases w/ custom evals, these smaller models provide an additional cost/speed lever to adjust. Ultimately, I think the point is to compete on cost for use-cases where Sol on the lowest reasoning is overkill.
If you have a fairly straightforward usecase where Terra performs just as well as Sol, but is faster and cheaper, why not use it?
handzhiev 1 hour ago | parent
moecables 59 minutes ago | parent
foretop_yardarm 44 minutes ago | parent
InsideOutSanta 33 minutes ago | parent
hobofan 9 minutes ago | parent
I have some business automation process for some customers that I maintain, where Terra with low reasoning ended up with the best price/performance & latency. With an equivalent Luna with high reasoning, price was usually better, but quality had a higher variance (very much depends on where the thinking takes the model) and latency for high reasoning was worse.
altcognito 8 minutes ago | parent
rattynm 6 minutes ago | parent
simonw 1 hour ago | parent
Interesting that both "none" and "low" reasoning levels appeared not to spend any reasoning tokens at all, and in fact low ended up using less tokens and costing less than none here.
"medium" did use 496 reasoning tokens, but that's apparently not enough here to return a visible reasoning trace.
OpenAI's current frontier model lineup is gpt-6-astra, gpt-6.1-sol, gpt-6.1-terra, gpt-6-luna, so here's a comparison grid of all of their pelicans at different reasoning levels: https://static.simonwillison.net/static/2026/openai-pelicans...
AISnakeOil 1 hour ago | parent
simonw 1 hour ago | parent
notatoad 1 hour ago | parent
drewbitt 1 hour ago | parent
ape4 1 hour ago | parent
bahmboo 1 hour ago | parent
johnnyApplePRNG 1 hour ago | parent
If not, yawn...
guybedo 1 hour ago | parent
Previous Terra model was so good it was discontinued.
OpenAi needs a model to compete with Opus 5.5, and that's not Terra 6.1.
sehw 1 hour ago | parent
cesarvarela 39 minutes ago | parent
mattfrommars 30 minutes ago | parent
My plan for OpenAI recently expired and now I’m thinking to test Anthropic ecosystem. My primary use case is programming only.
Should I go with API use or subscription? For coding harness, I jump between codex, OpenRouter, pi, whatever coding harness is trending on that day
c0rruptbytes 20 minutes ago | parent
shepherdjerred 14 minutes ago | parent
Anthropic does not allow you to use 3rd party harnesses -- you have to use Claude Code. Claude Code is an excellent harness, though.
If you want the freedom to move between harnesses you should use OpenAI or xAI
I_am_tiberius 59 minutes ago | parent
6thbit 55 minutes ago | parent
GPT-6 Astra
Input:$10.00 / 1M tokens Cached input:$1.00 / 1M tokens Output:$50.00 / 1M tokens
GPT-6.1 Sol
Input:$2.00 / 1M tokens Cached input:$0.10 / 1M tokens Output:$10.00 / 1M tokens
GPT-6.1 Terra
Input:$1.00 / 1M tokens Cache read:$0.05 / 1M tokens Output:$5.00 / 1M tokens
GPT-6 Luna
Input:$0.10 / 1M tokens Cached input:$0.01 / 1M tokens Output:$0.50 / 1M tokens
That's how their pricing tiers end up now. https://openai.com/business/pricing/#api(For some reason they say "Cache read" instead of "Cached input" for 6.1 Terra)
6.1 Astra and 6.1 Luna must be coming up soon. Will they reduce their prices further?
agentdev001 35 minutes ago | parent
causal 55 minutes ago | parent
agentdev001 31 minutes ago | parent
On AA intelligence index, this fills in the cost per task frontier nicely between 6 Luna and 6.1 sol. So when 6.1 Luna inevitably releases...
The OAI model tango seems to not have an end in sight, for better or worse. Give me more API toys!
gobwas 21 minutes ago | parent