Recipe · Apify Store · runs in a terminal
Polanco vs. Condesa rents: what 200 Mexico City listings say about price per m²
Polanco had the higher median asking rent, but the lower median rent per square metre. Breaking the sample down by bedrooms changed the comparison again.
If your shortlist spans Polanco and Condesa, comparing asking rents tells you what you’d pay. Dividing by advertised floor area tells you what that money buys. In a sample of 200 Inmuebles24 listings, Polanco had a higher median asking rent (MXN 70,000 vs. 45,000) and a lower median rent per square metre (MXN 458 vs. 473). Among listings with two bedrooms, Polanco was more expensive per square metre.
What the search returned
I used automatic/inmuebles24-mx-scraper to search for apartment rentals in each neighborhood on November 18, 2026 UTC. I left the portal’s ordering in place and capped each search at 100 rows. The Condesa and Polanco searches both reached that cap. A third search using roma-norte finished with an unrecognized-location message and returned no rows. I left that search out of the price comparison.
I kept individual listings with a positive MXN asking rent and a positive source field for total area, totalAreaM2. I excluded seven USD listings and two developments with starting prices, all from Polanco, leaving 191 rows. The two result sets had no overlapping listing keys. Different ads can still describe the same apartment.
| Portal search | Returned | Used | Median asking rent (MXN/mo) | Median total area (m²) | Median rent (MXN/m²/mo) | Middle half (MXN/m²/mo) |
|---|---|---|---|---|---|---|
| Polanco | 100 | 91 | 70,000 | 144 | 458 | 377–582 |
| Condesa | 100 | 100 | 45,000 | 100 | 473 | 389–543 |
I calculated price per square metre for each listing, then took the median of those ratios. Dividing the median price by the median area would combine statistics that can come from different listings. The middle half runs from the first to the third quartile, with inclusive interpolation.
Compare by bedroom count
| Bedrooms | Polanco listings | Polanco median (MXN/m²/mo) | Condesa listings | Condesa median (MXN/m²/mo) |
|---|---|---|---|---|
| 1 | 19 | 593 | 26 | 545 |
| 2 | 31 | 488 | 54 | 442 |
| 3 | 36 | 371 | 17 | 400 |
Polanco had more three-bedroom listings in this sample. The median Polanco two-bedroom was also larger than the median Condesa two-bedroom (133 m² vs. 100 m²). If you’re shopping for two bedrooms, start with that row, then filter by your actual size range. The overall medians pool listings with different bedroom counts and sizes.
The top table includes every eligible listing. The bedroom table leaves out listings with an unknown bedroom count and counts outside the displayed groups. These are asking prices from the portal’s ranked results for one collection window. The comparison excludes maintenance fees and signed lease prices.
Reproduce the tables
Download the captured analysis fields as rentals.json. The snapshot preserves the returned order and includes only the fields used here. Save the code as compare.py and run python3 compare.py rentals.json.
import json
import sys
from pathlib import Path
from statistics import median, quantiles
runs = json.loads(Path(sys.argv[1]).read_text())["runs"]
def eligible(row):
return (
row["currency"] == "MXN"
and not row["isDevelopment"]
and not row["isStartingPrice"]
and (row["price"] or 0) > 0
and (row["totalAreaM2"] or 0) > 0
)
def per_m2(row):
return row["price"] / row["totalAreaM2"]
for run in runs:
raw = run["items"]
rows = [row for row in raw if eligible(row)]
if not rows:
continue
rates = [per_m2(row) for row in rows]
lower, _, upper = quantiles(rates, n=4, method="inclusive")
print(
run["input"]["location"], len(raw), len(rows),
f'{median(row["price"] for row in rows):,.0f}',
f'{median(row["totalAreaM2"] for row in rows):,.0f}',
f'{median(rates):,.0f}',
f'{lower:,.0f}–{upper:,.0f}',
)
for bedrooms in (1, 2, 3):
group = [row for row in rows if row["bedrooms"] == bedrooms]
if group:
print(
f" {bedrooms} bedrooms", len(group),
f'{median(row["totalAreaM2"] for row in group):,.0f}',
f'{median(map(per_m2, group)):,.0f}',
)
To pull a fresh sample, use the saved input objects in the snapshot as the request bodies for POST https://api.apify.com/v2/acts/automatic~inmuebles24-mx-scraper/runs?maxTotalChargeUsd=0.22&timeout=150 with an Apify bearer token. Wait for the run to finish, read defaultDatasetId from the run record, then fetch GET https://api.apify.com/v2/datasets/{datasetId}/items?format=json. Substitute those rows for items in the snapshot. A fresh run uses the portal results available at collection time.
The run records list customer prices of $0.015 per start at the tested memory setting and $0.0015 per billed listing, read on November 18, 2026 UTC. The publisher account incurred about $0.0199 in platform usage across the three attempts, including the empty search.
Apify run IDs
| Search | Run ID | Dataset ID | Result |
|---|---|---|---|
| Polanco | 1CzUe5PdPjy1dGdZM |
xKIJfQc3hMhxamIv3 |
100 rows |
| Condesa | 6OYC8hsfDb03VXK9E |
tup7xnU1yVQqfQTcW |
100 rows |
| Roma Norte | ciUEU0tehEOzIsI3J |
eIX87Ncl62PrZ5DNO |
Empty, location unrecognized |
Affiliate disclosure: The Apify Store link carries our referral code. If you sign up for a paid plan through it, ssh.autos may earn a commission at no cost to you.
Sources in this recipe
-
Inmuebles24: Mexico Casas y Departamentos
Inmuebles24 scraper for Mexico real estate: casas y departamentos en venta y renta with MXN/USD prices, m2, recamaras, banos, parking, coordinates, building age and agency.
Machine-readable: openapi.json · llms.txt