# Storm History by Address, Reported Events Since 2003 (`truefixr_atlasunited/storm-history-by-address`) Actor

Send street addresses, get every reported and radar-detected storm event within your radius back to 2003, by peril: date, type, magnitude, distance. Planned $0.05 per event line, $10 minimum per report. Reported events, not a damage assessment; supports date-of-loss review, not proof of damage.

- **URL**: https://apify.com/truefixr_atlasunited/storm-history-by-address.md
- **Developed by:** [Valentin Yslas](https://apify.com/truefixr_atlasunited) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 history event lines

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

## Storm History by Address, Reported Events Since 2003

**You send full US street addresses; you get every reported and radar-detected storm event within your radius, back to 2003, by peril, with date, type, magnitude and distance, one flat row per event line.** Each report covers 11 reported-event categories (hail, wind, flood and heavy rain, lightning, tornado, hurricane, winter storm, extreme heat and cold, drought, wildfire, coastal). For hail, wind and winter storm each report applies a significant-event threshold as defined by the API (for example 0.75 inch hail, 50 mph wind, 6 inch winter storm) and every row carries the matching flag. Every report carries a `reference_id`, so any row can be reproduced and cited.

**Cost:** pricing is not enabled yet. The planned rate is $0.05 per event line with a $10 minimum per report, so a single report costs at least $10. A free preview logs the real line count and estimated cost first, and the run refuses to pull any report whose estimate exceeds `maxChargeUsd`.

This is a record of reported and radar-detected events, not a damage assessment. It supports date-of-loss review, not proof of damage.

### Input

```json
{ "addresses": ["891 Lake Hollow Blvd SW, Marietta, GA 30064"], "radiusMiles": 1, "dateOfLoss": "", "maxChargeUsd": 10 }
```

- `addresses` (required): full street addresses, one report each.
- `radiusMiles`: 1 to 25, default 5. A larger radius returns more lines.
- `dateOfLoss`: optional `YYYY-MM-DD`; anchors the report around that date (events near the address on the date, plus events just before and after). Weather data only.
- `maxChargeUsd`: optional spend cap checked against the preview before each report. The API returns the full report with every peril together, so there is no peril filter.

### Output

One row per event line.

| Field | Meaning |
|---|---|
| `address`, `geocoded_address`, `lat`, `lon` | The address you sent, the matched address, and its coordinates |
| `radius_mi`, `date_of_loss`, `report_period` | Search radius, date anchor if given, report period (2003-01-01 to present) |
| `reference_id` | Report identifier for citation and reproducibility |
| `peril` | Event category |
| `event_date` | Date of the reported event |
| `magnitude`, `magnitude_value`, `magnitude_unit` | Reported size or speed (for example 1.50 in, 70.00 mph) or "Count Only" when none was reported |
| `significant`, `significant_threshold` | Whether the magnitude meets the significant-event definition, and that definition |
| `method`, `distance_mi`, `county` | Measurement method, distance from the address, county |

### Example row

```json
{ "address": "1600 Pennsylvania Ave NW, Washington, DC", "radius_mi": 1, "reference_id": "TFX-202610-9983FBC2",
  "report_period": "2003-01-01 to present", "peril": "Wind", "event_date": "2026-07-21",
  "magnitude": "39.00 mph", "significant": false, "distance_mi": 0.24 }
```

### Interpretation

A row means an event was reported or radar-detected within the radius on that date. Lines are not de-duplicated across reports of the same event, so one storm can produce several rows. Rows are weather records, not damage findings, insurance determinations or claims of loss.

### Compliance

This is data, not insurance, legal or safety advice, and no guarantee of results is made. Not affiliated with NOAA or the National Weather Service.

# Actor input Schema

## `addresses` (type: `array`):

Full US street addresses, for example '891 Lake Hollow Blvd SW, Marietta, GA 30064'. Each address is one report.

## `radiusMiles` (type: `integer`):

Radius around each address, 1 to 25 miles. A larger radius returns more event lines.

## `dateOfLoss` (type: `string`):

Optional date, YYYY-MM-DD, to anchor each report around one date: events reported or radar-detected near the address on that date, plus events immediately before and after. Weather data only; it does not confirm a claim or any damage.

## `maxChargeUsd` (type: `number`):

A report is pulled only if its previewed cost fits within the remaining budget. The planned rate is $0.05 per event line with a $10 minimum per report, so a single report costs at least $10. Leave empty to rely on your Apify run budget.

## Actor input object example

```json
{
  "addresses": [
    "1600 Pennsylvania Ave NW, Washington, DC"
  ],
  "radiusMiles": 5
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `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 = {
    "addresses": [
        "1600 Pennsylvania Ave NW, Washington, DC"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("truefixr_atlasunited/storm-history-by-address").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 = { "addresses": ["1600 Pennsylvania Ave NW, Washington, DC"] }

# Run the Actor and wait for it to finish
run = client.actor("truefixr_atlasunited/storm-history-by-address").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 '{
  "addresses": [
    "1600 Pennsylvania Ave NW, Washington, DC"
  ]
}' |
apify call truefixr_atlasunited/storm-history-by-address --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,truefixr_atlasunited/storm-history-by-address"
        }
    }
}
```

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/Y0MjYaqG9dUJEgK9w/builds/dcALB3whVTTaXgjpB/openapi.json