Comparing apartment prices across comunas in Santiago is slower than it should be. Portal Inmobiliario and TocToc have no public listings API, rents are posted in CLP, sales are posted in UF (Chile's inflation-indexed unit), and new developments advertise a "Desde" (from) price that will skew any average if you leave it in the mix.

I built Chile Real Estate Scraper to get those listings into one spreadsheet. I'm René (Apify username ener90), and this is my own Actor, so you know the bias up front. The walkthrough below uses a real run from 26 October 2026 (America/Santiago), not a made-up sample.

1. What the Actor does

It crawls public search results (and, if you want, individual listing pages) from Portal Inmobiliario and TocToc, then writes one row per listing. Every row already has:

  • priceUF and priceCLP, converted with the official UF of the run date
  • pricePerM2UF and pricePerM2CLP when the listing has a single usable area (not a range)
  • comuna, bedrooms, bathrooms, m2Util, m2Total, coordinates, publisher, and photos
  • isNewProject plus pricePrefix: "Desde" so you can drop new developments from a median

The code is TypeScript on Crawlee, and it runs on Apify. A free Apify account is enough to try it: you pay per listing saved, and maxItems caps how many you get (and spend).

2. Configure the search

Open the Actor and paste this into Input (this is the exact input of the run I'll analyze below):

{ "comunas": ["Ñuñoa", "Providencia"], "region": "metropolitana", "operation": "arriendo", "propertyType": "departamento", "sources": ["portalinmobiliario", "toctoc"], "includeNewProjects": false, "maxItemsPerComuna": 40, "maxItems": 80, "includeDetails": true } 

The fields that actually exist today:

  • comunas (required). Accents are optional. region defaults to metropolitana and also accepts the other Chilean regions in the input schema.
  • operation: venta or arriendo (the default is venta).
  • propertyType: departamento, casa, oficina, terreno, local-comercial, bodega, estacionamiento, or parcela. TocToc only supports the first four.
  • sources: portalinmobiliario and/or toctoc. The default is Portal Inmobiliario only; set both if you want both.
  • minPrice / maxPrice with priceCurrency (UF or CLP). If you omit the currency, the Actor uses UF for sales and CLP for rent.
  • includeNewProjects: false drops the "Desde" development prices. The default is true, so turn it off when you want a clean median.
  • maxItemsPerComuna spreads the cap evenly across comunas. maxItems is the cap for the whole run.
  • includeDetails: true is Portal Inmobiliario only. It opens each listing page and adds total m², parking, coordinates, publish date, publisher, and photos. Turn it off if you only need a fast price pass.
  • Proxy defaults to a Chilean residential proxy. The portals block datacenter IPs, so leave that on.

3. Run and export

Click Start. When it finishes, open Storage → Dataset and download Excel, CSV, or JSON. You can also send the dataset to Google Sheets from Apify's integrations.

4. Analyze the rows

Each row includes priceUF, priceCLP, pricePerM2UF, pricePerM2CLP, and comuna. In Excel, a pivot table of the median price per m² by comuna is already a benchmark.

On 26 October 2026 (America/Santiago) I ran the input above. The Actor finished in 1 minute 40 seconds and returned 80 unique rental apartments, with new developments excluded. All 80 rows came from Portal Inmobiliario — TocToc contributed none in this run. Cost at the current price of US$0.003 per listing: US$0.24.

Comuna Listings Median rent Median CLP/m² Median 2-bedroom rent
Ñuñoa 40 CLP 575,000 CLP 13,415 CLP 655,000 (16 listings)
Providencia 40 CLP 1,040,264 CLP 15,137 CLP 1,243,316 (14 listings)

The range was CLP 360,000–1,607,622 in Ñuñoa and CLP 420,000–1,978,612 in Providencia. Per square meter, Providencia was about 13% more expensive (CLP 15,137 vs CLP 13,415). The median total rent was almost double, because the Providencia apartments in this sample were larger (median 75 m² vs 40 m² in Ñuñoa). That is why price per m² is the figure worth comparing, not the headline rent.

This is a snapshot of 80 listings from one morning, not a market report for the whole comuna.

5. Automate it

In Schedules, create a daily or weekly run with a fixed maxItems cap. Point the dataset at Google Sheets or a webhook and you have a simple market monitor.

Once you have sale and rental samples for the same comuna, a rough cap rate is (monthly rent × 12) / sale price, using pricePerM2CLP (or UF) on both sides so the units match. Other useful cuts: publishers (publisher, publisherType) for a list of active brokers in a zone, or a filter on new rows below a UF/m² threshold.

6. Cost and limits

Pricing on the Store today is US$3 per 1,000 listings (US$0.003 each). 50 listings would be about US$0.15; this 80-listing run was US$0.24. maxItems is the spend ceiling.

A few things the Actor will not do for you:

  • Results are deduplicated per portal, not across portals. If the same property is on both sites, it appears twice.
  • Price per m² is left empty on new projects that publish a range of floor areas, because a single ratio would be misleading.
  • TocToc does not cover local-comercial, bodega, estacionamiento, or parcela.
  • The two portals can return very different volumes for the same search. Always check the source column before you treat a file as a merged market sample.

If you try it, I'd like to know which fields are missing for the way you actually compare comunas.

Actor: apify.com/ener90/chile-real-estate-scraper