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, 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

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.