# Seattle Building Permits & Planning Monitor (`frankycheese/municipal-pre-permit-intelligence`) Actor

Monitor official Seattle building permits and planning activity for new or changed development signals. Get source-linked, replay-safe events for construction, real-estate, and local business research.

- **URL**: https://apify.com/frankycheese/municipal-pre-permit-intelligence.md
- **Developed by:** [franklin mccheese](https://apify.com/frankycheese) (community)
- **Categories:** Lead generation, Business
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$250.00 / 1,000 completed batches

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

## municipal pre-permit intelligence

public Seattle-focused Actor that converts supported official municipal APIs into source-linked change events.

### supported scope

- **Seattle:** validated paid scope; Legistar events/matters plus City of Seattle Socrata building permits.
- Boston and Milwaukee adapters remain offline portability fixtures and are not selectable paid inputs.

no arbitrary portals, PDFs, OCR, or browser automation.

### output

each dataset row is a deterministic `new`, `changed`, `scheduled`, `voted`, or `permitted` event containing stable IDs, prior/current values, normalized municipality/body/matter/permit/location/entity fields, official source URLs, confidence/evidence, freshness metadata, and deterministic cross-source joins.

### state

use a stable `stateStoreName` across runs. unchanged records are retained in state and suppressed from the dataset. `resetState=true` deliberately establishes a fresh baseline.

### charging

one successful bounded batch with at least one useful event charges exactly one `completed-batch` event. empty first runs and unchanged replays do not create a second charge; a replay retains the prior committed receipt for auditability. source-wide failure aborts before charging or state mutation.

The Actor is public on Apify at https://apify.com/frankycheese/municipal-pre-permit-intelligence with pay-per-event pricing of `$0.25` per chargeable completed batch.

### quick start

```json
{
  "cities": ["seattle"],
  "startDate": "2026-10-01",
  "endDate": "2026-10-31",
  "limit": 200,
  "stateStoreName": "seattle-development-watch"
}
```

Reuse the state-store name on a schedule and roll the date window forward. Route `new`, `changed`, `scheduled`, `voted`, and `permitted` rows into a territory queue or webhook. Every signal retains official source links and evidence; confidence is deterministic linkage evidence, not a prediction that construction or procurement will occur.

Useful workflow: Apify schedule → this actor → dataset webhook → Slack channel, project database, or analyst queue. Verify material opportunities against the linked city record before acting.

Other focused monitors: [local website-gap changes](https://apify.com/frankycheese/local-lead-delta), [Florida new entities](https://apify.com/frankycheese/new-entity-delta), and [FDA food-recall watchlists](https://apify.com/frankycheese/fda-recall-match-delta).

# Actor input Schema

## `cities` (type: `array`):

Select only supported official municipal source bundles.

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

ISO date; maximum range is 31 days.

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

ISO date; maximum range is 31 days.

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

Hard source-level row/event cap for this batch.

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

Use the same name across runs for change-only output.

## `resetState` (type: `boolean`):

Deliberately discard the prior change baseline for this named state store.

## Actor input object example

```json
{
  "cities": [
    "seattle"
  ],
  "limit": 200,
  "stateStoreName": "mppi-private-state",
  "resetState": false
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("frankycheese/municipal-pre-permit-intelligence").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("frankycheese/municipal-pre-permit-intelligence").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 frankycheese/municipal-pre-permit-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,frankycheese/municipal-pre-permit-intelligence"
        }
    }
}
```

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/fcIgF8I8BtwL5rqvP/builds/2snIt5btPknEueycv/openapi.json