# Crexi Scraper - Commercial Real Estate, Prices & Broker Leads (`scrapesage/crexi-scraper`) Actor

Scrape Crexi commercial real estate — for-sale & auction CRE listings with asking prices, price/SqFt, cap rate, financials, photos & geo, plus deduped broker leads (brokerage, license, phone). Keyless, no browser. Filter by location, type & price; monitor new listings & price drops.

- **URL**: https://apify.com/scrapesage/crexi-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Real estate, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 listings

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Crexi Scraper — Commercial Real Estate, Prices & Broker Leads

Extract **complete commercial real estate data from Crexi** — for-sale and auction CRE listings with **real asking prices, price per SqFt, cap rate and the full financial & physical profile of every property**, high-resolution photos, geo-coordinates, and the data other scrapers leave empty. Optionally turn every listing broker into a **ready-to-contact CRE lead** with brokerage, license, direct phone, profile and a 0–100 lead score.

No login, no API key, no browser — fast JSON extraction straight from Crexi's own marketplace API, with 99%+ reliability.

### Why this Crexi scraper?

The portfolio's first **commercial** real estate actor. Most real estate scrapers cover homes and apartments and ignore CRE — and the few that touch Crexi only read the listing cards. This actor pulls Crexi's internal asset, gallery and broker endpoints and ships the **richest dataset in the category**:

| Data | Typical scrapers | This actor |
|---|---|---|
| Asking price + price/SqFt | partial | ✅ real values |
| Property type & subtype (Office, Retail, Industrial, Multifamily, Land…) | partial | ✅ |
| Building size, lot size, stories, year built, zoning, APN | ❌ | ✅ |
| Cap rate / NOI / tenancy / occupancy / # units | ❌ | ✅ when published |
| Full marketing description | ❌ | ✅ |
| High-resolution photo gallery | partial | ✅ opt-in |
| Geo (lat/lng, county, ZIP, full address) | partial | ✅ |
| Sale condition + on-market / auction / sold status | ❌ | ✅ |
| Listing **broker leads** (name, brokerage, license, phone) | ❌ | ✅ opt-in |
| Lead score (0–100) per broker | ❌ | ✅ |
| New-listing / price-drop monitoring | ❌ | ✅ built-in |

### Use cases

- **CRE deal sourcing** — pull every Office, Retail, Industrial, Multifamily, Land, Self-Storage or Hospitality listing for a state, market, price band or keyword and feed your acquisition pipeline.
- **Broker & sponsor lead generation** — listing brokers are active B2B buyers and partners. Score them by active-listing count and platinum status, and reach them by direct brokerage phone (`brokeragePhone`) and Crexi profile.
- **Pricing & market intelligence** — track asking price, price/SqFt and cap-rate trends by property type and geography; spot price drops and newly listed assets first.
- **Comps & underwriting** — capture building/lot size, year built, tenancy, occupancy and NOI to build comp sets and pre-screen deals.
- **Investor & lender prospecting** — find owners and assets by market and asset class, with the broker as the warm point of contact.
- **Auction watch** — monitor on-market and auction inventory and re-pull only what changed.

### How to use

