AnyLearn
All lessons
Businessadvanced

The Enforcement Gap

Competition law was built to catch people agreeing in rooms. What happens when the coordination has no agreement, no communication, and no human intent, and how regulators are responding anyway.

Updated · AI-authored, review-gated · how lessons are made

Not signed in: your progress and quiz score won't be saved.
Progress1 / 9

What the law prohibits

Competition law does not prohibit high prices. This is the single most important thing to understand about the legal position, and it surprises most people.

The prohibition targets agreement. Section 1 of the US Sherman Act reaches contracts, combinations, and conspiracies in restraint of trade. Article 101 of the Treaty on the Functioning of the European Union reaches agreements between undertakings and concerted practices. Both require a meeting of minds between competitors.

Charging a high price alone is legal. Charging the same price as a competitor is legal. Watching a rival's prices and matching them is legal. What is illegal is agreeing with the rival to do so.

The reason is practical. In a concentrated market, firms can reach high prices simply by each recognising their interdependence, without any communication. Economists call this conscious parallelism or tacit collusion. It is economically harmful and, in most jurisdictions, lawful, because there is no agreement to prohibit and no conduct a court could order a firm to stop.

Algorithmic collusion lands directly in that pre-existing hole.

Full lesson text

All 9 steps on one page, for reading, reference, and search.

Show

1. What the law prohibits

Competition law does not prohibit high prices. This is the single most important thing to understand about the legal position, and it surprises most people.

The prohibition targets agreement. Section 1 of the US Sherman Act reaches contracts, combinations, and conspiracies in restraint of trade. Article 101 of the Treaty on the Functioning of the European Union reaches agreements between undertakings and concerted practices. Both require a meeting of minds between competitors.

Charging a high price alone is legal. Charging the same price as a competitor is legal. Watching a rival's prices and matching them is legal. What is illegal is agreeing with the rival to do so.

The reason is practical. In a concentrated market, firms can reach high prices simply by each recognising their interdependence, without any communication. Economists call this conscious parallelism or tacit collusion. It is economically harmful and, in most jurisdictions, lawful, because there is no agreement to prohibit and no conduct a court could order a firm to stop.

Algorithmic collusion lands directly in that pre-existing hole.

2. The gap, stated precisely

Bichler, Durmann, and Oberlechner put the problem in one sentence: even if a competition authority were to identify a potential case of tacit collusion, the current state of the law could make such practice irreproachable in the absence of explicit communication or contact among the companies using such autonomous algorithms.

Irreproachable is the operative word. Not hard to prove. Not requiring new evidence. Potentially lawful, because the conduct element the statute requires is genuinely absent.

The difficulty compounds when you ask who would be liable if it were unlawful. The firm did not instruct the software to collude. The vendor sold a profit-maximising tool. The developers implemented a standard algorithm from a textbook. Intent, which most enforcement regimes rely on somewhere, is distributed until it disappears.

And the usual remedy fails too. Cartel enforcement works partly because participants can defect and report each other for leniency. There is nobody to defect here, and no agreement to confess to.

So the gap is not evidential. It is definitional, and it cannot be closed by better investigation.

3. Where enforcement actually succeeds

Faced with that gap, regulators have concentrated on cases that do not require crossing it, and there is a clear pattern in which ones work.

The UK poster case noted by Bichler and colleagues involved online retailers using simple pricing algorithms as part of a horizontal cartel to coordinate prices on Amazon. There was a cartel; software executed it. Conventional law applies straightforwardly.

The European Commission's 2023 guidelines stipulate that explicit agreements to use the same pricing algorithm violate Article 101. Again, the violation is the agreement, not the algorithm.

The generalisation is worth stating as a rule. Enforcement succeeds where there is a human agreement somewhere in the picture, or a hub-and-spoke structure in which competitors do not talk to each other but each shares information with a common intermediary that feeds back into everyone's prices.

That second structure is not hypothetical, and it produced the most consequential case in this area so far.

4. The RealPage case

On 23 August 2024, the US Department of Justice filed a civil antitrust suit against RealPage, a revenue management software company, in the Middle District of North Carolina, joined by the attorneys general of North Carolina, California, Colorado, Connecticut, Minnesota, Oregon, Tennessee, and Washington.

