GPT-6.2 Sol vs Kimi K3.1 Pro
قارن النماذج
GPT-6.2 Sol is more worth it — 66% vs 40%
How we score worth-it? →OpenAI's everyday-work model: coding, documents and multi-step tasks at about a fifth of Astra's per-task cost.
- Looks like 6.1-sol high+ is equivalent to 6.2-sol medium at the same price. So a bit smarter at a cheaper cost.— hn ↗
- TL;DR - from the little I could gather, Sol 6.2 looks particularly impressive.— hn ↗
- As other commenters have pointed out, GPT 6.2 Sol does a better job at iterating on its own instead of saying "done" after making the first draft.— hn ↗
- I wouldn't go that far — 6.2 Sol is clearly more detailed than 6.1 Sol.— v2ex ↗
- 6.2-Sol feels a tad faster.— v2ex ↗
- For sol 6.2, some of them are slightly better at higher cost, some of them are way worse and only slightly cheaper— hn ↗
- Pelican is one legged on gpt 6.2 sol below high and has both legs on same side of the bicycle on high.— hn ↗
- I feel like "sol" is going to become a byword for "snail" from now on.— v2ex ↗
- Could it be that Fable 5.2 came in below OpenAI's expectations, which is why 6.2sol's price stayed unchanged — when during the grey test the quota was more than double that of 6.1?— bilibili ↗
- While evaluating a Max/MSP project through computer use, it asked me to make selections so it could move objects, presented very partial work, and stopped before reaching the original goal.— github ↗
“About one-fifth of Astra's per-task cost.”
“On FrontierCode 2.0 it trails Astra by only 0.5 points at max reasoning.”
“Same price as the previous Sol, with 6.2 improvements.”
2.8T params, beats GPT-6 Astra on Terminal-Bench
- It does pretty well for the price, around Sonnet 5.5.— hn ↗
- On mobile Kimi definitely wins from the UX point of view— hn ↗
- Genuinely honest about what it didn't build, security-conscious, and handled the keyboard protocol better than most models tested.— youtube ↗
- I'm really liking Kimi K3.1, including technical writing.— hn ↗
- Although models like GLM 5.3 are very close to Kimi K3 on benchmarks, Kimi K3 has far more parameters, which may be why it feels nicer to use. Kimi K3 understands what I mean better.— v2ex ↗
- Kimi didn't even finish the scan, ran out of the 5hr budget in less than 10 minutes. Unusable, unfortunately.— hn ↗
- I bought a yearly subscription to kimi when it was the hype and never use it. The 5h limit makes it completely unusable. You barely start doing anything and you hit the limit immediately. I advise everyone against using kimi.— hn ↗
- The subscription side has more complaints — people say the plan runs out within tens of minutes.— v2ex ↗
- If you've got money to burn, go ahead and use it.— v2ex
- Is it just me or Kimi K3.1 Pro don't look much better than DeepSeek 4.1 Flash?— reddit ↗
“The 1M context actually works. I dumped a whole codebase in and it kept track of everything”
“Terminal-Bench scores beating the top frontier models is not a fluke — it's genuinely that good at agent work”
“Half the price of the top frontier tier for comparable quality. The value is unreal”
Which should you pick?
The gap is clear: GPT-6.2 Sol sits at 66% while Kimi K3.1 Pro is at 40%, a 26-point difference. If you just want the safer pick, start with GPT-6.2 Sol.
They price differently (GPT-6.2 Sol: $2/$10 per 1M (cached $0.10); Kimi K3.1 Pro: $2/$10 per 1M), so estimate by your own usage.
Both are in the محادثة category with similar coverage; the real difference is stability and cost — run one of your own tasks through each before deciding.
What users actually said about GPT-6.2 Sol: "Looks like 6.1-sol high+ is equivalent to 6.2-sol medium at the same price. So a bit smart…"
FAQ
Is GPT-6.2 Sol or Kimi K3.1 Pro more worth it?
GPT-6.2 Sol is more worth it, with a 66% worth-it score vs 40% for Kimi K3.1 Pro.
How much does GPT-6.2 Sol cost vs Kimi K3.1 Pro?
GPT-6.2 Sol: $2/$10 per 1M (cached $0.10) · Kimi K3.1 Pro: $2/$10 per 1M.
What do users say about GPT-6.2 Sol vs Kimi K3.1 Pro?
GPT-6.2 Sol: About one-fifth of Astra's per-task cost.. Kimi K3.1 Pro: The 1M context actually works. I dumped a whole codebase in and it kept track of everything.