Historical Rental Listing Data: Why There's No Archive for Your Address
The oddly specific problem
A landlord wants to know what the unit down the block listed for in June 2022, and there is nowhere on earth to look it up.
A landlord in Boston owns a handful of units near the universities. What he wants is historical rental listing data by address, what did this unit, or the three-bed down the block, actually list for in June 2022?, and there is nowhere to get it. About nine out of ten leases in that market run September 1 to August 31, which means the entire pricing conversation happens in a window roughly the size of a summer internship: mid-May to mid-July, with a smaller flurry in January and February.
During that window, he reviews somewhere between 50 and 100 listings to find maybe ten that are genuinely comparable, same neighborhood, same bedroom count, same era of kitchen. Then the window closes, the listings vanish from the portals, and the data goes with them. Next spring, he starts over.
His options, as he describes them, are: screenshot everything during peak season and paste it into a spreadsheet, call around to see what local property managers are charging, get MLS access if he can, or manually track 25-30 comparable addresses quarterly to build his own private dataset. If he misses the window entirely, the fallback is to list high and walk the price down, which is a polite way of saying "pay for the mistake in vacancy days."
He also notes, correctly, that the commercial real estate data tools are "awesome for properties of 125+ units, not the small stuff."
He is not wrong about any of this. He is also, we think, describing a problem that cannot currently be solved by a product.
Wait, is this actually a problem?
The pain is real. The market size is murkier than it looks.
The structural argument is genuinely compelling on paper. Roughly 46% of the ~49.5 million U.S. rental units sit in 1-4 unit buildings, and only about 22% of small rental properties are professionally managed, versus 84% of properties with 150+ units (HUD/Census Rental Housing Finance Survey). That's a very large population of self-managing owners with no institutional data access.
9.7 million tax-paying landlords, the overwhelming majority owning 1-4 units, and 78% of owners planning rent increases in 2025.
There's also a legal angle. NYC's rent overcharge rules require courts to consider "all available rent history which is reasonably necessary" (NYC Admin Code §26-516(h)), which creates genuine demand for documented address-level rent history. That citation comes from a firm that litigates those cases, covers one city, and describes a one-time need rather than a subscription.
So: real friction, plausibly large population, weak evidence that anyone reaches for a credit card.
Who's already solving this (and what it costs)
Pricing as of research; the enterprise tiers are negotiated and don't publish rates.
Rentometer
$5/mo Basic (5 reports) · $8/mo Essential (100) · $16/mo Pro (500 + API) (as of research)
Nationwide rent estimates by address, radius comps, branded PDF reports, bulk processor, market insights.
The catch: "Today vs. one year ago." No point-in-time archive, no address-level listing history. Thin in rural/secondary markets.
RentCast
Free (5 comps) · $12/mo Pro billed annually (20 comps, 50+ properties) · API priced separately (as of research)
Rent estimates, up to 20 nearby comps, ZIP-level rent trends, portfolio dashboard, rent alerts, Zapier, REST API over 150M+ records.
The catch: ZIP-level trend lines only. No individual past listings, no legal-grade proof of a specific listing on a specific date.
RealPage Market Analytics
Enterprise only; est. $10,000-$30,000+/yr (as of research)
30+ years of proprietary multifamily history, daily rents/concessions/occupancy, 5-year forecasts, 425+ markets.
The catch: Not sold to you. No public API, no self-serve, no path under ~50 units. Also under DOJ antitrust scrutiny over algorithmic rent-setting.
Yardi Matrix
Est. $15,000-$25,000/yr, negotiated (as of research)
Property-level data on 50+ unit properties in major metros, effective rents, concessions, rent and sale history, forecasts.
The catch: 50+ units, major metros, by design. Nothing for 1-4 unit properties. Enterprise contracts only.
If you have this problem right now
RentCast's free tier is the correct first stop, five comps costs nothing, and its ZIP-level trend lines are the closest commercially available thing to "how has this submarket moved." Upgrade to Rentometer Essential at $8/mo if you need volume and branded reports for a lender or partner. Neither will retrieve the listing at 42 Comm Ave from June 2022. For that, your best available tool remains the unglamorous one: screenshot during your peak window, log it, and start building the private dataset now. It's dumb. It also works, and it's what the landlord in that thread ended up doing.
So why isn't this a slam dunk?
Because the gap in that table isn't an opportunity. It's a wall, and two companies already walked into it.
Rentometer has been running since 2012. Thirteen years, 500,000+ real estate professionals, 10 million+ rental records processed annually. They serve exactly this buyer. They have every commercial incentive to sell historical archives. They offer "this year vs. last year."
RentCast is the modern challenger, clean API, generous free tier, explicit historical tracking as a feature, developer-friendly by design. They stopped at ZIP-level aggregates.
Two well-resourced, motivated incumbents, working independently, arrived at the same ceiling. The tempting read is "they both missed it."
That's the second problem. Every path to the underlying data fails on inspection. Licensed feeds from ATTOM or RentCast have limited address-level historical depth, and commercial resale is a separately negotiated tier at an unquoted price. Scraping Zillow and Apartments.com violates ToS and invites a legal department. The Wayback Machine is unreliable, incomplete and unstructured. User submissions have a cold-start problem. Which leaves "start ingesting today and have an archive in 12-24 months", meaning you launch with zero historical data, which is the entire product, and you're pre-selling a dataset to people who need it this June.
And the moat, if you built it, is time-in-market. Any incumbent can start the same ingestion pipeline the morning you launch, with thirteen years of brand equity and 500,000 existing users to sell it to.
Then the buyer. The use case is a genuine 8-week seasonal event. At $9-$19/month with people cancelling once their units are leased, lifetime value lands somewhere around $18-$57. Customer acquisition for a diffuse, price-sensitive, notoriously frugal B2C segment, in search results dominated by Zillow, Apartments.com, Rentometer and RentCast, will not come in under that. The legal use case is one-time revenue at best, and third-party API data likely can't establish the chain-of-custody provenance a court would want anyway.
The product's central promise depends on data that was never stored.
Our verdict: kill it, 3/10. Not because the landlord's problem isn't real. Because the product's central promise depends on data that was never stored, the economics need a licensing contract nobody has been quoted, and the buyer churns before you recover acquisition cost.
What we're watching
Three things would move this off the kill list:
- A licensed feed with genuine address-level history, 3+ years deep, at flat-rate resale pricing. This is the gating condition, not a later negotiation. If you want to test this thesis, don't build anything, call ATTOM, RentCast and two others and ask for commercial resale terms on historical listing data. If the data exists at a workable price, everything changes. If it doesn't, the conversation is over in a week instead of eighteen months.
- Annual-only pricing validated by real landlords in one dense, seasonal market. Twenty paid annual subscriptions in Boston or NYC would neutralize the churn objection. Monthly billing against an 8-week use case never will.
- Practicing attorneys confirming they'd rely on the output as evidence. Until then, the legal angle is marketing copy.
Also worth watching: any regulatory push toward mandated rent registries. A public, structured, address-level rent history dataset would turn this from a data-acquisition problem into a UI problem, which is a business someone could actually build.
Having this (or a related) problem?
If one of these is yours and you've got a sharper angle on it (and a budget to match), we'd like to hear it. Tell us what you're actually trying to solve, and we'll tell you straight whether it's worth building together.
Write us a message →