The allegation, brought under Section 1 of the Sherman Act, was that RealPage used nonpublic, competitively sensitive information from competing landlords in generating its pricing recommendations, and discouraged independent pricing decisions, thereby facilitating price alignment.

Note the shape of the theory. It does not depend on proving that an algorithm learned to collude. The alleged mechanism is the flow of confidential competitor data through a common intermediary, which is a recognisable hub-and-spoke arrangement that existing doctrine can reach.

On 24 November 2025 the DOJ filed a proposed settlement. RealPage did not admit liability and agreed to no fine, but accepted conduct restrictions for a seven-year term, subject to court approval.

The terms are the interesting part, because they read as a template.

5. What the settlement regulates

The proposed settlement imposes detailed guardrails on RealPage's rent-pricing tools: how they may use competing landlords' nonpublic data, how pricing features are designed, and how competitively sensitive information may be collected and shared.

One restriction is unusually concrete and worth understanding. RealPage is forbidden from providing rental pricing data to its subscribers at a granularity narrower than state-wide.

The reasoning is that competitive sensitivity is a function of resolution. Knowing average rents across an entire state is market intelligence: it cannot tell you what the building across the street is charging. Knowing average rents for your immediate submarket, where you may face three competitors, is close to knowing their prices. Same category of data, entirely different competitive effect.

So the settlement does not ban the software, the data, or the recommendations. It regulates the resolution at which competitor information flows.

That is a genuinely new regulatory instrument, and it suggests where this area is heading: not toward banning algorithmic pricing, but toward constraining what data may enter it and at what granularity.

6. Which cases the law can reach

Three structures, three legal outcomes. The first two are reachable under existing doctrine because a human agreement or a data intermediary exists. The third, independent algorithms converging without any connection between firms, is the one that falls outside, and no enforcement action has closed it.

flowchart TD
  A["Parallel high prices observed"] --> B{"Is there human agreement?"}
  B -- yes --> C["Classic cartel, software is just the tool"]
  B -- no --> D{"Shared data intermediary?"}
  D -- yes --> E["Hub and spoke, reachable as in RealPage"]
  D -- no --> F["Independent algorithms converging"]
  F --> G["No agreement element, potentially lawful"]
  G --> H["The enforcement gap"]

7. Proposed responses

The policy conversation is active across jurisdictions. Bichler and colleagues note that the OECD and multiple countries including France, Germany, Denmark, Japan, Norway, and Sweden have published policy papers, and that the US Preventing Algorithmic Collusion Act of 2024 emphasises transparency.

Four categories of proposal recur, and they trade off differently.

Transparency requirements, making algorithmic decision-making visible to regulators. Useful for investigation, but a learned policy is not self-explanatory even when fully disclosed, which is why the interpretability problem is not merely technical.

Design constraints, guidelines discouraging collusive strategies. Klein's proposal fits here: require simultaneous rather than sequential price updates, and prohibit conditioning on price history. Precise, but it forbids ordinary responsiveness too.

Real-time monitoring, detection algorithms identifying collusive pricing patterns. Klein's cycling result is the warning: naive detectors looking for stable high prices miss the cycling case.

Regulatory audits, compliance testing requiring firms to disclose pricing algorithms.

Every one of these imposes costs on lawful, pro-competitive uses. Klein's own caution applies to all of them: pricing algorithms have many pro-competitive effects, and prohibiting their use would be excessive.

8. Practical compliance

For anyone deploying pricing software, the RealPage settlement and the case law point to a workable set of distinctions.

PracticeRisk
Optimising on your own sales and inventoryLow
Using publicly posted competitor pricesLow, this is ordinary observation
Agreeing with a rival to use the same toolHigh, direct Article 101 and Sherman Act exposure
Feeding nonpublic data to a shared vendorHigh, the RealPage theory
Receiving fine-grained rival data from a vendorHigh, granularity is what the settlement restricts
Software that discourages independent deviationHigh, was part of the DOJ allegation

The organising question is not whether you use an algorithm. It is where its inputs come from and whether you remain free to deviate.

Two gotchas. First, vendor assurances are not a defence: the DOJ theory targeted the data flow through the vendor, so a vendor's compliance claim does not resolve your exposure. Second, no admission is not vindication: RealPage settled without admitting liability and without a fine, yet accepted seven years of conduct restrictions. Read the restrictions, not the absence of a penalty, as the signal about what regulators consider problematic.

