News

Recent developments in algorithmic pricing: U.S. appeals court weighs in, enforcers stay aggressive, and open questions remain

Data Center
Data Center

As we have previously reported, antitrust enforcers at the Department of Justice (DOJ), Federal Trade Commission (FTC), and offices of state attorneys general, as well as private plaintiffs, have been heavily scrutinizing the use of algorithmic pricing tools.  This alert provides further updates on recent developments in U.S. federal courts, where principles are emerging regarding what sort of concerted action involving algorithmic pricing might state a claim under the Sherman Act, while lower courts continue to wrestle with which mode of antitrust analysis to apply to these cases.  We also provide an update on recent federal and state enforcement, which may provide some guidance to those using algorithmic pricing products or services, as well as ongoing efforts by state and local lawmakers to fill an enforcement gap through legislation that would ban or limit the use of algorithmic pricing in certain industries.

The first federal appellate decision on algorithmic pricing provides clarity on some, but not all, of the many challenging legal issues surrounding these practices

In Gibson v. Cendyn Group, the Ninth Circuit1 agreed with a lower court ruling2 that it does not violate Section 1 of the Sherman Act for competing hotels to independently use the same third-party pricing software to generate recommended pricing for their hotel rooms, at least where there was no underlying agreement amongst the competitors to do so, and where the software did not share any licensing hotel’s confidential information among competing licensees. The Ninth Circuit found that not even a rule of reason analysis is warranted in cases where there is no causal link between the purported agreement and an anticompetitive restraint. The Gibson decision marks the first time a U.S. appellate court has applied the antitrust laws to cases involving algorithmic pricing systems and is a significant addition to the rapidly developing caselaw addressing these issues.

At the initial stage of the case, the District of Nevada ruled that the plaintiffs had failed to plead that the hotel defendants’ independent licensing agreements to use a common pricing software was equivalent to an agreement on price.3 On appeal, the Ninth Circuit ruled that the independent licensing agreements with software provider Cendyn do not constitute a restraint of trade because: (1) the defendants did not agree amongst each other to follow Cendyn’s pricing recommendations (and parallel conduct absent an agreement is insufficient to state a claim under Section 1); and (2) “antitrust law provides no mechanism by which courts can evaluate the independent agreements between Cendyn and each Hotel Defendant ‘in the aggregate.’”4 The Ninth Circuit rejected the plaintiffs’ characterization of the contracts as vertical agreements between Cendyn and the hotels, since “relative to Hotel Defendants, Cendyn is not up or down the supply chain in the relevant market: hotel-room rentals on the Las Vegas Strip . . . [and] the software is not an input that goes into the production of hotel rooms for rentals.”5 The Ninth Circuit also concluded that, while “increased prices can serve as evidence of ‘a substantial anticompetitive effect’ in the context of certain agreements . . . that does not mean an individual firm’s independent choice to charge higher prices itself harms competition . . . [and] charging a higher price by itself is not anticompetitive.”6

The Ninth Circuit’s ruling provides some clarity on whether and how the use of algorithmic pricing software may violate the antitrust laws, and what the relevant considerations will be for courts making this determination. However, as the court pointed out, the plaintiffs had not “allege[d] that Cendyn pools, shares, or uses the confidential information provided by a given Hotel Defendant into the pricing recommendations it generates for any other Hotel Defendant.”7 Accordingly, the Ninth Circuit’s opinion did not address the antitrust implications of a tool that generates pricing suggestions based on the confidential information from competitors. In addition, the Ninth Circuit was not tasked with reviewing the district court’s dismissal of the plaintiffs’ allegation that the hotels entered into a “hub-and-spoke” agreement to utilize Cendyn’s revenue-management software and adopt the algorithm’s pricing recommendations.8 But the court made clear that “it would undoubtedly violate Section 1” if the hotels “agree among themselves to abide by a third party’s pricing recommendations,”9 and that such an agreement “would be a hub-and-spoke conspiracy”10 that would be “analyzed according to the per se rule and the rule of reason, as applicable.”11

A very similar case is now on appeal to the Third Circuit, after the District of New Jersey granted a motion to dismiss in a lawsuit targeting different hotels’ use of the same software at issue in Gibson. Like the lower court in Gibson, the New Jersey court ruled that, because the plaintiffs did not allege that the algorithmic software at issue used competitors’ nonpublic, proprietary data to generate pricing recommendations, they failed to allege an illegal hub-and-spoke conspiracy.12

