Crexi Commercial Property Listings & Pricing Extractor: MCP config, n8n workflow and API

{
  "opportunityZoneOnly": false,
  "includeUnpriced": true,
  "sortBy": "Rank",
  "sortDirection": "Descending",
  "scrapeDetails": false,
  "includeSimilarProperties": false,
  "maxProperties": 5
}

---
name: crexi-commercial-property-listings-and-pricing
description: "Dataset of Crexi sale, lease and auction commercial property listings with pricing, cap rate, NOI, sizes, brokers, locations, photos and optional detail enrichment. Runs the Apify Actor dataspryva/crexi-commercial-property-listings-and-pricing. Use when the user needs Crexi data with fields such as name, transaction_type, property_type, city, state, price and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "dataspryva/crexi-commercial-property-listings-and-pricing"
  store-url: "https://apify.com/dataspryva/crexi-commercial-property-listings-and-pricing"
---

# Crexi Commercial Property Listings & Pricing Extractor

Use this skill to fetch Crexi data with the Apify Actor `dataspryva/crexi-commercial-property-listings-and-pricing` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `propertyUrls` | array | Paste Crexi property links or IDs (e.g. https://www.crexi.com/properties/123456/name, /lease/properties/987/name, a bare ID, or a property-record link) to fetch those exact listings. |
| `searchTerms` | array | Free-text keywords matched against listing names, descriptions and addresses (e.g. warehouse, medical office). |
| `cities` | array | City names to filter by (e.g. Austin). Works alongside or instead of states. |
| `counties` | array | County names to filter by, including the word County where Crexi uses it (e.g. Travis County). |
| `zipCodes` | array | US ZIP codes to filter by (e.g. 78701). |
| `opportunityZoneOnly` | boolean | Only return sale listings located in a designated Opportunity Zone. |
| `includeUnpriced` | boolean | Include sale and auction listings Crexi shows without a public asking price (auctions, call for offers). |
| `sortBy` | one of `Rank`, `Price`, `CapRate`, `Noi`, `UpdatedOn`, `ActivatedOn`, `CreatedOn` | Order of results within each search. |
| `sortDirection` | one of `Descending`, `Ascending` | Ascending or descending order for the sort chosen above. |
| `scrapeDetails` | boolean | Fetch each listing's detail data: broker contacts (phone and email), the broker of record when published, the full photo gallery in high resolution, investment highlights, the marketing description, published fact-sheet values, and full auction details for… |
| `includeSimilarProperties` | boolean | Add up to 6 similar nearby listings (comps) to each record. |
| `maxProperties` | integer | Stop once this many listings have been collected. Crexi returns at most 1,500 rows per filter combination; larger requests are automatically split into price-range partitions. |

Example `input.json` (the Actor's published prefill):

```json
{
  "opportunityZoneOnly": false,
  "includeUnpriced": true,
  "sortBy": "Rank",
  "sortDirection": "Descending",
  "scrapeDetails": false,
  "includeSimilarProperties": false,
  "maxProperties": 5
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~crexi-commercial-property-listings-and-pricing/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~crexi-commercial-property-listings-and-pricing/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `name`, `transaction_type`, `property_type`, `city`, `state`, `price`, `cap_rate`, `net_operating_income`, `building_sqft`, `broker_names`, `property_url`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.