🏡 Realtor.com Scraper: Property & Agent Data

Part of the Real Estate MCP. This actor's data is also available to AI agents through our Real Estate MCP server — eight listing, sales and rental-market tools behind one endpoint. No result, no charge.

⚡ Part of a 69-scraper suite trusted by 450+ developers across 8,000+ runs · >99% run success · no login, no cookies, no ban risk.

💸 You're only charged for delivered results. Empty searches, failed pages and duplicate listings are never billed.

Overview

Realtor.com Scraper extracts real estate listings from Realtor.com by city or ZIP code. For every for-sale and recently-sold property you get price, beds, baths, square footage, price per sqft, listing agent, brokerage office, county, coordinates, and the listing URL. No login and no API key.

Built lean and HTTP-only, it runs on Apify residential proxies and bills pay-per-result. Every record carries the listing agent and office, making this ideal for real-estate lead lists.

✅ No login required | ✅ No API key | ✅ Pay only for results | ✅ MCP-ready for AI agents

Reliability: blocked, empty, or failed pages are never charged. You only pay for property records actually delivered to your dataset.

Features

Full location coverage. Search by city, state or ZIP with no per-metro caps. Agent and office data. Every listing includes listing agent and brokerage name. For-sale and sold modes. Flip soldMode to pull recently-sold comps with sold price and date. Rich property fields. Price, beds, baths, sqft, HOA, year built, coordinates, and photo URL. Residential proxies. No datacenter-IP blocks, no unblocker subscription.

How it works

Realtor.com has no public listings API for developers. Its data partnerships are gated, expensive, and coverage-limited. This actor talks directly to Realtor.com's own search backend over plain HTTP, so you are not capped by the row limits, rate limits, or licensing restrictions of a third-party feed.

You choose the location, the filters, and the volume. The actor pages through results, extracts each listing into a flat JSON record, and pushes to the dataset. Field availability depends on what Realtor.com publishes for each listing; lastSoldPrice and lastSoldDate populate in recently-sold mode.

🧾 Input configuration

{
  "location": "Austin, TX",
  "maxItems": 100,
  "soldMode": false,
  "minPrice": 400000,
  "minBeds": 3,
  "proxyConfig": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

To scrape recently-sold homes with sold price and date, set "soldMode": true.

📤 Output format

Real record captured from a live run against "Austin, TX":

{
  "propertyId": "7211899596",
  "listingId": "2997168140",
  "status": "for_sale",
  "address": "4719 Castleman Dr",
  "city": "Austin",
  "state": "TX",
  "zip": "78725",
  "county": "Travis",
  "price": 185000,
  "lastSoldDate": "2024-01-24",
  "beds": 3,
  "baths": 2,
  "sqft": 1405,
  "lotSqft": 5227,
  "yearBuilt": 1996,
  "propertyType": "single_family",
  "pricePerSqft": 132,
  "hoaFee": 31,
  "listDate": "2026-06-12T00:36:33.000000Z",
  "latitude": 30.246305,
  "longitude": -97.583195,
  "photoCount": 1,
  "photoUrl": "http://ap.rdcpix.com/7ed047f0f69ede3a6499c5571a4a6548l-m1699133238s.jpg",
  "officeName": "Keller Williams Realty",
  "url": "https://www.realtor.com/realestateandhomes-detail/4719-Castleman-Dr_Austin_TX_78725_M72118-99596",
  "scraped_at": "2026-07-15T01:15:23.964Z"
}

Field availability depends on what Realtor.com publishes for each listing; null fields (like lastSoldPrice or agentName when Realtor.com does not expose them for a given record) are omitted rather than sent as null.

Every property record carries these fields:

Field	Description
🏠 address / city / state / zip / county	Full location fields
💰 price	List price
🛏️ beds / 🛁 baths	Bedroom and bathroom counts
📏 sqft / 🌳 lotSqft	Interior and lot square footage
📐 pricePerSqft	Price per square foot
🏗️ yearBuilt	Year built
🏡 propertyType	Property type (e.g. single_family, condo)
🔖 status	Listing status
💵 hoaFee	Monthly HOA fee
📅 listDate	List date
🏷️ lastSoldPrice / 🗓️ lastSoldDate	Populated in sold mode
📍 latitude / longitude	Coordinates
📷 photoUrl	Primary photo URL
👤 agentName	Listing agent name
🏢 officeName	Brokerage office name
🔗 url	Realtor.com listing URL
🆔 propertyId / listingId	Property and listing identifiers

💼 Common use cases

Real-estate lead generation Extract agent and brokerage names for outreach and CRM enrichment. Build geo-targeted lists of listing agents by ZIP or metro.

Comparable sales and CMA Pull sold inventory in a ZIP to value a subject property. Combine for-sale and sold data for accurate market snapshots.

Investor deal sourcing Filter by price band and beds to surface candidates across a metro. Re-run on a schedule to catch new inventory the day it lists.

Price and inventory monitoring Track new listings, status changes, and price cuts over time. Feed dashboards with live listing counts and median prices by ZIP.

🚀 Getting started

1. Create a free Apify account and open the actor.
2. Enter a location (e.g. Austin, TX or 78704).
3. Optionally set maxItems, soldMode, minPrice, maxPrice, or minBeds.
4. Click Start and let the actor page through results.
5. Download your data as JSON, CSV, or Excel, or pull it via API or MCP.

FAQ

Do I need a Realtor.com account or API key? No. The scraper requires no login, no cookies, and no API key. You only need an Apify account to run it.

Can I scrape recently-sold homes? Yes. Set soldMode to true and the actor returns recently-sold homes with their last sold price and date instead of active for-sale listings.

How much does the Realtor.com Scraper cost? Pay per result at $2 per 1,000 results ($0.002 per property). There is no free tier. You only pay for properties actually returned.

How do I target a specific area? Pass a ZIP code (78704) to narrow to one area, or a city with state (Austin, TX) for metro-wide results.

Is scraping Realtor.com legal? Scraping publicly available listing data is generally permissible, but results may include personal data (e.g. agent names) protected under laws like GDPR. Ensure you have a legitimate purpose and comply with applicable regulations.

Can I use it inside an AI agent? Yes. It is exposed as an MCP tool. See below.

Use in Claude, ChatGPT & any MCP agent

https://mcp.apify.com/?tools=themineworks/realtor-scraper

Or call it programmatically with the Apify client:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });

const run = await client.actor('themineworks/realtor-scraper').call({
  location: 'Austin, TX',
  maxItems: 100,
  minBeds: 3,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

🛠️ Related real estate actors

Chain Realtor with the rest of the wedge:

• Redfin Scraper: Redfin for-sale and sold listings by location.
• Zillow Search Scraper: Zillow for-sale listings by location.
• Zillow Property Details: full Zillow detail pages by URL or ZPID.
• Zillow Recently Sold: Zillow sold comps for CMA.
• Zillow Rental Listings: Zillow for-rent listings.
• 99acres Scraper: India rent, buy, PG, and commercial listings.

Typical flow: realtor-scraper and zillow-search-scraper cover for-sale supply, zillow-recently-sold and Realtor sold mode drive comps, zillow-property-details fills in full detail pages.

Found a bug or have a feature request? Open an issue on the actor's Apify Console page or reach out through the Apify profile.