# Detroit Building Permits: Business Owners (`transparent_meteorite/detroit-building-permits`) Actor

Building permits issued by the City of Detroit (BSEED, official open data) with the owner of record and mailing address from the city parcel file. Filter by valuation, keyword, use type, business owners only. Lead score and delta mode for new permits.

- **URL**: https://apify.com/transparent_meteorite/detroit-building-permits.md
- **Developed by:** [Detroit Web Agent - Open Data](https://apify.com/transparent_meteorite) (community)
- **Categories:** Lead generation, Real estate, Other
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.50 / 1,000 permit 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/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

## Detroit Building Permits: Business Owners

Pull building permits issued by the City of Detroit (BSEED) together with the owner of record and the owner's mailing address from the city parcel file, ready to filter and score. Data comes straight from the City of Detroit open data portal (data.detroitmi.gov). No login, no proxies, no scraping of web pages.

### Overview

Detroit issues thousands of permits a year, and most are single-family homes. This actor cuts that down to the permits a business actually wants: commercial, industrial and multifamily projects owned by an LLC, corporation, trust, church or similar organization. Every row has the permit, the estimated cost, the property use, the owner of record, the owner's mailing address, the contractor business when the city has a linked trades permit, and a 0 to 100 `leadScore` you can sort or branch on.

What you get:

- Permits issued by BSEED with type, work description, issue date, estimated cost, fee, address, neighborhood and ZIP.
- Owner of record and owner mailing address, joined from the Parcels (Current) file by parcel id.
- `useCategory`: commercial, industrial, multifamily (5+ units) or residential (1 to 4 units).
- `ownerIsBusiness` and a business-owners-only filter.
- `leadScore` (0 to 100): valuation on a log scale (up to 60), property use (up to 20), business owner of record (15), owner mailing address on file (5).
- Contractor business name from a trades permit on the same parcel within 90 days, when one exists.
- Delta mode: only permits not returned by an earlier run.

### Why this vs other Detroit permit actors

- It joins the owner of record and the owner's mailing address to each permit, so you can contact the property owner, not only see the permit.
- It filters to business owners and non-residential use in one run, so you are not paying for single-family rows you then throw away.
- It adds `leadScore`, `useCategory` and `ownerIsBusiness` so a spreadsheet, CRM or n8n flow can sort and route rows without extra work.
- Broader multi-city permit actors and the all-datasets Detroit BSEED actors return permit records but do not rank them or filter by owner type.

### Input

| Field | What it does |
|---|---|
| `sinceDays` | Permits issued in the last N days (1 to 730). Ignored when `dateFrom` is set. |
| `dateFrom`, `dateTo` | Explicit issue date range, YYYY-MM-DD. |
| `minValuation` | Minimum estimated cost in USD. |
| `permitTypes` | Match permit type text, e.g. Alteration, New, Change of Use. |
| `keywords` | Match words in the work description, e.g. roof, HVAC, window. |
| `useTypes` | commercial, industrial, multifamily, residential. Empty = all. |
| `excludeResidential1to4` | Drop 1 to 4 unit residential (default on). |
| `businessOwnersOnly` | Keep only organization owners (default on). |
| `maxItems` | Stop after this many permits (default 50, max 5000). |
| `onlyNewSinceLastRun`, `stateStoreName` | Delta mode: skip permits already returned. |

Example input:

```json
{ "sinceDays": 90, "minValuation": 100000, "useTypes": ["commercial", "multifamily"], "maxItems": 100 }
```

### Output

One row per permit. Fields: `permitNumber`, `issueDate`, `permitType`, `workDescription`, `use`, `useCategory`, `valuation`, `permitFee`, `address`, `neighborhood`, `zipCode`, `parcelId`, `ownerName`, `ownerMailingAddress`, `ownerIsBusiness`, `contractorName`, `leadScore`, `status`, `recordUrl`, `source`. Download as JSON, CSV, Excel or HTML, or read it through the Apify API.

#### Sample output

Real row from a test run:

```json
{
  "permitNumber": "BLD2026-01277",
  "issueDate": "2026-11-16",
  "permitType": "Alter Revision",
  "workDescription": "Revision to BLD2025-02882 to reflect the amended scope of work to Code per plans. (Interior alterations to Code per plans.) Subject to Field Approval.",
  "use": "Shelter",
  "useCategory": "commercial",
  "valuation": 775000,
  "permitFee": 2909.5,
  "address": "11850 Woodrow Wilson St",
  "neighborhood": "Dexter-Linwood",
  "zipCode": "48206",
  "parcelId": "06006162-3",
  "ownerName": "CASS COMMUNITY NONPROFIT HOUSING CO",
  "ownerMailingAddress": "11850 WOODROW WILSON, DETROIT, MI, 48206",
  "contractorName": "Edgewood Electric",
  "ownerIsBusiness": true,
  "status": "Issued",
  "recordUrl": "https://services2.arcgis.com/qvkbeam7Wirps6zC/arcgis/rest/services/bseed_building_permits/FeatureServer/0/query?where=record_id%3D'BLD2026-01277'&outFields=*&returnGeometry=false&f=json",
  "source": "City of Detroit Open Data (data.detroitmi.gov), BSEED Building Permits + Parcels (Current)",
  "leadScore": 79
}
```

### Use cases

1. Commercial roofing, HVAC, electrical and glazing sellers: find owners starting large projects and mail or call the owner of record.
2. Construction suppliers and equipment rental: target projects by valuation and permit type before bids close.
3. Commercial real estate brokers and investors: track change-of-use and new-build permits by neighborhood to spot where capital is moving.
4. Lenders, insurers and title companies: follow active projects by business owners in your territory.
5. Local news, researchers and neighborhood groups: monitor development by ZIP code or neighborhood with the official record link on every row.

### Automate it

Schedule a weekly run with `onlyNewSinceLastRun` on, then send rows with a high `leadScore` to your CRM, Slack or a Google Sheet through Apify integrations, n8n, Make or Zapier.

### Pricing

Pay per event, no subscription. Current prices:

| Event | Price |
|---|---|
| Actor Start | $0.00005 |
| Permit record | $0.0045 |

Apify's free plan includes monthly platform credit that covers test runs.

Examples at the current price (one `apify-default-dataset-item` event per result; Free-plan tier):

| You pull | You pay |
|---|---|
| 100 results | $0.45 |
| 1,000 results | $4.50 |
| 10,000 results | $45.00 |

Scheduled runs stay cheap when each run only returns new records.

### FAQ

**Where does the data come from?** The City of Detroit open data portal: BSEED Building Permits, Parcels (Current) and BSEED trades permits. It is public record data.

**How fresh is it?** As fresh as the city publishes it. Recent permits usually appear within days of issue.

**Why is the contractor name sometimes empty?** The building permit itself does not name the contractor. The name is filled only when the city has a linked trades permit on the same parcel within 90 days.

**How do you decide an owner is a business?** The owner name is checked for organization words (LLC, INC, CORP, TRUST, CHURCH, CITY OF, PROPERTIES and similar). Individuals are dropped when `businessOwnersOnly` is on. It is a name test, so turn the filter off if you want to review borderline names yourself.

**Does it include personal phone numbers or emails?** No. The owner mailing address is the one on the city parcel file.

### Limits

- Detroit only, issued permits only. Permit applications and denials are not included.
- Up to 5000 permits per run and up to 730 days back with `sinceDays`.
- Owner and address come from the city parcel file and can lag recent sales.
- Estimated cost is the figure filed with the city, not the final project cost.
- `leadScore` is a transparent heuristic, not a prediction.

### Pairs well with

- [Building Permits Leads](https://apify.com/transparent_meteorite/building-permits-leads): construction permits from Chicago, NYC, LA, SF, Seattle, Austin and more, with valuation and contractor.
- [Contractor License Lookup](https://apify.com/transparent_meteorite/contractor-license-lookup): verify state trade licenses by name, trade or number.

# Actor input Schema

## `sinceDays` (type: `integer`):

Permits issued in the last N days. Ignored when Date from is set.

## `dateFrom` (type: `string`):

Earliest issue date. Optional.

## `dateTo` (type: `string`):

Latest issue date. Optional, default today.

## `minValuation` (type: `integer`):

Keep permits whose estimated cost is at least this. 0 = no minimum.

## `permitTypes` (type: `array`):

Match permit type text, for example Alteration, New, Addition, Change of Use, Fire Repair. Empty = all.

## `keywords` (type: `array`):

Match words in the work description or permit type, for example roof, HVAC, window. Any match keeps the permit. Empty = all.

## `useTypes` (type: `array`):

commercial, industrial, multifamily (5+ units), residential (1 to 4 units). Empty = all.

## `excludeResidential1to4` (type: `boolean`):

Drops single and two family homes (the bulk of Detroit permits).

## `businessOwnersOnly` (type: `boolean`):

Keep permits whose owner of record looks like an organization (LLC, INC, CORP, CO, TRUST, CHURCH, CITY and similar). Drops owners that look like individuals.

## `maxItems` (type: `integer`):

Stop after this many permits.

## `onlyNewSinceLastRun` (type: `boolean`):

Skip permits already returned by an earlier run that used the same state store.

## `stateStoreName` (type: `string`):

Named key-value store that remembers returned permit numbers.

## Actor input object example

```json
{
  "sinceDays": 30,
  "minValuation": 0,
  "permitTypes": [],
  "keywords": [],
  "useTypes": [],
  "excludeResidential1to4": true,
  "businessOwnersOnly": true,
  "maxItems": 50,
  "onlyNewSinceLastRun": false,
  "stateStoreName": "detroit-building-permits-seen"
}
```

# Actor output Schema

## `overview` (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 = {
    "sinceDays": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("transparent_meteorite/detroit-building-permits").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 = { "sinceDays": 30 }

# Run the Actor and wait for it to finish
run = client.actor("transparent_meteorite/detroit-building-permits").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 '{
  "sinceDays": 30
}' |
apify call transparent_meteorite/detroit-building-permits --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,transparent_meteorite/detroit-building-permits"
        }
    }
}
```

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/earSl0NgKcesVVnng/builds/DYs8pI7nhUynCpWgK/openapi.json
