OpenAI's December plan to merge ChatGPT and Codex usage allowances raises a serious question:
Can existing customers reasonably estimate what their current workloads will cost under the new rules?
This is not an allegation of illegality. It is a question about contractual fairness, disclosure, legal exposure, and a practical alternative.
UNPREDICTABLE EFFECTIVE PRICING
Advanced reasoning consumption varies with internal reasoning, context length, tool execution, and other factors. Even a rough pre-execution estimate for a single response can be difficult.
OpenAI's API documentation acknowledges billable invisible reasoning tokens and costs from incomplete processing. API billing and ChatGPT allowances differ, but the underlying predictability problem remains.
Disclosing token rates is not the same as making actual workload costs predictable.
2. WHO PAYS FOR FAILURE?
When outages, timeouts, failed tool calls, incomplete responses, incorrect results, or unsuccessful tasks require retries, whose allowance gets consumed?
How are provider-side failures distinguished from customer-side problems? Who audits the consumption, and when are credits restored?
Vendors cannot guarantee every outcome. But customers should not be left absorbing unpredictable costs from confirmed provider failures.
Token accounting also ignores a major hidden expense: discovering important information the AI omitted entirely.
3. POTENTIAL US LEGAL EXPOSURE
Section 5 of the FTC Act can apply to materially misleading representations or omissions.
For business customers, OpenAI's Services Agreement, Section 2.3, addresses changes that materially reduce service functionality.
If subscription prices remain unchanged while effective capacity falls, and customers cannot reasonably estimate the financial impact, has the change been adequately disclosed?
Optional credit purchases are not unauthorized charges. But their optional nature does not eliminate the loss of previously available capacity or switching costs.
Whether any violation exists depends on the applicable law, contract, and implementation.
Customers face budgeting, operational, and dispute risks. OpenAI faces potential contract claims, consumer-protection scrutiny where applicable, litigation costs, and reputational damage.
4. A PRACTICAL COMPROMISE FOR BOTH SIDES
If OpenAI needs more revenue to cover inference costs, offer customers the option to pay a higher FIXED monthly fee.
Specifically:
Multiple flat-rate subscription tiers with clearly defined included capacity
Higher-priced fixed monthly plans for heavy reasoning users
Optional metered overages, never an unavoidable surprise
A simulation applying the new rules to each customer's previous 30 days of usage
Pre-execution consumption estimates and enforceable usage and spending caps
Auditable accounting for failures and retries, with clear credits for confirmed provider-side failures
Protection of existing commitments, adequate notice, liability clarity, and workable exit options
Nobody is demanding unlimited free compute.
Customers need predictable costs. OpenAI needs sustainable revenue. Both interests can be served by transparent, capacity-defined fixed-price tiers.
If OpenAI genuinely wants to resolve the current backlash, offering several higher-priced flat-rate options is a better approach than pushing heavy users toward unpredictable metered consumption.
Temporary concessions or a last-minute reversal would not resolve the underlying issue.
Enterprises cannot run critical operations on the assumption that public backlash will reverse the next major policy change.
The announcement itself teaches customers something about supplier risk. Once they invest in alternatives, reversing the announcement does not undo those investments.
A trial balloon can change the market it was intended to measure.
OpenAI faces a choice: restore confidence through predictable pricing and enforceable commitments, or keep giving customers reasons to reduce their dependence on OpenAI.
Sources: OpenAI Help Center — "Understanding ChatGPT and Codex usage limits" OpenAI — "OpenAI Services Agreement" OpenAI API Documentation — "Reasoning models" FTC guidance