OpenAI's 80% Price Cut Is Real Evidence for Million-Token Production — But It's Still Not the Evidence We Need
OpenAI slashed GPT-5.6 Luna pricing by 80% on July 30, dropping to $0.20 per million input tokens — a number that starts to make million-token context window processing economically plausible at enterprise scale. textak holds our million-token production forecast at 61%, and today's pricing move is genuine positive signal. But we want to be honest about what it proves and what it doesn't, because there's a significant gap between 'this is now affordable' and 'Fortune 500 companies are using it in production today.'
The economics case for million-token production just got materially stronger. At $0.20/million input tokens, a single million-token context call costs $0.20. That's not a research budget line — that's a rounding error in most enterprise software budgets. Combined with what we've already logged — Kimi K3 at 1M context under Modified MIT license, DeepSeek V4 Pro at roughly 1/100th prior cost — the cost barrier to million-token production has collapsed faster than we modeled when we first set this forecast. The 61% reflects that cost collapse as a real tailwind.
Here's what we're weighting against it, and this is the part of our thesis that genuinely keeps us up at night: cost falling doesn't mean production adoption follows automatically. The forecast requires Fortune 500 companies deploying million-token windows in actual production workflows — not pilots, not internal experiments, confirmed production use. The strongest counterevidence in our data remains structural: enterprise workflows that could theoretically use million-token context are actively choosing agent-based chunked approaches instead. That preference exists not because million-token windows are too expensive (they're not anymore) but because chunked retrieval is more reliable, more auditable, and easier to debug when something goes wrong. Latency at million-token scale hasn't been solved by pricing.
The LG K-EXAONE 2.0 release (Story 11) at 262K-token context under Apache 2.0 is worth noting here — it's evidence that the frontier is settling around context windows well above standard enterprise use but below the 1M threshold. That middle-ground settlement pattern is circumstantial evidence that the production sweet spot may not be at 1M tokens, even if the cost argument is now resolved.
We're holding at 61% rather than moving higher because the evidentiary gap that matters most is unchanged: no Fortune 500 customer has been confirmed using million-token context in production today. The pricing move is proximate evidence — it shows conditions are forming — not direct evidence that production deployment has occurred. What would push us above 70%? A named Fortune 500 customer case study confirming million-token production workflow deployment, ideally with performance or cost-efficiency data. What would drop us below 50%? Evidence that enterprise architects are explicitly documenting decisions to cap context at 200K-400K for reliability reasons — that would suggest the ceiling is behavioral, not economic, and much harder to shift.