# US County Assessor Data: Assessed Value, Sales by Parcel (`accountable_eel/us-county-assessor-open-data-lookup`) Actor

Look up a Cook County, Illinois parcel by PIN or street address: assessed land and building value by year, year built, square footage, bedrooms and baths, and recorded sale history, from the county Assessor's open data. Owner names are never returned.

- **URL**: https://apify.com/accountable_eel/us-county-assessor-open-data-lookup.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Real estate, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 parcel returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## US County Assessor Data: Assessed Value, Sales by Parcel

**Look up a Cook County, Illinois parcel by PIN or street address and get its assessed value by year, year built, square footage, bedrooms and baths, and recorded sale history, in one row.**
The data comes straight from the county Assessor's open-data portal, so there is no scraping, no proxy and no key. Who uses it: real-estate analysts and investors pricing a parcel list, proptech and lead-gen teams enriching addresses, appraisers and researchers pulling assessment history. Owner, buyer and seller names are never returned.

Cook County only for now (Chicago and its suburbs, about 1.8 million parcels). A parcel that is a condo, or commercial, has an assessed value and sale history but no year built or bedrooms, because the Assessor publishes those characteristics for single- and multi-family buildings (under 7 units) only.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `parcels` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~us-county-assessor-open-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"parcels":["32213210090000"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "parcels": [
    "32213210090000"
  ]
}
```

One per line: a 14-digit Cook County PIN (dashes allowed, e.g. 32-21-321-009-0000) or a street address (e.g. 1617 Hanover St, Chicago Heights). Owner names are never returned. Accepted formats: 32213210090000, 32-21-321-009-0000, 1617 Hanover St, Chicago Heights IL 60411.

One dataset row is returned per parcel. A PIN or address that matches nothing comes back as a row with `"found": false` and is never charged. An address shared by several parcels (a condo building) returns one row per parcel, up to 5.

### Output

One row per item, for example:

| query | found | status | parcelCount | parcels | pin | pinFormatted | propertyAddress | propertyCity | propertyZip | propertyClass | township | neighborhood | assessmentYear | assessmentStage | assessedBuildingValueUsd | assessedLandValueUsd | assessedTotalValueUsd | valueHistory | yearBuilt | buildingSqft | lotSqft | bedrooms | fullBaths | halfBaths | rooms | characteristicsYear | buildingCount | saleCount | lastSaleDate | lastSalePriceUsd | saleHistory | sourceUrl | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 32213210090000 | true | OK | <parcels returned> | \<all parcels (full list)> | <pin> | \<pin (formatted)> | <property address> | <property city> | <property zip> | <property class code> | <township> | <neighborhood code> | <assessment year> | <assessment stage> | \<assessed building value (usd)> | \<assessed land value (usd)> | \<assessed total value (usd)> | <assessed value by year> | <year built> | <building sqft> | <lot sqft> | <bedrooms> | <full baths> | <half baths> | <rooms> | <characteristics year> | \<buildings (cards) on the parcel> | <recorded sales> | <last sale date> | \<last sale price (usd)> | <sale history> | <source> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged. Values the Assessor did not record are `null`, never `0`. Dollar figures are **assessed** values, not market values: the Assessor assesses residential property at a fraction of market value.

Example row (PIN 32213210090000, trimmed):

```json
{
  "pinFormatted": "32-21-321-009-0000",
  "propertyAddress": "1617 HANOVER ST",
  "propertyCity": "CHICAGO HEIGHTS",
  "assessmentYear": 2025,
  "assessmentStage": "BOARD_OF_REVIEW",
  "assessedBuildingValueUsd": 5256,
  "assessedLandValueUsd": 930,
  "assessedTotalValueUsd": 6186,
  "yearBuilt": 1897,
  "buildingSqft": 740,
  "lotSqft": 3100,
  "bedrooms": 2,
  "fullBaths": 1,
  "saleCount": 0,
  "lastSalePriceUsd": null
}
```

### Pricing

- **Parcel returned**: $30 per 1,000 parcels

Plus a $0.002 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged.

### Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token and no account of your own beyond an Apify login.

**One parcel by PIN.** The default shape (dashes are fine).

```json
{ "parcels": ["32-21-321-009-0000"] }
```

**A list of parcels, assessment history for each.**

```json
{ "parcels": ["32213210090000", "14081020220000"], "maxResults": 20 }
```

**One street address.** House number and street as the Assessor spells it; city or ZIP are optional and narrow the match.

```json
{ "parcels": ["1617 Hanover St, Chicago Heights IL 60411"] }
```

### Data source and limits

Records come from the Cook County Assessor datasets on datacatalog.cookcountyil.gov (assessed values, parcel addresses, single and multi-family improvement characteristics, parcel sales). The portal throttles per IP, so the actor makes about four requests per parcel, one second apart; expect roughly 4 to 6 seconds per parcel. Sale history lists the 10 most recent recorded sales; a sale price of 0 in the source (a transfer with no consideration) is returned as `null`. Property owner and taxpayer names, and sale buyer and seller names, are deliberately excluded.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~us-county-assessor-open-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"parcels":["32213210090000"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~us-county-assessor-open-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"parcels":["32213210090000"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~us-county-assessor-open-data-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"parcels":["{{parcel or address}}"]}`, mapping the row's parcel or address into the `parcels` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "county property assessor data lookup" — the agent will find and run this actor.

# Actor input Schema

## `parcels` (type: `array`):

One per line: a 14-digit Cook County PIN (dashes allowed, e.g. 32-21-321-009-0000) or a street address (e.g. 1617 Hanover St, Chicago Heights). Owner names are never returned. Accepted formats: 32213210090000, 32-21-321-009-0000, 1617 Hanover St, Chicago Heights IL 60411. You're only charged for the ones we actually find — a miss costs nothing.

## `county` (type: `string`):

Which county's Assessor open data to query. Cook County, Illinois is the only county in this release.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each parcel found gets its own row instead of being grouped under its parcel or address. You're still only charged once per parcel or address, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## Actor input object example

```json
{
  "parcels": [
    "32213210090000"
  ],
  "county": "cook-il",
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "parcelCount",
    "parcels",
    "pin",
    "pinFormatted",
    "propertyAddress",
    "propertyCity",
    "propertyZip",
    "propertyClass",
    "township",
    "neighborhood",
    "assessmentYear",
    "assessmentStage",
    "assessedBuildingValueUsd",
    "assessedLandValueUsd",
    "assessedTotalValueUsd",
    "valueHistory",
    "yearBuilt",
    "buildingSqft",
    "lotSqft",
    "bedrooms",
    "fullBaths",
    "halfBaths",
    "rooms",
    "characteristicsYear",
    "buildingCount",
    "saleCount",
    "lastSaleDate",
    "lastSalePriceUsd",
    "saleHistory",
    "sourceUrl"
  ],
  "expandRows": true,
  "maxConcurrency": 1
}
```

# Actor output Schema

## `results` (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 = {
    "parcels": [
        "32213210090000"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/us-county-assessor-open-data-lookup").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 = {
    "parcels": ["32213210090000"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/us-county-assessor-open-data-lookup").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 '{
  "parcels": [
    "32213210090000"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/us-county-assessor-open-data-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/us-county-assessor-open-data-lookup"
        }
    }
}
```

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/nS1eeCgnDQuHeDLx0/builds/bOQUTEX0BLTYmpcsA/openapi.json