# Redfin Sold Comps (`apt_marble/redfin-sold-comps`) Actor

Get recently sold comparable homes for any property: sold prices, sold dates, sizes, beds, baths and addresses.

- **URL**: https://apify.com/apt\_marble/redfin-sold-comps.md
- **Developed by:** [Hamza](https://apify.com/apt_marble) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 sold-comp records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Redfin Sold Comps

Paste a home link and get back its recently sold comparables: real sold prices, sold dates, sizes, beds, baths and addresses. Built for anyone who prices homes with data: agents building a CMA, appraisers pulling comps, investors checking what a neighborhood actually pays, and analysts tracking sold trends.

### What you can do with it

- **Price a home with real sales** — paste a home link and get the nearby homes that actually sold, with prices and dates.
- **Build a CMA packet** — export beds, baths, square feet, $/sq ft and days on market for every comp.
- **Check a neighborhood's range** — the run summary reports the low, high and average $/sq ft across each home's comp set.
- **Cover a whole pipeline** — run hundreds of home links through one run and collect every comp set into a single dataset.
- **Re-run on a schedule** — fresh sales appear constantly, so schedule weekly runs and diff each dataset against the last.

### What you get

One row per sold comparable. Abridged sample of a single record:

```json
{
  "subjectPropertyId": 32987967,
  "subjectUrl": "https://www.redfin.com/TX/Austin/15708-Fisher-Island-Dr-78717/home/32987967",
  "propertyId": 32987953,
  "listingId": 213005773,
  "url": "https://www.redfin.com/TX/Austin/15805-Pumpkin-Ridge-Dr-78717/home/32987953",
  "address": "15805 Pumpkin Ridge Dr",
  "unit": null,
  "city": "Austin",
  "state": "TX",
  "zip": "78717",
  "soldPrice": 550000,
  "soldDate": "2026-04-28",
  "pricePerSqFt": 259,
  "beds": 3,
  "baths": 2,
  "sqFt": 2127,
  "stories": 2,
  "daysOnMarket": 89,
  "mlsId": "9902347"
}
```

### Input reference

| Setting | Type | Default | What it does |
| --- | --- | --- | --- |
| Property URLs | list of text | — | Home links to find sold comparables for, e.g. `https://www.redfin.com/TX/Austin/15708-Fisher-Island-Dr-78717/home/32987967`. One set of comps is collected per link. **Required.** |
| Listing IDs | list of text | — | Optional. Listing identifiers aligned by position with the links above — entry 1 belongs to link 1. The link alone is usually enough. |
| Max comps per property | whole number | `25` | Maximum sold comparables kept for each home link (1–100). |
| Max items | whole number | `2000` | Maximum comp rows to collect in total, up to 20,000. The actor works through your links until this number is reached or the links run out. |

### Output fields

| Field | Type | Description |
| --- | --- | --- |
| `subjectPropertyId` | number | The property you asked about. |
| `subjectUrl` | text | The home link you supplied. |
| `propertyId` | number | Stable key of the sold comparable. |
| `listingId` | number | Listing key of the sold comparable. |
| `url` | text | Full link to the comparable's home page. |
| `address` | text | Street address. |
| `unit` | text | Unit designator when shown. |
| `city` | text | City. |
| `state` | text | State code. |
| `zip` | text | ZIP code. |
| `soldPrice` | number | Actual sold price in USD. |
| `soldDate` | text | Actual sold date (`YYYY-MM-DD`). |
| `pricePerSqFt` | number | Dollars per square foot when shown. |
| `beds` | number | Bedroom count. |
| `baths` | number | Bathroom count. |
| `sqFt` | number | Interior square feet when shown. |
| `stories` | number | Story count when shown. |
| `daysOnMarket` | number | Days on market when shown. |
| `mlsId` | text | MLS number. |

### Pricing

You pay per sold-comp record, with no monthly minimum.

| What you are charged for | Price |
| --- | --- |
| Sold-comp record — one record added to your dataset | **$1.50 per 1,000** |

### Limits & what this actor cannot do

- Comparables come from the site's own similar-sold set for each home — you cannot pick the radius or the lookback window.
- Rows are a snapshot at the moment of collection; new sales appear constantly, so re-run for freshness.
- Fields a comparable does not show come back empty rather than guessed.
- Non-home links (search pages, city pages, other sites) are skipped, not charged.
- Speed depends on the size of the job and on the listing site's own response times; no fixed throughput is promised.
- The source site's terms govern automated access. You are responsible for using the data lawfully and in line with the source site's terms, and for handling any personal data in line with applicable privacy law.

### FAQ

**Do I need an account on the listing site?**
No. The actor reads only what the site shows publicly, and there is nothing to connect — paste home links and press start.

**What counts as a home link?**
A link containing `/home/` followed by a property number, such as `https://www.redfin.com/TX/Austin/15708-Fisher-Island-Dr-78717/home/32987967`. Anything else is skipped.

**How many comps come back per home?**
Up to the per-property limit you set (default 25), depending on how many the site lists for that home.

**What is in the run summary?**
Per-home counts plus the low, high and average $/sq ft the site reports for each comp set.

**Can I schedule it?**
Yes. Schedule it hourly, daily or weekly from the Apify console, and each run writes a fresh dataset you can compare against the last.

**Is the data complete?**
It is complete for everything the site shows openly in each home's sold-comparables set. Where a comp omits a field, the actor leaves it empty rather than guessing.

# Actor input Schema

## `propertyUrls` (type: `array`):

Home links to find sold comparables for, e.g. "https://www.redfin.com/TX/Austin/15708-Fisher-Island-Dr-78717/home/32987967". One set of comps is collected per link.

## `listingIds` (type: `array`):

Optional. Listing identifiers aligned by position with the links above — entry 1 belongs to link 1. The link alone is usually enough.

## `maxCompsPerProperty` (type: `integer`):

Maximum sold comparables kept for each home link.

## `maxItems` (type: `integer`):

Maximum comp rows to collect in total. The actor works through your links until this number is reached or the links run out.

## Actor input object example

```json
{
  "propertyUrls": [
    "https://www.redfin.com/TX/Austin/1115-W-10th-St-78703/unit-209/home/32315213"
  ],
  "listingIds": [],
  "maxCompsPerProperty": 25,
  "maxItems": 2000
}
```

# Actor output Schema

## `results` (type: `string`):

Every row this run produced.

## `runSummary` (type: `string`):

What this run collected, and anything it could not read.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "propertyUrls": [
        "https://www.redfin.com/TX/Austin/1115-W-10th-St-78703/unit-209/home/32315213"
    ],
    "listingIds": [],
    "maxCompsPerProperty": 25,
    "maxItems": 2000
};

// Run the Actor and wait for it to finish
const run = await client.actor("apt_marble/redfin-sold-comps").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "propertyUrls": ["https://www.redfin.com/TX/Austin/1115-W-10th-St-78703/unit-209/home/32315213"],
    "listingIds": [],
    "maxCompsPerProperty": 25,
    "maxItems": 2000,
}

# Run the Actor and wait for it to finish
run = client.actor("apt_marble/redfin-sold-comps").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "propertyUrls": [
    "https://www.redfin.com/TX/Austin/1115-W-10th-St-78703/unit-209/home/32315213"
  ],
  "listingIds": [],
  "maxCompsPerProperty": 25,
  "maxItems": 2000
}' |
apify call apt_marble/redfin-sold-comps --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apt_marble/redfin-sold-comps"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vat5Gs9rt9AbS3nHV/builds/iYiUn4zQ6JIz0Ujcf/openapi.json