1. [Sign up for Apify](https://console.apify.com/sign-up) — the free plan is enough to try this actor.
2. Open the **Crexi Scraper**, choose a mode, enter a location / property type / price filter (or paste Crexi listing URLs), and click **Start**.
3. Watch results stream into the dataset table.
4. **Export** as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the [Apify API](https://docs.apify.com/api/v2).

### Input

```json
{
    "outputType": "search",
    "searchText": "medical office",
    "states": ["TX", "FL"],
    "propertyTypes": ["Office", "Retail"],
    "askingPriceMin": 500000,
    "askingPriceMax": 10000000,
    "includePropertyDetails": true,
    "includeBrokerLeads": true,
    "maxResults": 200
}
```

- **outputType** — `search` (CRE listings, the headline mode), `propertyDetail` (full records by ID/URL), or `brokerLeads` (deduped broker contacts only).
- **searchText** — free-text keyword/area (property name, description, ZIP, "gas station", "Austin"…). Loose match — pair it with the precise filters below.
- **states** — US state codes (`TX`, `CA`) or names (`Texas`); the exact location filter.
- **propertyTypes** — `Multifamily`, `Office`, `Retail`, `Industrial`, `Hospitality`, `Land`, `Special Purpose`, `Mixed Use`, `Self Storage`, `Mobile Home Park`, `Senior Living`, `Note/Loan`, `Business For Sale`.
- **askingPriceMin / askingPriceMax / includeUnpriced** — price filters.
- **assetIds / startUrls** — numeric Crexi IDs or `/properties/<id>/<slug>` URLs (for `propertyDetail` / `brokerLeads`, or to add specific listings to any run).
- **includePropertyDetails** *(default true)* — fetch each listing's full record (marketing description, cap rate / NOI / tenancy / year built / zoning…) and photo gallery.
- **includeBrokerLeads** *(default false)* — also output one deduped broker lead per listing broker.
- **maxPhotos** *(default 25)* — cap gallery image URLs per property.
- **maxResults** — overall cap on records for the run.
- **monitorMode / monitorKey** — only output new or changed listings across scheduled runs (see below).

### Output

One record per listing (`type: "listing"` or, with details on, `type: "propertyDetail"`), plus optional broker leads (`type: "brokerLead"`):

```json
{
    "type": "propertyDetail",
    "assetId": 2591585,
    "name": "240 E Fresno St",
    "url": "https://www.crexi.com/properties/2591585/california-240-e-fresno-st",
    "propertyTypes": ["Office", "Mixed Use", "Special Purpose"],
    "propertyTypeLabel": "Office, Mixed Use, Special Purpose",
    "subtypes": ["Traditional Office", "School", "Religious/Church"],
    "status": "Active",
    "saleCondition": "For sale by owner",
    "askingPrice": 850000,
    "askingPriceText": "$850,000",
    "currency": "USD",
    "squareFootage": 12000,
    "pricePerSqFt": 70.83,
    "pricePerSqFtText": "$70.83",
    "lotSizeSqFt": 14261,
    "stories": 2,
    "zoning": "commercial",
    "tenancy": "Vacant",
    "apn": "017104011",
    "address": "240 E Fresno St",
    "city": "Dinuba",
    "county": "Tulare",
    "state": "CA",
    "zip": "93618",
    "latitude": 36.5427648,
    "longitude": -119.3898065,
    "fullAddress": "240 E Fresno St, Dinuba, Tulare, CA 93618",
    "isInOpportunityZone": false,
    "hasOfferingMemorandum": true,
    "marketingDescription": "Located just minutes from downtown Dinuba, this versatile property offers…",
    "attributes": { "Ground Lease": "No", "Permitted Zoning": "commercial", "Lot Size (SqFt)": "14,261" },
    "images": ["https://images.crexi.com/assets/2591585/..._3000x2000_resize.jpg"],
    "imageCount": 6,
    "scrapedAt": "2026-06-18T05:00:00.000Z"
}
```

```json
{
    "type": "brokerLead",
    "brokerId": 3054463,
    "fullName": "Antonio Castillo",
    "brokerTitle": "Real Estate Salesperson",
    "brokerageName": "Harness Realty",
    "brokerageAddress": "124 West Tulare Street",
    "brokerageCity": "Dinuba",
    "brokerageState": "CA",
    "brokerageZip": "93618",
    "brokeragePhone": "559-305-8361",
    "licenses": ["02095413"],
    "licenseStateCode": "CA",
    "publicProfileId": "antoniocastillo4",
    "profileUrl": "https://www.crexi.com/profile/antoniocastillo4",
    "numberOfActiveListings": 2,
    "isPlatinum": false,
    "leadScore": 67,
    "sourceAssetId": 2591585,
    "sourceAssetName": "240 E Fresno St",
    "sourceState": "CA",
    "sourceAskingPrice": 850000,
    "scrapedAt": "2026-06-18T05:00:00.000Z"
}
```

### Monitor mode — only new & changed (works *with* Schedules)

Turn on **`monitorMode`** and the actor remembers what it emitted in previous runs (in a named key-value store) and outputs **only new listings, price drops/rises, status changes and newly sold assets** — each tagged with a `monitorReason`. This is **complementary to**, not a replacement for, [Apify Schedules](https://docs.apify.com/platform/schedules): you use a Schedule to decide *when* the actor runs (e.g. every morning), and monitor mode makes each run return *only the deltas*. Use a distinct `monitorKey` per saved search so separate watch lists keep their own memory.

### Automate & schedule

Run this actor on autopilot and pull results into your own stack:

- **[Apify API](https://docs.apify.com/api/v2)** — start runs, fetch datasets, and manage schedules over REST.
- **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[apify-client for Python](https://docs.apify.com/api/client/python/)** — official SDKs.
- **[Schedules](https://docs.apify.com/platform/schedules)** — run it hourly/daily/weekly with `monitorMode` to watch a market, asset class, or price band for new deals and price drops.
- **[Webhooks](https://docs.apify.com/platform/integrations/webhooks)** — trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

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

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

const run = await client.actor('scrapesage/crexi-scraper').call({
    outputType: 'search',
    states: ['TX'],
    propertyTypes: ['Multifamily'],
    askingPriceMin: 1000000,
    includeBrokerLeads: true,
    maxResults: 200,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} CRE listings & broker leads`);
```

### Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

- **[Make](https://docs.apify.com/platform/integrations/make)** — multi-step automation scenarios.
- **[Zapier](https://docs.apify.com/platform/integrations/zapier)** — push new broker leads straight into your CRM.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when a monitored search finds new listings or price drops.
- **[Google Drive / Sheets](https://docs.apify.com/platform/integrations/drive)** — auto-export every run to a spreadsheet.
- **[Airbyte](https://docs.apify.com/platform/integrations/airbyte)** — pipe results into your data warehouse.
- **[GitHub](https://docs.apify.com/platform/integrations/github)** — trigger runs from commits or releases.

### Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. You can call this actor from Claude, ChatGPT, or any agent framework through the **[Apify MCP server](https://docs.apify.com/platform/integrations/mcp)** — ask your assistant to "find multifamily deals in Texas under $5M and list the brokers" and let it run this scraper for you.

### Agent-ready: autonomous payments (x402 & Skyfire)

This actor is **agent-ready** — AI agents can discover it, run it, and **pay for it autonomously**, with no Apify account and no human in the loop. It uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) — no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)** — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

### More scrapers from scrapesage

Build a complete **real estate & B2B lead-gen stack**:

- **[Redfin Scraper](https://apify.com/scrapesage/redfin-scraper)** — US residential listings, sold comps & estimates.
- **[Realtor.ca Scraper](https://apify.com/scrapesage/realtor-ca-scraper)** — Canadian property listings & agent leads.
- **[Rightmove Scraper](https://apify.com/scrapesage/rightmove-scraper)** — UK property listings & agent leads.
- **[Rent.com Scraper](https://apify.com/scrapesage/rent-com-scraper)** — US apartments, rentals & property-management leads.
- **[Property Finder Scraper](https://apify.com/scrapesage/property-finder-scraper)** — UAE real estate, agents & leads.
- **[FastExpert Scraper](https://apify.com/scrapesage/fastexpert-agent-scraper)** — US real estate agent leads & reviews.
- **[ImportYeti Scraper](https://apify.com/scrapesage/importyeti-scraper)** — US import records, suppliers & B2B leads.
- **[FMCSA Trucking Scraper](https://apify.com/scrapesage/fmcsa-trucking-scraper)** — motor carriers, authority & contact leads.

### Tips

- **Filter precisely**: `states` is the exact geographic filter; `searchText` is a loose keyword/area match. Combine them (e.g. `states: ["TX"]` + `searchText: "Austin"`) to focus a market.
- **Cost control**: `includePropertyDetails` (on by default) fetches the full record + photos per listing. Turn it off for fast, card-level listings, and keep `includeBrokerLeads` off until you specifically want leads.
- **Big markets**: a state + property-type query can return tens of thousands of listings — set `maxResults`, narrow by price band, or split runs by property type.
- **Recurring monitoring**: combine [Schedules](https://docs.apify.com/platform/schedules) with `monitorMode` to track only new listings and price drops.
- **Proxies**: keep the default Apify datacenter proxy; the actor rotates a fresh IP per request.

### FAQ

**How do I scrape Crexi listings for a specific city or state?** Put state codes in `states` (e.g. `["TX"]`) and add the city or keyword to `searchText`. For exact listings, paste their `/properties/<id>/<slug>` URLs into `startUrls`.

**Does it need the Crexi API or a key?** No key, no login, no browser. The actor reads Crexi's own public marketplace endpoints and ships the same (and richer) data you see on the site.

**Where do the broker phone numbers come from?** From the license details Crexi publishes for each listing broker — the same brokerage contact a visitor sees on the listing page. Turn on `includeBrokerLeads` (or use `brokerLeads` mode) to collect them.

**Can I export to Google Sheets, CSV, or Excel?** Yes — one click in the dataset view, or automatically on every run via the [Google Drive integration](https://docs.apify.com/platform/integrations/drive).

**How do I monitor new commercial listings automatically?** Turn on `monitorMode` and create a [Schedule](https://docs.apify.com/platform/schedules); each run outputs only new or changed listings, optionally pushed to your CRM via a [webhook](https://docs.apify.com/platform/integrations/webhooks) or [Zapier zap](https://docs.apify.com/platform/integrations/zapier).

**A field is null — why?** Some listings genuinely don't publish a price (call-for-offers/auction), a cap rate, or an occupancy figure. Fields are `null` only when the data doesn't exist, not because the scraper skipped them.

**Is scraping Crexi legal?** This actor collects publicly available data only. You are responsible for using the data in compliance with applicable laws (e.g. GDPR/CCPA for personal data) and Crexi's terms.

### Need help?

Open an issue on the actor's **Issues** tab, or visit the [Apify help center](https://help.apify.com/). Feature requests are welcome — this actor is actively maintained.

# Actor input Schema

## `outputType` (type: `string`):

search = commercial real estate listings (the headline mode). propertyDetail = look up full property records by Crexi ID or URL. brokerLeads = deduped CRE broker contact leads sourced from the matching listings.

## `searchText` (type: `string`):

Free-text query matched across property name, description and area — e.g. "Austin", "gas station", "medical office", a ZIP or an address. Combine with the precise State and Property type filters below. Leave empty to browse the whole marketplace.

## `states` (type: `array`):

Filter listings by US state — 2-letter codes (TX, CA, FL) or full names (Texas). Leave empty for all states. This is the precise location filter (Search text alone is a loose keyword match).

## `propertyTypes` (type: `array`):

Filter by CRE property type. Valid values: Multifamily, Office, Retail, Industrial, Hospitality, Land, Special Purpose, Mixed Use, Self Storage, Mobile Home Park, Senior Living, Note/Loan, Business For Sale. Leave empty for all types.

## `askingPriceMin` (type: `integer`):

Only listings with an asking price at or above this value. Set "Include unpriced" off to exclude call-for-offer / unpriced listings.

## `askingPriceMax` (type: `integer`):

Only listings with an asking price at or below this value.

## `includeUnpriced` (type: `boolean`):

Include listings marketed without a public asking price ("Contact for price" / auctions / call-for-offers). Turn off to keep only priced listings.

## `assetIds` (type: `array`):

For outputType = propertyDetail or brokerLeads: numeric Crexi asset IDs (the number in a /properties/<id>/<slug> URL).

## `startUrls` (type: `array`):

Paste Crexi listing URLs (https://www.crexi.com/properties/<id>/<slug>) to scrape them directly. Works alongside the filters above and in any mode.

## `includePropertyDetails` (type: `boolean`):

In search mode, fetch each listing's full record (marketing description, cap rate / NOI / tenancy / year built / zoning and all other financial & physical attributes, plus the photo gallery). Off = faster, card-level listings only. When on, each record is billed as a property detail.

## `includeBrokerLeads` (type: `boolean`):

In search / propertyDetail mode, also emit one deduped CRE broker lead per listing broker (name, brokerage, license, phone, profile, lead score). The dedicated "Broker leads" mode outputs only leads.

## `maxPhotos` (type: `integer`):

Cap on high-resolution gallery image URLs collected per property (detail records only).

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

Overall cap on the number of listings (or leads) collected for this run.

## `monitorMode` (type: `boolean`):

Remember what was emitted in previous runs (in a named key-value store) and output only NEW or CHANGED listings — new listings, price drops/rises, status changes (e.g. on-market → sold). Perfect for scheduled CRE deal-flow and price-watch alerts. Each record carries a monitorReason field.

## `monitorKey` (type: `string`):

Namespace for monitor memory. Use a distinct key per saved search so separate watch lists don't share state.

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

Parallel requests. The actor rotates a fresh proxy IP per request; lower this if you hit throttling.

## `proxyConfiguration` (type: `object`):

Proxy settings. Apify Proxy (datacenter) is recommended and enabled by default — Crexi's public API is clean from datacenter IPs with fresh-session rotation.

## Actor input object example

```json
{
  "outputType": "search",
  "includeUnpriced": true,
  "includePropertyDetails": true,
  "includeBrokerLeads": false,
  "maxPhotos": 25,
  "maxResults": 100,
  "monitorMode": false,
  "monitorKey": "default",
  "maxConcurrency": 6,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All scraped CRE listing, property-detail and broker-lead records as JSON items in the default dataset.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/crexi-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/crexi-scraper").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 '{}' |
apify call scrapesage/crexi-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/crexi-scraper"
        }
    }
}

```

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/Wzuho5UTyAFep8N7o/builds/sRDX9Dax4Ty40o2eP/openapi.json