Lower courts continue to debate whether to apply the per se approach or rule of reason

The question left open in Gibson—whether to apply the per se rule or the rule of reason in cases alleging price fixing through algorithmic pricing—continues to vex the lower federal courts.

In April 2023, a federal court in Tennessee ruled in the ongoing RealPage litigation—a private plaintiff class action challenging multifamily residential lessors’ use of RealPage’s revenue management software—that it is not per se illegal for competitors to use a common pricing tool, at least where there was no direct evidence of a direct agreement among the competitors, and where plaintiffs failed to allege that RealPage or any of the lessors “can enforce acceptance of price recommendations” provided by the algorithmic pricing tool.13 Instead, the judge held that a rule of reason analysis applied to plaintiffs’ Section 1 claim, and in applying that standard, denied defendants’ motion to dismiss.14 Then, a few months later in Duffy v. Yardi Systems, a case involving similar allegations, a federal judge in Washington held that where plaintiffs adequately alleged “both invitation and acceptance and sufficient plus factors to give rise to a plausible inference of a preceding agreement” and that defendants implemented the software’s pricing recommendations, the per se standard should apply.15 Judge Lasnik noted in his Duffy opinion that he “respectfully disagrees” with the RealPage ruling, saying that “[t]he point of the per se rule and rule of reason analysis is not to create a heightened pleading standard related to the existence or purpose of the conspiracy, but to determine whether the restraint on trade is ‘unreasonable’ for purposes of § 1. Chief Judge Crenshaw [in RealPage] cites no authority for judging the reasonableness of an adequately alleged conspiracy to restrain trade by the strength of the conspiracy allegations.”16

More recently, in June 2025, a federal court in Illinois denied a motion to dismiss a consolidated class action complaint alleging that defendants—health insurance data analytics firm MultiPlan and several health insurance companies—unlawfully conspired to underpay out-of-network health care providers by outsourcing rate-setting to MultiPlan.17 The court found that that plaintiffs had sufficiently alleged that third-party payors who contracted to use MultiPlan’s rate calculation software and negotiation services collectively agreed to fix prices for out-of-network service payments by sharing sensitive information that MultiPlan used in its algorithmic software to “align” rates for payors. The court in its ruling applied the per se standard, noting that “horizontal price-fixing agreements are per se illegal,” and that “the plaintiffs have plausibly alleged a horizontal hub-and-spokes price-fixing agreement.”18

DOJ and State AGs continue to pursue antitrust enforcement targeting algorithmic pricing tools, and early settlements may shed light on evolving standards

Under the leadership of AAG Abigail Slater, DOJ has reasserted a commitment to antitrust enforcement targeting “algorithmic collusion” that was first established during the Biden administration. In a recent video statement on social media, AAG Slater said that she expects the number of DOJ Antitrust Division investigations into potential collusion through algorithmic pricing to grow, and that DOJ is “not afraid to litigate” these cases. Slater also advised firms to “perform their own due diligence on shared algorithms inputs and functionality to prevent collusion that can harm consumers.”19

DOJ’s lawsuit against RealPage and six multifamily residential lessors is currently making its way through federal court in North Carolina. The government alleges that RealPage violated both Section 1 and Section 2 of the Sherman Act because: (1) RealPage’s revenue management software collects competitively sensitive data from landlords and generates rental pricing recommendations; and (2) the landlords agreed both with RealPage and each another to share nonpublic, sensitive information, both indirectly through the RealPage software, and directly.20 The amended complaint also alleges that, in combination with the use of RealPage’s pricing algorithms, the defendants’ coordination is “even more likely to restrain, rather than promote, competition.”21 But as we outlined in a prior client alert, DOJ’s amended complaint against RealPage—which ten states have joined as co-plaintiffs—does not allege that the conduct is a per se violation of Section 1.22 In other recent comments, AAG Slater noted that “there’s nothing wrong with using algorithms,” but that the RealPage tool “was running on proprietary, competitive, sensitive data that went to output [and] price,” and that where certain “parameters are in place”—like the algorithm’s being shared by competitors and “relying on sensitive data”—then “it can lead to bad, anticompetitive outcomes.”23

