# Realtor.com ZIP Market Stats (`alol/realtor-zip-statistics`) Actor

Get six Realtor.com ZIP market metrics without aggregating individual listings. Compare inventory and prices across ZIPs with explicit missing-data status and your own correlation IDs.

- **URL**: https://apify.com/alol/realtor-zip-statistics.md
- **Developed by:** [Al Ol](https://apify.com/alol) (community)
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.85 / 1,000 complete zip market statistics — usd 0.95 to usd 0.85 per 1,000s

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Realtor.com Housing Market Statistics by ZIP Code

**Get Realtor.com housing market data by ZIP code: inventory, median listing price, median rent, median sold price, price per square foot, and days on market.** Retrieve six source-provided metrics without exporting and aggregating individual listings. Compare up to 100 ZIPs; set `maxResults` to the number of ZIPs to process (default 1).

Successfully fetched target records are returned even if another target fails. The run still reports the upstream failure; completed requests are drained and returned in input order, with normal status and billing rules.

- **Use market-level context:** retrieve Realtor.com ZIP aggregates instead of calculating a market estimate from a capped listing export.
- **Recognize data gaps:** complete, unavailable, and not-found statuses plus `missing_fields` distinguish missing metrics from real zero values.
- **Join results to your workflow:** preserve five-digit ZIP codes, including leading zeros, and attach your own `externalId` and `correlationId`.

Retrieve six current Realtor.com housing-market aggregates for one to 100 five-digit US ZIP codes. The Actor preserves leading zeroes and emits exactly one normalized status row for every processed ZIP.

To collect individual listings together with ZIP market statistics, use [Realtor.com Listings by ZIP](https://apify.com/alol/realtor-search). To retrieve detailed records for specific properties, use [Realtor.com Property Details](https://apify.com/alol/realtor-property-details).

This is a strict ZIP-only product. Unsupported and unknown fields are rejected instead of being ignored.

### Input examples

```json
{
  "zipCodes": ["08109", "00501"],
  "maxResults": 2,
  "maxConcurrency": 5,
  "externalId": "zip-benchmark-42"
}
```

### Pricing

The effective result price depends on the customer's Apify account tier. Platform usage is included.

There is no fixed start charge. Only a published `complete` six-metric row is billed. `unavailable` and `notFound` rows are free.

The Actor reserves the possible complete-result price before requesting a ZIP, writes the result, then charges only complete rows. Free results release their reservation for later ZIPs. Max Cost in the platform run options and `maxTotalChargeUsd` both limit collection; the lower limit applies. When another ZIP cannot be funded, collection finishes and saved rows remain available. Unprocessed ZIPs do not produce rows.

#### `zip-statistics`

| Apify tier | Per result | Per 1,000 results |
| --- | ---: | ---: |
| FREE | `$0.00095` | `$0.95` |
| BRONZE | `$0.00095` | `$0.95` |
| SILVER | `$0.00090` | `$0.90` |
| GOLD | `$0.00085` | `$0.85` |

### FAQ and troubleshooting

#### Can I compare median home prices across ZIP codes?

Yes. Supply multiple ZIP codes and set `maxResults` to the number you want to process. Compare the available median listing and sold prices, median rent, price per square foot, inventory, and days on market. These are current source-provided observations; this Actor does not return a historical time series or a price forecast.

**Why are some values `null`?** Realtor.com did not provide those metrics for the ZIP at observation time. Check `status` and `missing_fields`; the Actor does not interpolate or substitute values.

**Why is a ZIP `notFound`?** The upstream response did not contain a ZIP geography. Confirm the five-digit string and remember that syntactically valid ZIPs do not guarantee source coverage.

**Does concurrency change row order?** No. Requests can run in parallel, but rows are normalized in input ZIP order.

**Does this Actor use a proxy or browser fallback?** Yes. Requests use a fixed operator-managed chain: primary residential proxy, premium residential proxy, then Bright Data Scraping Browser. Each proxy tier exhausts bounded fresh-session retries before fallback. The Actor fails closed if the chain is not configured and never uses Apify Residential or a direct connection. The endpoint is an internal GraphQL contract and can change without notice; deterministic contract errors fail immediately rather than wasting fallback requests.

### Related Actors

Explore our other real-estate Actors for property discovery, enrichment, market analysis, and monitoring:

- [Realtor.com Listings by ZIP](https://apify.com/alol/realtor-search) — Collect Realtor.com listing cards and separate market-statistics rows by ZIP code.
- [Realtor.com Property Details](https://apify.com/alol/realtor-property-details) — Enrich Realtor.com property IDs or detail URLs with detailed property records.
- [Zillow Search](https://apify.com/alol/zillow-search) — Collect listing cards by ZIP code, location, search URL, or map bounds.
- [Zillow Map Results](https://apify.com/alol/zillow-map-results) — Collect lightweight map cards with coordinates and Zillow property IDs.
- [Zillow Area Statistic](https://apify.com/alol/zillow-area-statistic) — Get ZIP-level statistics calculated from Zillow sale or rental listings.
- [Zillow Property Details](https://apify.com/alol/zillow-property-details) — Enrich Zillow property IDs or detail URLs with detailed property records.
- [Zillow Listing Monitor](https://apify.com/alol/zillow-listing-monitor) — Track new listings, price changes, status changes, and confirmed delistings across repeated scans.

### Responsible use and data availability

This independent Actor is not affiliated with or endorsed by Realtor.com. It does not grant rights to Realtor.com, broker, MLS, photographic, personal, or other third-party data.

Market aggregates are source-provided observations, not appraisals, guarantees, or complete market records. Availability and coverage can vary by ZIP and time. Customers are responsible for lawful use, compliance with applicable terms, copyright, database, privacy, fair-housing, marketing, and other rules, and for obtaining any required permissions.

# Actor input Schema

## `externalId` (type: `string`):

Optional caller-owned run ID copied to every Realtor.com output row.

## `correlationId` (type: `string`):

Optional trace or workflow ID copied to every Realtor.com output row.

## `zipCodes` (type: `array`):

One to 100 five-digit US ZIP codes. Leading zeroes are preserved.

## `maxResults` (type: `integer`):

Cap on ZIP statistics rows produced. Paid runs require at least one requested result.

## `maxTotalChargeUsd` (type: `number`):

Hard limit for Realtor.com pay-per-event charges in this run. Paid rows are not written after the limit is reached.

## `maxUpstreamAttempts` (type: `integer`):

Optional run-level ceiling for Realtor.com GraphQL request attempts. The deployment limit can only reduce this value.

## `maxUpstreamCostUsd` (type: `number`):

Optional best-effort ceiling for measured Realtor.com GraphQL request cost. The final request may cause a small overshoot.

## `maxConcurrency` (type: `integer`):

Upper bound for parallel ZIP work. Output remains in input ZIP order.

## Actor input object example

```json
{
  "zipCodes": [
    "10314"
  ],
  "maxResults": 1,
  "maxConcurrency": 10
}
```

# Actor output Schema

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

No description

# 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 = {
    "zipCodes": [
        "10314"
    ],
    "maxResults": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("alol/realtor-zip-statistics").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 = {
    "zipCodes": ["10314"],
    "maxResults": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("alol/realtor-zip-statistics").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 '{
  "zipCodes": [
    "10314"
  ],
  "maxResults": 1
}' |
apify call alol/realtor-zip-statistics --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alol/realtor-zip-statistics"
        }
    }
}
```

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/DR4uoDV0NZn2AtVw2/builds/6SxqWmvOyPgEWNJQ0/openapi.json