← Latest · Archive

SEV-3OpenAI
2 sources standard

OpenAI published a blog post on 18 January 2026 outlining a shift in its business model toward pricing that "scales with the value of intelligence" [source]. The post describes a move away from fixed per-token or per-request pricing toward variable pricing tied to task complexity and perceived value delivered by its models.

The company states it will begin testing "value-based pricing" for certain enterprise customers, where costs adjust based on factors including task difficulty, model reasoning time, and business impact. OpenAI cites examples such as charging more for complex code generation or strategic analysis than for simple text summarization.

The announcement does not specify which models or API endpoints will be affected, nor does it provide a timeline for broader rollout. OpenAI states that existing pay-per-token pricing will remain available for standard API usage, but that "high-value tasks" may incur additional charges under the new model.

The post frames the change as aligning incentives between OpenAI and its customers, arguing that customers benefit when they pay in proportion to outcomes rather than compute usage. It does not address how value will be measured or whether customers will receive advance notice of variable charges.

Industry observers note that value-based pricing introduces uncertainty for developers building on OpenAI's platform, as costs may become less predictable. The model also raises questions about transparency, particularly whether OpenAI will disclose the criteria used to assess task value or allow customers to contest charges.

OpenAI has not responded to requests for clarification on implementation details or safeguards against unexpected billing.

Why this is an AI incident

Launch-archive bulk classification (10 May 2026). Source signal originates from a real AI provider, regulator, or model-comparison probe; the harm or behavioural change described would not have occurred without the AI system being deployed in the role described. Editor reviewing the archive may amend the rationale per-wire.

Counterfactual "but-for" test per the Editor's Guide.

Codes M1, F10
Providers OpenAI