On August 8, 2025, DOJ announced24 a settlement with one of the lessor defendants, which may provide some guidance on what DOJ believes is an appropriate use of pricing algorithms. If approved, the proposed final judgment25 would, among other provisions, prevent use of any revenue management product that uses external, nonpublic data to generate rental prices or rental pricing recommendations, or uses a model or algorithm trained on nonpublic data.26

Nevada is not a co-plaintiff in the DOJ’s case against RealPage, but the Nevada attorney general recently announced that it had entered into a consent judgment with RealPage in state court, agreeing to settle allegations of anticompetitive conduct involving use of the software in the state. The settlement is RealPage’s first in this wave of antitrust enforcement and litigation, and while RealPage provided no admission of wrongdoing or liability, the settlement terms limit RealPage to only:

  • Use the nonpublic data of other unaffiliated properties in the runtime operation of its revenue management software to calculate recommendations for properties in Nevada if the data is at least three months old, anonymized, and aggregated to at least ten properties;
  • Publish nonpublic data regarding rent, occupancy or availability to its customers in Nevada if the data is aggregated to at least ten properties and anonymized;
  • Use machine learning models trained with nonpublic data from properties in Nevada if the data is aged at least three months.27

States and municipalities seek legislation banning residential real estate companies’ use of algorithmic pricing tools

Over the past year, many states and municipalities have introduced ordinances prohibiting the use of certain algorithmic devices or services to set rents or occupancy levels for residential rental units. The San Francisco Board of Supervisors enacted one of the first such ordinances in October 2024.28 Similar ordinances are currently in effect in Providence, Rhode Island; Hoboken, New Jersey; Jersey City, New Jersey; Seattle, Washington; San Diego, California; Minneapolis, Minnesota and Philadelphia, Pennsylvania.29 Generally speaking, these ordinances prohibit the use or provision of algorithmic tools that incorporate certain nonpublic competitor information provided by competing real estate lessors to generate suggested rental prices, lease terms, and/or occupancy levels for users.30 What qualifies as “nonpublic competitor information” under these ordinances varies by municipality. For example, Jersey City’s ordinance limits its ban to those algorithmic pricing systems that produce rental pricing or occupancy recommendations based on nonpublic competitor information that is less than 365 days old;31 the statutory definitions of “nonpublic competitor information” in the San Diego32 and Minneapolis ordinances33 do not include that sort of date limiter.

Similar laws have been introduced in the state legislatures in California, Illinois, Massachusetts, Michigan, New Jersey, New York, North Carolina, Ohio, Pennsylvania, and Wisconsin. To date however, no state has enacted a law banning the use or sale of algorithmic pricing devices in residential real estate markets. The Colorado state legislature passed a law that would have prohibited the sale or use of an algorithmic device to competing landlords that recommends and sets the amount of rent, level of occupancy, or other commercial term associated with the occupancy of a residential premises; however, Governor Jared Polis vetoed the bill in May 2025.34

Takeaways

With the state of play continuing to evolve, few certain predictions can be made about what is next in antitrust enforcement against algorithmic pricing tools. But there are at least some clear takeaways from these recent developments:

  • First, although labels like “algorithmic pricing” and “A.I. tool” are used often and interchangeably, these technologies do not all offer the same functionality or present the same antitrust risk. Companies relying on pricing tools that might fit under the “algorithmic pricing” umbrella must have an exacting understanding of those tools' terms of use, including, e.g., whether the tool automatically implements pricing recommendations, and the sources of the information provided to the tool.
  • Second, early indications that courts might be hesitant to apply the per se standard in any cases involving algorithmic pricing, because the technology and practice was relatively new, have not endured, and several federal courts have allowed per se claims to proceed past motions to dismiss.
  • Third, despite the modern technology at issue in these cases, courts seem to be looking for familiar hallmarks of potentially anticompetitive conduct—agreements among competitors to, e.g., follow the recommendations of a shared tool, and an exchange of competitively sensitive information. Even where courts do not find the per se standard appropriate, the nature of a given market (i.e., the degree of concentration, barriers to entry) can elevate the antitrust risk.
  • Finally, although the federal agencies usually lead on antitrust enforcement priorities, amidst some relative uncertainty in the caselaw, state and local authorities are increasingly looking to ramp up enforcement, even if that means pushing the law to more aggressively police these practices. It is essential that companies who may have antitrust risk exposure track not only DOJ and FTC developments, but also be mindful of nuanced distinctions in new state and local laws as well.

