# Colorado Long-Term Owner Leads (`lanky_orchid/colorado-longterm-owner-leads`) Actor

Long-term owner (20+ yrs) residential leads from Colorado county assessor public records. Filter by county, tenure, absentee, entity/trust, zip.

- **URL**: https://apify.com/lanky\_orchid/colorado-longterm-owner-leads.md
- **Developed by:** [Michael Ferreyros](https://apify.com/lanky_orchid) (community)
- **Categories:** Real estate, Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 lead records

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

## Colorado Long-Term Owner Leads (Apify actor)

Residential parcels from Colorado county assessor PUBLIC records where the
current owner has held 20+ years (or has no recorded sale). Owner name and
mailing address included - direct-mail ready. Filters: county, tenure,
absentee, LLC/trust, ZIP, market value.

Counties: Denver, Douglas, Adams, Jefferson (more coming).
History depth: Douglas to 1880, Adams 1901, Jefferson 1900; Denver public
transfers start 2015, so Denver "no sale on record" = 11+ yr tenure floor.

Pricing: pay per lead-record event. Data refresh cadence follows each
county's publication schedule (see repo DESIGN.md).

### Deploy notes (private)

1. `scripts/export_parquet.py` -> `data/out/leads.parquet`
2. Upload parquet to public object storage; set `LEADS_PARQUET_URL` env var
   on the actor (Settings -> Environment variables).
3. `apify push` from `actor/`. Configure pay-per-event 'lead-record'
   (suggested $0.01-0.03) in the actor's monetization settings.

# Actor input Schema

## `counties` (type: `array`):

Counties to include.

## `minYearsOwned` (type: `integer`):

Owners with no recorded sale always qualify (see README for per-county history depth).

## `absenteeOnly` (type: `boolean`):

Only include owners whose mailing address differs from the property address.

## `includeEntities` (type: `boolean`):

Include owners flagged as LLC/corporate entities.

## `includeTrusts` (type: `boolean`):

Include owners flagged as trusts.

## `zips` (type: `array`):

Optional situs ZIP filter.

## `minMarketValue` (type: `integer`):

Only include properties at or above this assessed/market value.

## `limit` (type: `integer`):

Maximum number of lead rows to return.

## Actor input object example

```json
{
  "counties": [
    "denver",
    "douglas",
    "adams",
    "jefferson"
  ],
  "minYearsOwned": 20,
  "absenteeOnly": false,
  "includeEntities": true,
  "includeTrusts": true,
  "zips": [],
  "minMarketValue": 0,
  "limit": 1000
}
```

# Actor output Schema

## `leads` (type: `string`):

All matched long-term-owner leads for the run's filters.

# 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("lanky_orchid/colorado-longterm-owner-leads").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("lanky_orchid/colorado-longterm-owner-leads").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 lanky_orchid/colorado-longterm-owner-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lanky_orchid/colorado-longterm-owner-leads"
        }
    }
}

```

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/vQho8TipoaTAXyka3/builds/bj6bjZQz6EC2mp3QN/openapi.json