# Building Permit Address Lookup - Open & Expired Permit Check — workflow

## Choose this tool

Review specific properties without sorting a whole-city permit feed. Each successful address check brings together matching permits, available open/expired indicators and a plain-language summary for further investigation.

Useful output columns: `city`, `state`, `matchConfidence`, `permitCount`, `permitCapReached`, `openPermitCount`.

## Practical workflow

Create a property-review checklist using the three Austin addresses in the starter below. One saved row is an address-level permit assessment, not one permit.

1. Keep `city: "austin"` and inspect the existing address examples before entering your own properties. Set the lookback period and per-address permit cap deliberately; the address count determines the number of requested assessments. Check the Store's current per-address rate and set a maximum run charge.
2. Map `queryAddress`, `city`, `matchConfidence`, `permitCount`, `permitCapReached`, `openPermitCount`, `statusUnknownCount`, `issuedNeverFinaledCount`, `humanSummary` and `verdictBasis` into your checklist. Keep `JSON.stringify([city, queryAddress])` as a consistent query key, not a universal parcel identifier.
3. Route uncertain address matches, unknown statuses or reached permit caps to manual review before interpreting the summary. Open the underlying municipal records to verify important findings. No matching record within the chosen coverage is not proof that a property has no permit history.
4. For repeat reviews, rerun the same query scope and compare saved output downstream. Retain the observation date and run ID; update the existing address entry and keep prior observations if an audit trail is needed. There is no native change-only switch.

**Use the result correctly:** Coverage is limited to supported cities and the selected lookback. A permit status or computed summary does not establish a code violation, legal clearance, property condition or whether work actually occurred. The workflow creates no schedule or customer destination automatically.

## Check the fit

Coverage is ten supported portals, one city per run. Some cities cannot support open or expired verdicts. An expired-but-open record is a flag to investigate, not proof of unpermitted work or a substitute for an official search.

## Real output sample

One selected row from a 2026-10-14 run. One saved row, selected scalar columns only. Contact details, patient demographics and long text are omitted. Original values and nulls are preserved.

Run: ePggVCyw9HV66lXxb. Summary status: not specified. Incomplete: not specified.

Historical output from this run; the current example input is a separate starting configuration and may produce different records.

```json
{
  "city": "Austin",
  "state": "TX",
  "matchConfidence": "exact",
  "permitCount": 2,
  "permitCapReached": false,
  "openPermitCount": 1,
  "statusUnknownCount": 0,
  "issuedNeverFinaledCount": 1,
  "expiredButOpen": true,
  "scrapedAt": "2026-10-14T14:10:13.663Z"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [Business License Scraper - New Business Leads, 7 Markets](https://mayd-it.com/data-tools/actors/us-business-licenses-scraper/)

New business leads scraper for 7 US city & statewide registries. Export newly registered businesses with address, phone & email to CSV/JSON. Keep this Business License Scraper evidence alongside the original source in a reviewed local project research workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Addresses and business names require review across sources. A permit, license, inspection or directory listing does not establish purchase intent, current operating status or suitability.

### [Restaurant Inspection Data Scraper - 7 US Cities](https://mayd-it.com/data-tools/actors/us-restaurant-inspections-scraper/)

Restaurant inspection data scraper for 7 US cities in one normalized schema: health grades, scores, violation detail, geocodes. Export CSV/JSON or monitor for new results. Keep this Restaurant Inspection Data Scraper evidence alongside the original source in a reviewed local project research workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Addresses and business names require review across sources. A permit, license, inspection or directory listing does not establish purchase intent, current operating status or suitability.