For companies that are currently using or considering investing in algorithmic pricing tools, experienced antitrust counsel like the team at Hogan Lovells can help navigate the enforcement and legal uncertainty and help you understand how developments at the federal, state, and local level might impact your business's risk exposure.

 

 

Authored by Ben Holt, Claude Szyfer, Holden Steinhauer, and Jill Ottenberg.

References

1 Opinion, Gibson v. Cendyn GroupLLC, 148 F.4th 1069  (9th. Cir.) (hereafter “Gibson 9th Circuit Opinion”).

2 Order, Gibson v. Cendyn Group, LLC et al., No. 23-cv-00140, 2024 WL 2060260, at *1–9 (D. Nev. May 8, 2024).

3 Id

4 Gibson 9th Circuit Opinion at 1087.

5 Id. at 1081–82 (citations omitted);  6 Phillip E. Areeda & Hovenkamp, Antitrust Law (5th Ed. 2023) ¶ 1437a) (“The agreement appears to be an ‘ordinary sales contract,' which, according to a leading antitrust treatise, ‘does not restraint trade' and ‘without [which], trade would be impossible.”)

6 Id. at 1087–88 (citation omitted).

7 Id. at 9.

8 Plaintiffs abandoned their appeal of the district court's dismissal of this hub-and-spoke claim. See id. at 10.

9 Id. at 1076

10 Id. at 1085 n. 10.

11 Id. at 1081.

12 See Cornish-Adebiyi v. Caesars Entertainment, Inc., No. 23-cv-02536, 2024 WL 4356188, at *4 (D.N.J. Sep. 30, 2024) (“[T]he purported hub-and-spoke conspiracy in this case is nearly identical to that pled in [Gibson] . . . .”). 

13 See In re RealPage, Inc., Rental Software Antitrust Litig. (No. II), 709 F.Supp.3d 478, 520 (M.D. Tenn. Dec. 28, 2023).  The RealPage decision noted that “courts are hesitant to apply the per se standard to new or ‘novel way[s] of doing business' that have not yet been tested or studied by economists to conclusively determine that these types of conspiracies are per se anticompetitive.”  See id. (citation omitted).

14 Id. at 536–37.

15 Order Denying Defendants' Joint Motion to Dismiss, Dkt. No. 187 at 11, Duffy v. Yardi Systems, Inc., No. 23-cv-1391 (W. D. Wash.) (hereafter Duffy v. Yardi Opinion) (citing Complaint, Dkt. No. 1).  Recently, the presiding judge in Duffy, Judge Robert Lasnik, dismissed charges in a lawsuit brought by hotel guests against CoStar Group and hotel company co-defendants alleging that industry benchmarking reports produced by a CoStar subsidiary Smith Travel Research (STR) helped arbitrarily increase prices for luxury hotel rooms.  See Order Granting Motion to Dismiss, Dkt. No. 117, Portillo et al. v. CoStar Group Inc. et al., No. 2:24-cv-00229 (W.D. Wash. ).  Judge Lasnik explained that, unlike in Duffy, the plaintiffs in Portillo did not sufficiently plead that defendants gave STR any information on the actual prices of individual hotel rooms. He also noted that, unlike the technology at issue in Duffy, STR's benchmarking reports are not an algorithmic pricing product.  Because the reports generated by STR “are likely one of many inputs into algorithms that ‘push higher rates' for luxury hotel rooms,” Judge Lasnik found that there was “too attenuated and speculative a connection between STR reports and final hotel room prices to justify this Court finding that defendants' alleged parallel conduct of contracting with STR is significant in a case that is allegedly about ‘price fixing in its modern form.'”  See id. at 13–14.

16 Duffy v. Yardi Opinion at 14 (citation omitted).

17 Memorandum Opinion and Order on Motions to Dismiss, Dkt. No. 428, In re MultiPlan Health Ins. Provider Litig., No. 24-cv-06795 (N.D. Ill.).

18 Id. at.

19 Khushita Vasant, “Algorithmic pricing probes to increase as use grows, U.S. DOJ's Slater says” MLex (Aug. 11, 2025, 5:28 PM) available here (on file with author).

20 Amended Complaint, Dkt. No. 47, United States et al. v. RealPage, Inc. et al., No. 1:24-cv-00710 (M.D.N.C.).

