OpenAI's New Rules Take Effect on November 20: AI Gateways Must Be Approved, Distilling Competing Models Explicitly Banned

OpenAI has updated its usage policy, effective November 20, to require prior approval for AI gateways and model routers and to ban using OpenAI model outpu

On October 21, 2026, OpenAI released an updated usage policy that will officially take effect on November 20. It is the company's most consequential adjustment to the AI ecosystem at the terms level—not through technical guardrails but through contractual obligations, redrawing who may distribute its model capabilities and who may learn from its outputs.

Two Core Changes: One Gate, One Prohibition Line

The first change targets intermediary service providers. Under the new policy, any service that operates a “model-access intermediary platform” or allows third parties to directly call OpenAI models must first obtain OpenAI's review and approval. Affected parties include model routers and AI gateways—platforms that resell OpenAI model capabilities to downstream developers in the form of a unified API.

OpenAI draws a specific boundary in the policy text: if an application merely calls OpenAI models to implement its own functionality, it is not subject to this constraint; but if a platform “wholesales” access to OpenAI models to external users, it must first pass OpenAI's review. In other words, whether one is a user or a reseller will have legally binding significance after November 20.

The second change is more fundamental. The new policy explicitly prohibits using OpenAI model outputs to provide training material for any “competing model intended to replace or supplant OpenAI models and services.” The prohibited scope is enumerated in considerable detail: creating training datasets, building scoring rubrics, setting up reinforcement learning (RLHF) environments, providing annotation labels, generating preference rankings, and filtering or screening training data. This prohibition even applies to cases “even if you do not train the final model yourself”—that is, even if you merely provide third parties with GPT-generated training material, it is still a violation.

The Direct Trigger: Distillation Suspicions Around Chinese AI Labs

These two changes did not emerge out of thin air. The tightening of policy is closely tied to persistent allegations—Chinese AI labs such as DeepSeek, Moonshot AI, Alibaba, MiniMax, StepFun, and Zhipu AI have been accused of extensively extracting reasoning outputs through OpenAI's API to train their own models.

“Distillation” is essentially a knowledge-transfer technique: using a large model's outputs as supervision signals to train a smaller model to reproduce its reasoning capabilities. This path is extremely efficient, especially when the large model itself has strong chain-of-thought reasoning capabilities. At its release, DeepSeek-R1 prompted speculation over whether some of its reasoning capabilities came from systematic distillation of outputs from OpenAI's o-series models.

OpenAI also offered a safety rationale—officials said that training OpenAI outputs on another model “can transfer capabilities, but not the safety safeguards at the same time.” This statement is intended to show that models competitors obtain through distillation possess some of GPT's capabilities but have not gone through the safety filtering mechanisms in OpenAI's alignment training.

The Real Logic of the Approval Mechanism

The gateway approval gate rests on a clear enforcement logic. When developers connect directly through the OpenAI API, OpenAI has complete account identity information; once a gateway layer is inserted in between, OpenAI effectively loses visibility into the actual end users—who is calling, how much they are calling, and for what scenarios are all obscured by the gateway.

The approval requirement amounts to re-establishing a trust anchor at this information gap. Before OpenAI approves a gateway, the operator must disclose to OpenAI its business model, safety measures, and enforcement mechanisms. The policy also requires partners to “maintain safeguards consistent with OpenAI's standards and coordinate enforcement efforts.” This means OpenAI not only reviews you but also makes you bear associated compliance obligations.

Multi-provider routing platforms such as Together AI and Perplexity are the most directly affected. The core value of such services is precisely “one API to access multiple models”—users can have the platform automatically route requests to different underlying models based on cost, speed, or task type. Once OpenAI's approval threshold intervenes, this kind of multi-model unified interface model must first obtain separate permission from each major model provider.

Nadella's Pushback: Double Standard or Reasonable Boundary?

The new policy has also triggered strong doubts from within the industry. Microsoft CEO Satya Nadella directly called the practice “ironic”—AI providers scrape public internet data to train their own models under the banner of “fair use,” while prohibiting customers from engaging in similar knowledge transfer from their outputs. Nadella also raised the concept of a “reverse information paradox”: the corrections, ratings, feedback, and other “exhaust” generated by users while using models actually help providers continuously improve their models, yet users never receive any reciprocal return.

Nvidia CEO Jensen Huang and Meta CEO Mark Zuckerberg have previously defended distillation, arguing that it is a necessary path for maintaining the competitiveness of U.S. open-weight models. The core question in this debate is: who do model outputs actually belong to? The company providing the service, or the user who pays to generate them?

OpenAI's position is the former, and it has grounded this position through contractual terms. This judgment is not without controversy, but its enforcement cost is extremely low—a violation means breaching the terms of service, and the account can be directly banned without any judicial process.

Exemption List: Research and Evaluation Remain Unrestricted

The new policy explicitly preserves several exemptions. Research, software development, model evaluation and benchmarking, and product development remain permitted as long as they fall within the boundaries defined by the policy. This means that using GPT for capability comparison tests, publishing academic analyses, or citing GPT outputs as references in products does not constitute a violation.

The policy also specifically states that if certain uses are explicitly permitted in your agreement with OpenAI, the agreement prevails. This leaves room for negotiation for large partners and also means that the same behavior may have completely different compliance status under different contractual frameworks.

Enforcement Capacity: The Biggest Unknown Variable

There has historically been a gap between a policy's legal force and its actual enforcement. OpenAI's current main enforcement tools are account bans and manual review when abnormal usage patterns are detected. But large-scale distillation operations often use dispersed accounts, proxy nodes, or third-party APIs, making detection extremely difficult.

The gateway approval system may be a more effective layer of defense. By requiring intermediary service providers to proactively declare and bear associated liability, OpenAI shifts enforcement pressure from its own technical monitoring to visible nodes in the ecosystem chain. A compliant gateway that has passed review may instead become an ally in helping identify abnormal usage.

But this logic has a premise: actors who truly want to circumvent the rules will not apply for approval. Gateways operating without approval, services operating in foreign jurisdictions, and operations that directly use the API for distillation will not stop because of this policy. The more likely effect of the new rules is to raise operating costs for existing compliant service providers while setting a higher entry barrier for new entrants that have not yet reached scale.

Independent Judgment

The essence of this policy is that OpenAI has completed a reaffirmation of ecosystem control at the commercial-terms level. Its strategic significance lies not in whether it can truly stop intentional distillation evasion, but in the fact that it has clearly drawn a legal line: OpenAI's outputs are OpenAI's ecosystem assets and must not flow free of charge into competitors' training pipelines.

For the AI industry, if this approval-plus-distillation-ban mechanism is followed by other major model providers—Anthropic already has similar terms—the data-flow landscape of the entire API economy will undergo a structural change: the diffusion speed of model capabilities will no longer depend only on technological iteration, but also on how tight or loose compliance boundaries are. And the intermediary service providers that currently rely on multi-provider routing are standing at the very front line of this boundary.