When you underwrite a multifamily deal today, the rent line increasingly comes from software. You feed in your units, a revenue-management engine reads "the market," and it hands you a number. It feels like reading a thermostat — neutral, mechanical, just the market talking.

The miss is that one of those engines wasn't only reading the market. According to the Department of Justice, it was helping landlords who are supposed to compete quietly line up their prices using each other's private data. This spring a court started dismantling it — and the rules just changed under every operator who prices with a tool.

The signal isn't in your rent comp. It's in where your pricing engine gets its inputs — and that just turned from a software feature into a legal question.

Algorithmic pricing was sold as efficiency. The antitrust case says some of it was coordination in a trench coat. Here's the mechanism, step by step.

Step 1 — The tool pooled private data. RealPage's pricing software recommended rents using nonpublic, competitively sensitive lease data drawn from other landlords — the kind of private information rivals could never legally hand each other across a table. The engine could, because it sat in the middle.

Step 2 — Shared inputs produce shared prices. When competing buildings feed their private numbers into one engine and follow its output, they stop competing and start moving together. That's coordination without a meeting. The algorithm was the back room.

Step 3 — The DOJ drew the line. RealPage settled with the Department of Justice and agreed to stop offering software that uses nonpublic, competitively sensitive data shared among landlords to recommend rents — no damages, no admission of wrongdoing, but the core practice is gone. The settlement isn't really about one vendor; it's a rule for the whole category: read public signals all you want, but you can't quietly pool competitors' private data and call it a recommendation.

Step 4 — The states went harder. A coalition of 10 state attorneys general brought a parallel case. Greystar, one of the largest landlords in the country, settled for $7 million. New York went furthest, passing one of the first laws in the nation against algorithmic price-fixing outright.

Step 5 — Now it's a constitutional fight. RealPage is suing New York, arguing the ban is "a sweeping and unconstitutional ban on lawful speech." Whether an algorithm's price output is protected math or illegal coordination is being decided in court right now — and the answer sets the rules for every pricing tool in the market.

The connection nobody is making: The legal exposure didn't attach to the vendor alone. It attaches to the operator who set rents off pooled competitor data. Your rent line may be carrying antitrust risk you never underwrote — and "the software did it" is not a defense.

The hidden variable: The risk in a rent-pricing tool was never the algorithm's math — it's the provenance of its inputs. A tool that reads public signals is an edge. A tool that quietly pools competitors' private data is a liability, and that liability now sits on the operator who priced with it, not just the vendor who sold it.

If you operate multifamily and price with a tool, the question flipped from "is it smart?" to "where does it get its data?" Ask your vendor in writing whether the recommendation engine uses nonpublic data from other owners or operators — and keep the answer.

If you underwrite or acquire, a target whose rent roll was built on pooled-data pricing carries both legal exposure and re-pricing risk. Diligence it. Don't inherit it blind in the cap rate.

If you're a lender or an LP, "the algorithm set it" has stopped being a shield. Coordinated-pricing exposure is a real line item in the deals you finance, and it can move post-close.

If you build proptech, the moat just shifted — from the most aggressive recommendation to the most defensible inputs. Provenance is the new product.

The people who get hurt are the operators who treated the rent line as neutral software output instead of a decision they own.

1. RealPage v. New York. The ruling decides whether an algorithmic price recommendation is protected speech or coordination — the precedent the whole category waits on. commondreams.org

2. Copycat state bills. When a second and third state pass NY-style bans, the question stops being local and every operator nationwide needs a defensible answer about pricing inputs.

3. Vendor repositioning. Watch for revenue-management tools publicly switching to "public-data-only" models to stay sellable — the market pricing in the new rule.

4. DOJ Antitrust Division filings. The scope of the consent terms defines what "allowed" looks like for everyone else. propublica.org

5. Your own vendor's data-source disclosure. The operator-level tell: if they can't say plainly that inputs are public or first-party, that's your risk surfacing.

Claim: Through 2027, additional states will pass or advance laws restricting algorithmic rent-pricing, and major revenue-management vendors will visibly reposition their products around public-data-only models to stay sellable.

Verification date: December 2027
Status: OPEN

The long call proves the thesis. This one proves we're live.

Near-term claim: By September 30, 2026, there will be material movement in RealPage v. New York and/or at least one additional state introducing or advancing algorithmic-rent-pricing legislation.

Stated confidence: 75%
Verification date: September 30, 2026
Status: OPEN

This analysis cross-referenced antitrust enforcement, state legislation, and multifamily pricing operations — a chain from a consent decree to your rent roll that no single market report assembles.

The pricing tool everyone trusted is being rebuilt in real time. The operators who understand why will be the ones who can still defend the number on the lease.

You know exactly who needs this — the one who prices a rent roll off a revenue-management tool and has never once asked where its numbers come from.

Send it to them before the next renewal cycle. It protects them from carrying antitrust exposure they never underwrote, and it makes you the person who saw the line move first — the one whose read they trust next time. One name, one forward, right now, while it's in front of you.

Cross-domain reads like this one — spanning antitrust, regulation, and real estate operations — are what I do for clients. Bring me your market or portfolio question at cokas.io: describe it, and get a written scope back within 48 hours. No sales call.

Submit a request at cokas.io

The Pattern Brief — See what others miss.
A publication of Cokas.io | thepatternbrief.com · © 2026

ClarityCore outputs are AI-assisted analysis. Professional review recommended before action. This newsletter provides analysis, not financial advice. Every prediction carries a verification date and is revisited in a future edition.