9. What this path establishes

Four claims, stated at the strength the evidence supports.

The mechanism is demonstrated, in simulation. Independent Q-learning agents in a standard oligopoly model reach supra-competitive prices sustained by finite punishment and gradual return to cooperation, with no communication and nobody programming the strategy.

The generalisation is genuinely contested. Large exploration parameters eliminate it, transfer across environments often breaks it, convergence conditions are poorly understood, and there is little evidence that deployed pricing software uses reinforcement learning at all.

The field evidence shows an outcome, not a mechanism. German fuel margins rose 9 percent with adoption in non-monopoly markets and 28 percent in duopolies where both stations adopted, a pattern consistent with softened competition, but nobody observed the algorithms.

The legal gap is definitional. Competition law requires agreement, tacit coordination without communication is largely lawful, and enforcement to date has succeeded only where a human agreement or a data intermediary existed.

The useful mental model: this is not a settled harm awaiting enforcement, nor a phantom. It is a demonstrated possibility whose real-world prevalence is unknown, sitting in a legal category built for a different problem.

Check your understanding

The lesson ends with a 5-question quiz. Take it in the player above to see your score.

  1. Why does algorithmic collusion sit outside conventional competition law?
    • Software is exempt from antitrust statutes in most jurisdictions
    • Prohibitions target agreement between competitors, and tacit coordination without communication supplies no agreement to prohibit
    • Prices set by algorithms are treated as trade secrets
    • Only criminal statutes apply to pricing conduct
  2. What was the legal theory in the DOJ's case against RealPage?
    • That its algorithm had learned a punishment strategy against deviating landlords
    • That charging above-market rents is itself unlawful
    • That it used nonpublic competitor data in pricing recommendations and discouraged independent pricing
    • That landlords had signed an explicit agreement to fix rents
  3. Why does the RealPage settlement restrict data granularity to state-wide level?
    • State-level data is cheaper for the vendor to compile
    • Federal jurisdiction extends only to state-level commerce
    • Narrower data would violate tenant privacy law
    • Competitive sensitivity depends on resolution: submarket data approximates knowing your immediate rivals' prices
  4. What does Klein's finding about price cycling imply for regulatory monitoring?
    • Detectors looking for stable high prices would miss markets cycling around a supra-competitive average
    • Monitoring is unnecessary because cycling indicates competition
    • Cycling markets are always more competitive than stable ones
    • Real-time monitoring can only detect collusion in monopoly markets
  5. For a firm deploying pricing software, which practice carries the highest legal risk?
    • Optimising prices against its own sales and inventory data
    • Adjusting prices in response to publicly posted competitor prices
    • Contributing nonpublic pricing data to a vendor shared with competitors
    • Changing prices more frequently than competitors do

Related lessons

Law & Compliance
advanced

Proof: Disclosure, Presumptions, and the Complexity Rule

Strict liability is worthless if the claimant cannot prove a defect they never saw. Articles 9 and 10 answer that with a disclosure order, three presumptions of defectiveness, a presumption of causation, and a rule turning complexity into the claimant's ally. This lesson works through the cascade, the three-year and ten-year clocks, and what a defendant should be able to produce.

10 steps·~15 min
Law & Compliance
advanced

Who Pays, and For What Damage

The Directive builds a chain of liable operators so an injured person in the EU always has someone to sue. This lesson covers the manufacturer and component manufacturer, the importer and fulfilment service provider route, the distributor's one-month rule, online platforms, how a modification makes you a manufacturer, the heads of damage including data loss, and the exemptions.

10 steps·~15 min
Law & Compliance
advanced

Defectiveness: The Safety a Person Is Entitled to Expect

A product is defective when it lacks the safety a person is entitled to expect. Article 7 turns that into circumstances a court weighs, several written for software: the ability to learn after release, interconnection, cybersecurity requirements, and recalls. This lesson works through the list, the rule that a later improvement is not an admission, and why compliance is not a defence.

10 steps·~15 min
Law & Compliance
advanced

Software as a Product: What the New Liability Directive Changed

Directive (EU) 2024/2853 replaces the 1985 regime and settles a forty-year argument by naming software a product. This lesson covers the new definition and why delivery method is irrelevant, why information is not a product, how components and related services extend the net, where open source sits, and why liability cannot be disclaimed by contract.

10 steps·~15 min