AI slowdown coordination faces a US antitrust challenge
A proposed class action alleges that Anthropic, OpenAI, SpaceXAI and Google crossed an antitrust line by coordinating calls to slow frontier-AI development. The companies had not responded publicly when the suit was reported.

The story
A proposed US class action is testing whether cooperation among frontier-AI companies on safety and development pace can be treated as unlawful coordination among competitors. The complaint, filed on September 18 in the US District Court for the Northern District of California, names Anthropic, OpenAI OpCo, SpaceXAI and Google. Four paying subscribers brought the case on behalf of a proposed nationwide class of customers who purchase access to ChatGPT, Claude, Grok or Gemini. The case is Buist et al. v. Anthropic, PBC et al., number 3:26-cv-10693.
The central allegation is not that an individual company lacks the right to slow its own work for safety reasons. Instead, the plaintiffs argue that the companies reached a horizontal agreement to reduce the pace at which competing AI products improve. According to Associated Press reporting on the complaint, the plaintiffs say such coordination would reduce the value of paid subscriptions and restrain competition. These are allegations at the opening of a civil case. No court has determined that an agreement existed, that it affected product output, or that any defendant violated antitrust law.
The complaint points to public statements made after Anthropic chief executive Dario Amodei called for an industry-wide approach to what he described as pacing the frontier. It also cites supportive responses by leaders associated with OpenAI, SpaceXAI and Google DeepMind. The plaintiffs interpret those statements as evidence of coordinated restraint. Public support for a policy proposal, however, is not automatically the same as a binding commercial agreement. That distinction is likely to be central if the defendants seek dismissal or challenge whether the complaint plausibly alleges concerted action.
The policy problem behind the dispute is real even if the legal theory remains untested. Frontier developers face pressure to release capable models before rivals while also warning that the systems require stronger evaluation, security and oversight. A company that slows alone may lose customers, talent or capital. Coordination can therefore make safety commitments more credible, but the same mechanism can resemble an agreement among dominant suppliers to limit output or innovation. Antitrust law and AI-safety policy are approaching the same conduct from different directions.
Amodei had acknowledged the collision. AP reported that his proposal said government mediation, or a narrow waiver for certain safety conversations, could help companies discuss shared limits without creating antitrust exposure. OpenAI chief executive Sam Altman separately supported a consistent federal safety framework while arguing that firms need not wait for new legislation or an exemption to improve safeguards. Those positions leave substantial room between common safety standards, which can benefit users, and coordinated decisions about training, compute or product release schedules, which can alter competition.
The complaint seeks relief for paid subscribers, but its implications could reach beyond consumer pricing. Frontier-model competition influences developer access, enterprise procurement, research publication and the speed at which capabilities spread internationally. A ruling that treats certain safety coordination as presumptively suspect could make companies more cautious about joint evaluations or shared thresholds. A ruling that accepts broad coordination without clear limits could, by contrast, give incumbent firms a way to shape the market while presenting their choices as safety policy. Neither outcome would eliminate the need for public rules.
The early record also contains important absences. AP said representatives for the four defendants did not immediately respond to its request for comment. The public reporting does not establish implementation details showing that a company delayed a model, reduced compute or changed a release because of an agreement. Nor does the filing itself prove harm to subscribers. The defendants will have opportunities to dispute the factual account, the definition of the proposed class, the alleged injury and the connection between public statements and competitive conduct.
The strongest policy response may be a framework that separates legitimate safety collaboration from commercial restraint. Government-defined reporting rules, independent evaluations and transparent capability thresholds can create common obligations without letting competitors privately decide how quickly the market should move. The lawsuit now puts pressure on courts to examine that boundary before lawmakers have supplied a comprehensive answer. For readers and customers, the immediate fact is narrow: a complaint has been filed and a contested legal process has begun. The wider significance will depend on evidence, judicial rulings and whether regulators create a clearer route for verifiable safety coordination.
INNOVOX analysis
The case exposes a governance gap. Private coordination may solve the incentive problem that makes unilateral safety restraint difficult, yet private competitors should not be allowed to set market-wide output limits without scrutiny. Transparent government rules and independent evaluations are more durable than either unchecked racing or an opaque industry pact. The legal merits remain unresolved, but the policy tension is already unavoidable.
What to watch
Watch for the defendants' first responses, any motion to dismiss, and evidence that connects public statements to actual decisions about training, compute or releases. Also watch whether Congress or federal agencies define a safe harbor for narrowly tailored technical safety work while preserving competition in products and research.
