# Storm Damage Lead Finder (`hereditary_model/storm-lead-finder`) Actor

Finds active severe weather alerts by state from the National Weather Service, scored for roofing and restoration lead potential by hail size, wind speed, and severity.

- **URL**: https://apify.com/hereditary\_model/storm-lead-finder.md
- **Developed by:** [Aaron Marxsen](https://apify.com/hereditary_model) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 alert returneds

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?

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

## Storm Damage Lead Finder

The window between "a storm just hit" and "every roofer in three states is knocking on the same doors" is short. This pulls active severe weather alerts straight from the National Weather Service and scores them for canvassing potential — hail size and wind speed are the two numbers that actually predict roof and property damage claims.

### What it does

1. Fetches every active NWS alert for each state you give it.
2. Drops anything below your minimum severity **before** billing.
3. Pulls hail size and wind gust out of the alert's structured parameters when NWS reports them.
4. Scores every alert 0–100: severity level, hail size, wind speed, and a bump for the event types that correlate hardest with property damage (tornado, hurricane, severe thunderstorm).
5. Sorts highest-score first, so the storm worth driving to today is at the top.

### Output

| Field | Notes |
| --- | --- |
| `event`, `severity`, `certainty`, `urgency` | What NWS is warning about, and how confident they are |
| `areaDesc`, `headline`, `description` | Where, and the human-readable detail |
| `maxHailSize`, `maxWindGust` | The two damage-potential numbers, when NWS reports them |
| `effective`, `expires` | The active window |
| `leadScore` | 0–100, canvassing potential |

### Input

Only `states` is required.

```json
{
  "states": ["FL", "TX", "OK"],
  "minSeverity": "Moderate"
}
```

Run it on a schedule across the states you cover, and you've got a same-day feed of where to send crews.

### Pricing

Pay per event. You're billed per alert returned and once per state digested. Data source: National Weather Service (api.weather.gov), no API key required.

# Actor input Schema

## `states` (type: `array`):

Two-letter US state codes to check, one per line, for example FL or TX.

## `minSeverity` (type: `string`):

Drop alerts below this severity level, before billing.

## `maxResultsPerState` (type: `integer`):

Caps how many alerts are returned per state, highest lead score first.

## Actor input object example

```json
{
  "states": [
    "FL"
  ],
  "minSeverity": "Moderate",
  "maxResultsPerState": 50
}
```

# Actor output Schema

## `alerts` (type: `string`):

No description

## `summary` (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 = {
    "states": [
        "FL"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hereditary_model/storm-lead-finder").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 = { "states": ["FL"] }

# Run the Actor and wait for it to finish
run = client.actor("hereditary_model/storm-lead-finder").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 '{
  "states": [
    "FL"
  ]
}' |
apify call hereditary_model/storm-lead-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hereditary_model/storm-lead-finder"
        }
    }
}

```

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/aLR7sdceqhP7ZLfae/builds/Anj4AYYAKInhGJBPY/openapi.json