Competitive with opus 4.8 but weaker than sol or fable. About 20x cheaper.
Competitive with opus 4.8 but weaker than sol or fable. About 20x cheaper.
For DeepSeek V4 Pro the typical split is 750 in, 290 out, 82k cached.
Cost per request for V4 Pro: $0.000875 per request.
Equivalent Opus cost (w/o taking into account cache write costs): $0.052 per request.
ignore the numbers except the classic and keep in mind that classic is based on pi with the only change limiting tool output to 10kb
https://harness.eveid.com/lazy-harness-cost-simulation
* I built this for getting an initial estimate between different checkpoint/ compaction methods for the harness.
I don't mean to hype up the US AI firms, but if a ChatGPT $200/m subscription can get you $16,000 in effective API costs, doesn't effectively every model get destroyed by the subsidized Claude/ChatGPT models? Both in price and intelligence.
If I spent that every night it would be 3x my GPT subscription.
Cycle forward to Fable 7, Kimi 5, GPT 7 a couple years out. Forget about it unless you own a datacenter.
A single local user can run frontier models slowly on a 24/7 basis, which drops hardware requirements by orders of magnitude compared to a datacenter setup for just-in-time inference. This is not a real alternative to subsidized subscriptions at present, but it's a great insurance policy against future VC-driven rug pulls.
I keep track of my token consumption even on subscription plans and my equiv. cost for my 5.6-Sol usage is around $4000-$8000 a month.
Wonder how much more they'll squeeze out.
Wasn't worth it.
I was running a session over a couple days and it didnt cross a dollar lol.
I still find 5.6-Sol can solve some things neither of those can, but it's so slow (and it's so hard to trace / debug the reasoning) that I just let it run overnight.
I'm trying out a development workflow where I generate mundane code with MiMo and Luna (and soon V4 Pro 0813?) and have Opus 5, which is running on only a Pro subscription, review and refactor it. I'm not sure it will justify the context switching, but it's an interesting exercise.
And it wasn't tens* until recently. Didn't expect this to be one of my best performing assets this year.
Flash makes a lot more initial mistakes, and then has to re-check stuff, and produces much more output compared to Pro. It often gets to the correct result eventually, but the output volume is often 5x more than for Pro, and the initial outputs are often wrong, with the first few saying something wrong (like there's a bug, or the code won't compile when it does), and then saying things like "Wait, let me re-check:", or "Actually, looking at it more carefully:" and then it thinks a bit more and eventually gets to the right answer.
pro plans, flash implements. I am super happy with how flash behaves like that.