# Centris Broker Profile Scraper (`realestateapi/centris-agent-properties-and-details-scraper`) Actor

Centris broker-profile Actor; live collection is disabled because current Terms prohibit scraping and data mining. The default run completes SUCCEEDED / SKIPPED_POLICY with no source requests.

- **URL**: https://apify.com/realestateapi/centris-agent-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

## Centris Broker Profile Actor

This Actor is scoped to Quebec broker and agency profiles. It is currently **disabled for live collection** because the Centris Terms of Use, last updated May 15, 2025, prohibit screen scraping, data scraping, and data mining intended to collect, store, copy, reproduce, reorganize, or manipulate site content. No applicable written permission is recorded.

The entrypoint completes as `SUCCEEDED` / `SKIPPED_POLICY` and makes zero source requests. It accepts no input that can enable networking. Do not restore live requests unless applicable written permission from the rights holder has been reviewed and the Actor is deliberately updated. Offline parser output omits phone numbers, office addresses, contact-form links, and any broker profile missing its real name; those fields remain optional in the dataset schema only to describe unchanged historical rows.

The directory and profile parser modules remain available for offline development and tests. They do not imply permission to fetch Centris pages. Historical dataset rows are retained unchanged; they were recorded before the current Terms review and are not fresh-verified output. If a future authorized source request fails before saving profiles, report `FAILED` / `FAILED`; if real profiles were saved before a later failure, keep the run `SUCCEEDED` / `PARTIAL`. Failures and policy skips do not become dataset rows.

### Local checks

```text
npm test
npx apify validate-schema
```

These checks are offline. Do not run the previous live `apify run` command while collection remains disabled.

### Dependency security — October 3, 2026

Compatible dependency updates and the patched `basic-ftp` 6.2.1 are locked in `package-lock.json`. Offline regression checks exercise the API used by `get-uri` and bound adversarial listing parsing in a subprocess. The Docker build uses Node 24 and `npm ci --omit=dev --ignore-scripts`; it does not silently re-resolve dependency ranges.

`http-cache-semantics` currently has no published patched version for [GHSA-ch52-4w7c-c8xp](https://github.com/advisories/GHSA-ch52-4w7c-c8xp). It remains a transitive SDK dependency and an unresolved release-security prerequisite. Do not treat closed policy gates or an untested claim of unreachable code as a security fix. Applicable source permission/access and current-build extraction proof are also still required.

# Actor input Schema

## Actor input object example

```json
{}
```

# 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/centris-agent-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/centris-agent-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/centris-agent-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/centris-agent-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/FNC7LM0yGoicje7la/builds/At1a7CR1xUtGdwivk/openapi.json