# US Property Lookup - Listings, Tax Liens & Foreclosures (`dwelldata/us-property-lookup`) Actor

One property in, everything we know out. Give a street address or parcel id (APN) and get every matching record across active multifamily listings (with NOI/DSCR underwriting), county tax delinquency signals, and sheriff sale auctions, each with its source URL. A no-match lookup is not charged.

- **URL**: https://apify.com/dwelldata/us-property-lookup.md
- **Developed by:** [Sean](https://apify.com/dwelldata) (community)
- **Categories:** Real estate, Lead generation, Agents
- **Stats:** 2 total users, 1 monthly users, 83.3% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 property lookups

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

## US Property Lookup — Listings, Tax Delinquency & Foreclosure by Address

**One property in, everything we know out. You never pay for a blank.**

Give this Actor a street address or a county parcel id (APN) and it returns every
matching record we hold for that one property, across three separate public-record
feeds — in a single call. Built for the question an investor actually asks: *"what's
the story on this address?"*

### What one lookup returns

| Section | What's in it |
|---|---|
| `listings` | Any active small-multifamily listing at that address, with typed underwriting: advertised cap rate vs. an independent **HUD-SAFMR-underwritten** cap and NOI, **DSCR** under declared assumptions, list price, units, and the listing URL |
| `distress_signals` | County **tax-delinquency** records: owner name, parcel id, delinquent amount, and the public-record source URL |
| `auctions` | Upcoming **sheriff-sale foreclosure** auctions: sale date, appraised value, opening-bid floor, case number, parties, and the official court-journal source URL |
| `matches` | A count per section, so you can tell "nothing there" from "didn't look" |
| `coverage_note` | Plain-language explanation of what a zero in any section actually means |

Every row carries its own **public source URL** — you can verify any claim against
the county's own record.

#### A zero is explained, never implied

If a section returns nothing, `coverage_note` tells you whether that's because the
property is clean or because it's outside our coverage for that feed. A zero in
`distress_signals` for a Texas property means we don't cover that county — not that
the taxes are paid. That distinction is the whole point.

#### You never pay for a blank

Pricing is **pay-per-event: one charge per property looked up.** If we hold nothing
at all on that address, the run returns a typed reason and **the lookup charge is
not applied** — you are never billed for an empty answer.

*(The only thing a no-match run costs is Apify's platform start fee of $0.00001 —
the minimum the Store allows, roughly one cent per thousand lookups. We keep it at
that floor rather than removing it because it covers the run's compute.)*

### Input — one of `address` or `apn` is required

| Field | Meaning |
|---|---|
| `address` | Street address, e.g. `2615 N Gettysburg Ave`. Number and street are enough. |
| `apn` | County parcel id, e.g. `H33300821 0125`. Spaces and dashes ignored. Matches distress + auction records only — listings carry no parcel id. |
| `city` | Optional. Disambiguates a street name that exists in several cities. |
| `state` | Optional two-letter state code. |

### Output

One dataset item per run — the complete bundle for that property. `matches` gives
you the per-feed counts at a glance; the three arrays hold the records themselves.

### Coverage & freshness

- **Listings:** small multifamily across ~20 US metros (Midwest + Sun Belt), refreshed daily
- **Tax-delinquency signals:** Cincinnati, Toledo, Dayton and Akron OH
- **Foreclosure auctions:** Summit and Mahoning counties OH

Underwriting is recomputed every two days. Parcel/APN lookups match distress and
auction records only.

***

*Data provided by the DwellData real-estate data engine. Sibling Actors cover the
full scored multifamily deals feed, county tax-delinquency distress signals,
sheriff-sale foreclosure auctions, and scored off-market seller leads.*

# Actor input Schema

## `address` (type: `string`):

Street address of the property, e.g. "2615 N Gettysburg Ave". House number and street are enough, leave off city/state/ZIP here and use the fields below. Required unless you supply a parcel id.

## `apn` (type: `string`):

County parcel number, e.g. "H33300821 0125". Spaces and dashes are ignored. Matches distress and auction records only — listings carry no parcel id. Required unless you supply an address.

## `city` (type: `string`):

Optional. Narrows the match when the same street name exists in several cities.

## `state` (type: `string`):

Optional two-letter state code.

## Actor input object example

```json
{
  "address": "2615 N Gettysburg Ave",
  "apn": "H33300821 0125",
  "city": "Dayton",
  "state": "OH"
}
```

# Actor output Schema

## `result` (type: `string`):

The full bundle for the property that was looked up.

## `summary` (type: `string`):

Per-feed match counts, the query as resolved, and the data guarantee.

# 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 = {
    "address": "2615 N Gettysburg Ave",
    "city": "Dayton",
    "state": "OH"
};

// Run the Actor and wait for it to finish
const run = await client.actor("dwelldata/us-property-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 = {
    "address": "2615 N Gettysburg Ave",
    "city": "Dayton",
    "state": "OH",
}

# Run the Actor and wait for it to finish
run = client.actor("dwelldata/us-property-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 '{
  "address": "2615 N Gettysburg Ave",
  "city": "Dayton",
  "state": "OH"
}' |
apify call dwelldata/us-property-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dwelldata/us-property-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/3iBh9Et0Vjpx2ACXj/builds/DSJVp1Pt8CFIseU1A/openapi.json