# Crexi Powerai Properties and Details Scraper (`realestateapi/crexi-powerai-properties-and-details-scraper`) Actor

Permission-gated Crexi commercial property scraper. Default runs make zero source requests; automated extraction requires an applicable written agreement.

- **URL**: https://apify.com/realestateapi/crexi-powerai-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Crexi PowerAI Properties and Details Scraper

This Actor is permission-gated. Crexi's Customer Terms of Service, section 3.5(a), prohibit scraping/copying through automated systems and accessing content through means not provided or authorized by Crexi. No applicable written agreement or approved data-access route is recorded for this project. A default run completes as `SUCCEEDED` / `SKIPPED_POLICY`, makes zero source requests, and writes no dataset rows.

Set `authorizationConfirmed` only when current written terms or a signed agreement explicitly authorizes this Actor's automated extraction and the intended dataset reuse. This checkbox is an operator attestation; it does not grant permission. Do not use proxies, alternate transports, or redirects to work around Crexi's restrictions.

### Current source and saved-data review

On 2026-09-25, Chrome rendered Crexi's public for-sale search interface. The official [Customer Terms of Service](https://www.crexi.com/tos), last modified October 28, 2024, were then reviewed; section 3.5 prohibits scraping/copying and unauthorized automated access. No property detail or contact control was opened after reviewing the terms, no listing-specific values were added to project files, and no Actor/source request was made during this review.

The active saved dataset contains no property rows. Its one historical six-field `HTTP_403` diagnostic was preserved byte-for-byte outside the Actor folder and removed from the active dataset. The historical run summary is `FAILED` / `FAILED` with zero saved listings. Neither the schema nor the parser test fixture proves current live listing coverage.

### Potential output fields

The schema describes normalized identity, listing URL, title, property type/status, price and currency, address, location, coordinates, building and lot sizes, cap rate, year built, broker fields, images, and description. Optional values are omitted. Run failures are summarized in the key-value store and never emitted as dataset rows. Current source field coverage is unverified because no source-backed record is available.

### Run status

- A no-request authorization skip is `SUCCEEDED` / `SKIPPED_POLICY`.
- A source failure or empty result with no saved property listings is `FAILED` / `FAILED` and exits unsuccessfully.
- If at least one real listing is saved before a later request or storage error, the run is `SUCCEEDED` / `PARTIAL`.
- A complete run with saved listings is `SUCCEEDED` / `COMPLETED`.

### Input

- `authorizationConfirmed` — defaults to `false`; this Actor makes zero source requests while false.
- `startUrls` — optional HTTPS Crexi search or property URLs, host-validated before use.
- `searchQueries`, `locations`, `propertyTypes` — bounded search inputs used to construct candidate URLs only after authorization is confirmed.
- `maxPages`, `maxItems` — bounded limits for an authorized run.

The Actor does not sign in, submit requests for information, collect gated broker contact details, or solve challenges. It accepts only credential-free HTTPS URLs on `crexi.com` or `www.crexi.com`, blocks off-site redirects, limits each response to 5 MiB and 25 seconds, and follows canonical Crexi listing-detail links. Title-only page shells and security-challenge responses do not produce listing rows.

### Offline validation

```bash
npm test
npm run check
npx apify validate-schema
```

### Runtime dependency remediation

Batch input and JSON storage use the documented Apify REST API and isolated local JSON storage, with environment-only credentials, bounded requests, no platform redirects, and no automatic dataset-POST retry. The Actor does not import the full Apify/Crawlee SDK. Source collection rules and authorization gates are unchanged. This adapter does not provide request queues, proxies, browser automation, encrypted input fields, or long-running system-event migration. Those capabilities are not used by this implementation.

# Actor input Schema

## `authorizationConfirmed` (type: `boolean`):

Set true only when current written authorization explicitly permits this Actor's automated listing extraction and intended dataset reuse. This attestation does not grant permission. Defaults to false and makes zero source requests.

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

HTTPS Crexi listing or search pages, used only after written authorization is confirmed.

## `searchQueries` (type: `array`):

Public Crexi search phrases.

## `locations` (type: `array`):

Locations used for generated Crexi searches.

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

Property types used for generated searches.

## `maxPages` (type: `integer`):

Maximum public Crexi pages to inspect.

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

Maximum Crexi listings to emit.

## Actor input object example

```json
{
  "authorizationConfirmed": false,
  "maxPages": 5,
  "maxItems": 100
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/crexi-powerai-properties-and-details-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("realestateapi/crexi-powerai-properties-and-details-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 realestateapi/crexi-powerai-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/crexi-powerai-properties-and-details-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/5LczMK8fpxWUTDBsT/builds/DyBvfKaJOdT09pJs0/openapi.json