# Chicago Property Use and Occupancy Changes (`recordfoundry/chicago-property-use-changes`) Actor

Find Chicago building permits describing a change in property use or occupancy. Get previous and planned uses, addresses, permit status, and original source wording as JSON.

- **URL**: https://apify.com/recordfoundry/chicago-property-use-changes.md
- **Developed by:** [Record Foundry](https://apify.com/recordfoundry) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1,000.00 / 1,000 nonempty chicago permit reports

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/actors/running/actors-in-store.md#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

## Chicago Property Use and Occupancy Changes

Find City of Chicago building permits whose descriptions explicitly state a change from one use or occupancy to another. The report keeps the original description, permit ID and number, issue date, status, milestone, address, and an official City data link.

The City dataset includes residential and commercial permits. This tool does not classify them, infer a business opening, identify a tenant, predict an opening date, or say that work is complete. It uses fixed text rules and no LLM calls.

### Input

Use an empty object for the latest seven UTC dates, or provide an inclusive range of up to 31 days:

```json
{"startDate":"2026-08-08","endDate":"2026-09-07"}
```

### Matching and source limits

It selects the bounded wording `change (of|in) (use|occupancy) ... from ... (to|into) ...`. It rejects negated wording such as “no change in use” and deliberately excludes the contextual `change of use & ... to ...` construction. These limits make results reviewable but non-exhaustive.

Each run queries the official City of Chicago Building Permits dataset (`ydr8-5enu`) by `issue_date`, counts the rows independently, then downloads at most 5,000 rows. It verifies metadata before and after collection, the count, unique IDs, required identities, and date bounds. A source failure is an error; it is never returned as an empty report.

### Output and caveats

One dataset item is emitted for each successful run. `records` contains each supported transition and its exact source quote. `sourceStatus` and `sourceMilestone` may be null because the source does not publish them for every permit type. `openingDate` is always null, and `historicalTransitionObserved` is always false. `summaries` has `summaryVersion: "1"` and deterministic exact-text `plannedUseCounts`, `sourceStatusCounts`, and `locationCounts`. A permit counts once per distinct planned-use label, so planned-use totals can exceed the permit count. A null status is missing or unavailable source data. Locations are not grouped into neighborhoods or geocoded.

The dataset is a current City publication and can change. A permit description is evidence of authorized work as described by the City, not proof of current occupancy, completion, a new business, or an opening date. City scope is Chicago only, not Cook County or the metropolitan area.

Source: [City of Chicago Building Permits](https://data.cityofchicago.org/Buildings/Building-Permits/ydr8-5enu). This service is not affiliated with the City of Chicago.

### Pricing and local verification

One successfully delivered nonempty report uses the `report` charge event ($1). Empty reports return one free report item. Runtime: Python 3.12 with Apify SDK 4.0.2.

```sh
python -m unittest -v
```

### More from Record Foundry

[Record Foundry publisher](https://apify.com/recordfoundry) · [Austin Commercial Change-of-Use Permits](https://apify.com/recordfoundry/austin-commercial-use-changes) · [FDA Import Refusal History by Facility](https://apify.com/recordfoundry/fda-import-refusal-history)

# Actor input Schema

## `startDate` (type: `string`):

YYYY-MM-DD. Defaults to six days before endDate. Maximum window: 31 days.

## `endDate` (type: `string`):

YYYY-MM-DD. Defaults to today UTC. Future dates are rejected.

## Actor input object example

```json
{}
```

# Actor output Schema

## `report` (type: `string`):

One JSON report with date, source-count, and matched-permit information.

# 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("recordfoundry/chicago-property-use-changes").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("recordfoundry/chicago-property-use-changes").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 recordfoundry/chicago-property-use-changes --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,recordfoundry/chicago-property-use-changes"
        }
    }
}

```

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/YStEk36qsprJyjrvm/builds/oINEO2icdaaxl91Hg/openapi.json