# Site Due-Diligence Bundle — One-Call Fatal-Flaw Scorecard (`malonestar/site-due-diligence-bundle`) Actor One call (lat/lon + radius) returns a Phase-I fatal-flaw site scorecard across 15 layers: EPA contamination, flood, ESA habitat, protected lands, seismic, wildfire, karst, landslide, levee, impaired waters, grid, IRA energy community, tank/spill registries, gas pipelines, CalFire FHSZ. - **URL**: https://apify.com/malonestar/site-due-diligence-bundle.md - **Developed by:** [Kyle Maloney](https://apify.com/malonestar) (community) - **Categories:** Real estate, Developer tools, Agents - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $55.00 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/integrations/mcp.md). If your project is in a different language, use 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 ## Site Due-Diligence Bundle — One-Call Fatal-Flaw Scorecard Takes a coordinate and a radius and returns one site-screening scorecard that runs fifteen environmental, hazard, regulatory, and opportunity checks at once, instead of calling fifteen separate actors. Each site comes back as a single row with a rolled-up `fatal_flaw_count`, a `flags` list, an `opportunities` list, and a plain-language summary. Built as a fast pre-screen for site selectors, developers, and the consultants who scope the real studies. ### What it screens (15 layers) | Layer (`layers` key) | Source | Result type | |---|---|---| | `epa_contamination` | EPA ECHO (`echodata.epa.gov`) — RCRA hazardous-waste handlers and TRI reporters within the radius | flag | | `flood_risk` | FEMA National Risk Index (county) resolved via the FCC block geocoder | flag on high inland/coastal flood risk | | `critical_habitat` | USFWS ESA Critical Habitat, Final + Proposed | flag (ESA Section 7) | | `protected_lands` | USGS PAD-US protected/conservation lands (point-in-polygon) | flag | | `seismic_design` | USGS ASCE 7-16 seismic design web service | flag on high Seismic Design Category / site-specific study | | `wildfire_exposure` | NIFC WFIGS active perimeters and incidents | flag when in or near an active fire | | `karst_terrain` | USGS CONUS_Karst national karst/pseudokarst compilation (OFR 2014-1156), 7 layers | flag — `Elevated` (near-surface soluble rock) or `Moderate` (buried/pseudokarst) tier | | `landslide_hazard` | USGS US Landslide Inventory (mapped polygons + points) | flag — inside a mapped slide, or a mapped slide within the radius | | `levee_proximity` | USACE National Levee Database (NLD) Leveed Areas | flag — behind a mapped levee, with an editorial 0–100 `levee_risk_score` | | `impaired_waters_303d` | EPA ATTAINS Clean Water Act §303(d) impaired/threatened waters (Esri Living Atlas mirror) | flag — in or near a listed/impaired waterbody, with listed pollutant causes | | `transmission_grid` | HIFLD transmission lines + substations within the radius | opportunity (interconnection proximity) | | `ira_energy_community` | DOE/NETL IRA energy-community layers (coal closure + Fossil Fuel Employment MSA) | opportunity (10% ITC / +10% PTC bonus) | | `state_tank_spill_registry` | EPA UST Finder national baseline (registered UST facilities + LUST releases) **plus** state registries — NY DEC Spills (Socrata), CA SWRCB GeoTracker, TX TCEQ PST/LPST, FL DEP petroleum contamination — within the radius | flag on any currently **open** case; registered tank facilities are counted but informational | | `gas_pipeline_proximity` | US DOT NTAD Natural Gas Pipelines (sourced from EIA) — nearest pipeline segment and right-of-way encroachment band | flag when the nearest pipeline is inside the tight `<500ft` band | | `calfire_fhsz` | CAL FIRE Fire Hazard Severity Zone (SRA/LRA/pending/federal), California only | flag on a **Very High** FHSZ hit; outside California is an informational clear | Every layer returns `{ status: clear | flag | opportunity | unavailable, detail, metric fields, citation }`. A layer that errors upstream is marked `unavailable` — never silently reported as clear — and one bad layer or one bad coordinate never crashes the run. National wildfire data is fetched once per run and reused across all sites; the impaired-waters FeatureServer base URL (which Esri renames quarterly), the NY tank/spill geo capability, and the EPA UST Finder service name are also resolved once per run and reused. The CAL FIRE FHSZ layer resolves its layer-role IDs once per run too, and skips the network call entirely for any asset outside California. ### Example input ```json { "assets": [ { "lat": 29.7355, "lon": -95.2601, "label": "Houston Ship Channel industrial site, TX" }, { "lat": 44.29, "lon": -105.5, "label": "Gillette, WY greenfield (coal-country)" } ], "radiusMiles": 1 } ```` ### Key output fields (one scorecard row per site) - `fatal_flaw_count` — how many of the fifteen layers returned `flag`. Zero means nothing flagged; null if the coordinate was invalid. - `flags` — each flagged constraint as a readable sentence (contamination, flood, critical habitat, protected land, high seismic, active wildfire, karst/sinkhole susceptibility, landslide hazard, behind a levee, impaired waterbody nearby, an open tank/spill case, a gas pipeline inside the <500ft band, a Very High CAL FIRE FHSZ hit). - `opportunities` — positive findings (grid interconnection proximity, IRA energy-community bonus eligibility). - `unavailable_layers` — layers that could not be screened this run (upstream error/timeout), treated as not-screened rather than clear. - `layers` — the full per-layer object with each verdict, its metrics, and its citation. - `site_screen_summary` — one-line roll-up. - `radius_miles`, `disclaimer`, `checked_at`, `error`. ### How radius works `radiusMiles` (default 1; 1–25 in the Console editor, down to 0.25 via API) drives the distance-based layers: EPA, critical habitat, grid, the wildfire proximity flag, the landslide nearby-search, the impaired-waters proximity check, the state tank/spill registry, and the gas-pipeline proximity check. The point-in-polygon-only layers — protected lands, flood/NRI county, seismic, IRA energy-community, karst terrain, the USACE levee check, and the CAL FIRE FHSZ check — are exact intersect tests and ignore it. ### Who uses it - Site selectors and corporate real estate teams pre-screening a shortlist of parcels for deal-killers before ordering full studies. - Renewable-energy and infrastructure developers checking grid proximity and the IRA energy-community bonus alongside the full environmental/hazard constraint stack in one call. - Phase I ESA and environmental consultants scoping the assessment with a fast regulatory-records and sensitive-receptor read. - CRE lenders and insurers pulling flood, wildfire, seismic, karst, landslide, levee, contamination, tank/spill, pipeline, and CalFire wildfire-zone exposure on a collateral address. - AI agents turning a coordinate into a structured constraint profile. ### Use as an MCP tool A Pay-Per-Result API callable by AI agents through mcp.apify.com. The input is a coordinate list, so an agent can chain "geocode an address, screen the site, summarize the flaws" in one flow. ### FAQ **Is this a Phase I Environmental Site Assessment?** No. It is an informational multi-source pre-screen to scope and prioritize — not a substitute for an ASTM E1527 Phase I, a legal ESA or land determination, a flood certificate, a stamped engineering study, or tax advice. Confirm every flag with the authoritative agency and a licensed professional. **What isn't screened?** The EPA layer covers RCRA and TRI facilities via ECHO; Superfund/SEMS records without coordinates, the IRA brownfield category, and NWI wetlands are out of scope, so a clear result does not rule those out. (The standalone `epa-contaminated-site-screener` actor covers six EPA programs if you need deeper contamination detail.) The karst, landslide, levee, and impaired-waters layers are also compiled national datasets that can lag ground truth or draw boundaries conservatively/coarsely — a "clear" result on any layer does not rule out an undocumented local condition, and `nearest_distance_*` fields on the landslide and impaired-waters layers are straight-line proximity proxies, not drainage or engineering delineations. The **tank/spill registries** layer carries a **national EPA UST Finder baseline** (registered UST facilities + LUST releases anywhere in the US) plus deeper state spill/cleanup registries in **NY, CA, TX, and FL** — TX/FL records without coordinates are matched at county level, and outside those four states state-level spill cases beyond the EPA baseline are not screened; the **CAL FIRE FHSZ** layer covers **California only** (elsewhere it is an informational clear with no network call); and the **gas-pipeline proximity** layer flags only the tight `<500ft` right-of-way band — a pipeline farther away is informational only, not a fatal-flaw flag. **How many sites per run?** Up to `maxAssets` (default 250). One billable scorecard row per site. # Actor input Schema ## `assets` (type: `array`): List of sites to run the full fatal-flaw scorecard on. Each item is an object with numeric lat and lon (WGS84 decimal degrees) and an optional label. One billable scorecard row is returned per asset. Example: \[{"lat":29.7355,"lon":-95.2601,"label":"Houston Ship Channel parcel"}]. ## `radiusMiles` (type: `integer`): Search radius in statute miles for the proximity layers (EPA contamination, ESA critical habitat, transmission-grid, wildfire flag, landslide nearby-search, CWA §303(d) impaired-waters proximity, state tank/spill registry, and natural-gas pipeline proximity). Point-in-polygon-only layers (protected lands, flood/NRI county, seismic, IRA energy-community, karst terrain, USACE levee, CalFire FHSZ) ignore this. Smaller = a tighter on-site screen. Console accepts 1-25 (whole miles); sub-1-mile radii down to 0.25 are accepted via the API. ## `maxAssets` (type: `integer`): Maximum number of assets to screen from the list (safety cap). Extra assets beyond this are ignored. ## Actor input object example ```json { "assets": [ { "lat": 29.7355, "lon": -95.2601, "label": "Houston Ship Channel industrial site, TX" }, { "lat": 44.29, "lon": -105.5, "label": "Gillette, WY greenfield (coal-country)" } ], "radiusMiles": 1, "maxAssets": 250 } ``` # Actor output Schema ## `results` (type: `string`): The default dataset. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "assets": [ { "lat": 29.7355, "lon": -95.2601, "label": "Houston Ship Channel industrial site, TX" }, { "lat": 44.29, "lon": -105.5, "label": "Gillette, WY greenfield (coal-country)" } ], "radiusMiles": 1 }; // Run the Actor and wait for it to finish const run = await client.actor("malonestar/site-due-diligence-bundle").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "assets": [ { "lat": 29.7355, "lon": -95.2601, "label": "Houston Ship Channel industrial site, TX", }, { "lat": 44.29, "lon": -105.5, "label": "Gillette, WY greenfield (coal-country)", }, ], "radiusMiles": 1, } # Run the Actor and wait for it to finish run = client.actor("malonestar/site-due-diligence-bundle").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "assets": [ { "lat": 29.7355, "lon": -95.2601, "label": "Houston Ship Channel industrial site, TX" }, { "lat": 44.29, "lon": -105.5, "label": "Gillette, WY greenfield (coal-country)" } ], "radiusMiles": 1 }' | apify call malonestar/site-due-diligence-bundle --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=malonestar/site-due-diligence-bundle", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Site Due-Diligence Bundle — One-Call Fatal-Flaw Scorecard", "description": "One call (lat/lon + radius) returns a Phase-I fatal-flaw site scorecard across 15 layers: EPA contamination, flood, ESA habitat, protected lands, seismic, wildfire, karst, landslide, levee, impaired waters, grid, IRA energy community, tank/spill registries, gas pipelines, CalFire FHSZ.", "version": "1.0", "x-build-id": "z06ZA6lCSCHhdZ7Ju" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/malonestar~site-due-diligence-bundle/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-malonestar-site-due-diligence-bundle", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/malonestar~site-due-diligence-bundle/runs": { "post": { "operationId": "runs-sync-malonestar-site-due-diligence-bundle", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/malonestar~site-due-diligence-bundle/run-sync": { "post": { "operationId": "run-sync-malonestar-site-due-diligence-bundle", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "assets": { "title": "Sites to screen (coordinates)", "type": "array", "description": "List of sites to run the full fatal-flaw scorecard on. Each item is an object with numeric lat and lon (WGS84 decimal degrees) and an optional label. One billable scorecard row is returned per asset. Example: [{\"lat\":29.7355,\"lon\":-95.2601,\"label\":\"Houston Ship Channel parcel\"}]." }, "radiusMiles": { "title": "Proximity radius (miles)", "minimum": 1, "maximum": 25, "type": "integer", "description": "Search radius in statute miles for the proximity layers (EPA contamination, ESA critical habitat, transmission-grid, wildfire flag, landslide nearby-search, CWA §303(d) impaired-waters proximity, state tank/spill registry, and natural-gas pipeline proximity). Point-in-polygon-only layers (protected lands, flood/NRI county, seismic, IRA energy-community, karst terrain, USACE levee, CalFire FHSZ) ignore this. Smaller = a tighter on-site screen. Console accepts 1-25 (whole miles); sub-1-mile radii down to 0.25 are accepted via the API.", "default": 1 }, "maxAssets": { "title": "Max assets", "minimum": 1, "maximum": 1000, "type": "integer", "description": "Maximum number of assets to screen from the list (safety cap). Extra assets beyond this are ignored.", "default": 250 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```