21 Id. ¶ 78.

22 Under the leadership of prior AAG Jonathan Kanter, DOJ took the position that it may be considered per se illegal price fixing when “competitors knowingly combine their sensitive, nonpublic pricing and supply information in an algorithm that they rely upon in making pricing decisions, with the knowledge and expectation that other competitors will do the same.” Statement of Interest of the United States, Dkt. No. 628 at 15, In Re: RealPage, Rental Software Antitrust Litig. (No. II), Case No. 3:23-MD-03071 (M.D. Tenn.).  A more recent Statement of Interest filed by DOJ under the leadership of AAG Slater, while asserting that competitors' joint use of a common pricing algorithm to set starting-point or maximum prices can be concerted action under Section 1, does not explicitly argue that the per se standard should apply.  See Statement of Interest of the United States, Dkt. No. 382, In re MultiPlan Health Ins. Provider Litig., Case No. 1:24-cv-06795 (N.D. Ill.).   

23 Khushita Vasant,  “U.S. DOJ's Slater signals tougher enforcement as algorithms spread” MLex (Sep. 19, 2025 10:58 GMT) available here (on file with author).

24 Department of Justice press release, “Justice Department Reaches Proposed Settlement with Greystar, the Largest U.S. Landlord, to End Its Participation in Algorithmic Pricing Scheme” (Aug. 8, 2025) available here (on file with author).

25 Proposed Final Judgment, Dkt. No. 152-1, United States of America v. Greystar Management Services, LLC, No. 24-cv-00710 (M.D.N.C.) available here.

26 Greystar is the second lessor defendant to settle with the government in the RealPage case.  On January 7, 2025, DOJ announced a proposed consent decree with Cortland Management LLC that included similar terms as the Greystar Final Judgment.  See Proposed Final Judgment, Dkt. No. 49-1, U.S. v. Cortland Management LLC, N. 1:24-cv-00710 (M.D.N.C.).

27 Real Page Newsroom, Real Page Reaches Revenue Management Software Settlement with Nevada Attorney General (Sept. 19, 2025) available here (on file with author).  RealPage has also agreed to: (1) contribute $200,000 to the State of Nevada for distribution to nonprofit or governmental organizations that provide down payment assistance or rent reduction to Nevada residents; (2) provide annual certifications of compliance to Nevada for five years; and (3) maintain an antitrust compliance program with training for revenue management personnel. Id.

28 SF.gov, “New law prohibits algorithmic devices used to set rents in San Francisco” (Oct. 16, 2024) available here.

29 The Berkeley, California City Council also passed a similar ordinance in March 2025.  However, the effective date has been postponed until March 1, 2026, pending the resolution of a lawsuit filed by RealPage in April 2025 seeking a temporary restraining order and motion for preliminary injunction to enjoin the ordinance on First Amendment grounds.  See Amanda McLeod and Sarah Hennessey,  “Citing litigation costs, City Council suspends ban on pricing algorithms,” The Daily Californian (July 1, 2025) available here (on file with author).

30 See, e.g., San Diego, CA (O-2025-107 REV.) and Philadelphia, PA (Bill No. 240823).

31 New Jersey City Ordinance 25-056.

32 O-2025-107 REV., An Ordinance Amending Chapter 9, Article 8 of the San Diego Municipal code by Adding New Division 11, Sections 98.1101, 98.1102, 98.1103, and 98.1104, relating to prohibiting anti-competitive automated rent price-fixing (May 22, 2025).

33 City of Minneapolis, Ordinance No. 2025-010 (March 27, 2025).

34 In his May 29, 2025 veto letter, Governor Polis stated that while he agrees that ”of course, collusion between landlords for purposes of artificially constraining rental supply and increasing costs on renters is wrong,” he has concerns about “inadvertently tak[ing] a tool off the table that could identify vacancies and provide consumers with meaningful data to help efficiently manage residential real estate to ensure people can access housing . . . this bill may have unintended consequences of creating a hostile environment for providers of rental housing and could result in further diminished supply of rental housing based on inadequate data.”  Governor Polis left open the possibility of supporting a similar bill in the future that “makes a distinction between collusive and non-collusive uses of nonpublic competitor data.” (on file with author). 

View more insights and analysis

Register now to receive personalized content and more!