# Natural Hazard Alerts - USGS + NWS + GDACS (`calculating_kitchen_h0b/natural-hazard-alerts`) Actor

Unified natural hazard feed: USGS earthquakes, US National Weather Service alerts and GDACS global disasters (cyclones, floods, volcanoes, wildfires). Filter by location radius, state, magnitude.

- **URL**: https://apify.com/calculating_kitchen_h0b/natural-hazard-alerts.md
- **Developed by:** [Andres Barcelo](https://apify.com/calculating_kitchen_h0b) (community)
- **Categories:** Business, Automation, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.50 / 1,000 hazard events

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

## Natural Hazard Alerts - Earthquakes, Weather, Floods & Cyclones (USGS + NWS + GDACS)

One run, one normalized feed of **natural hazard events from three official sources**:

- **USGS** - global earthquakes (magnitude, depth, PAGER alert level, tsunami flag)
- **US National Weather Service** - all active weather alerts (hurricanes, tornadoes, floods, heat, fire weather, winter storms...)
- **GDACS (UN/EC Global Disaster Alert and Coordination System)** - global earthquakes, tropical cyclones, floods, volcanoes, droughts, wildfires with Green/Orange/Red alert levels

Filter by distance from any point (lat/lon + radius), US state, lookback window and minimum quake magnitude. Every event gets the same fields, sorted newest first.

### Use cases

- Supply-chain, logistics and insurance risk monitoring around facilities or ports (schedule hourly + webhook/Slack)
- Travel & event safety, NGO/humanitarian dashboards
- Real-estate, utilities and field-service operations
- Feed AI agents with current hazard context

### Input

```json
{"sources":["usgs","nws","gdacs"],"lookbackDays":3,"minMagnitude":"4.5","latitude":34.05,"longitude":-118.24,"radiusKm":500}
```

### Output

```json
{"source":"USGS","hazardType":"earthquake","severity":"GREEN","magnitude":5.1,"time":"2026-10-14T08:12:00Z","area":"10 km SW of ...",
 "latitude":35.1,"longitude":-117.9,"depthKm":8.2,"tsunami":false,"distanceKm":123.4,"url":"https://earthquake.usgs.gov/..."}
```

### Pricing

Pay per result - charged per hazard event returned.

Data: USGS and NWS (US public domain), GDACS (public). Not affiliated with these agencies. Not for life-safety decisions; always follow official warnings.

# Actor input Schema

## `sources` (type: `array`):

usgs = global earthquakes, nws = active US weather alerts, gdacs = global disasters (earthquakes, cyclones, floods, volcanoes, droughts, wildfires).

## `lookbackDays` (type: `integer`):

For USGS and GDACS events. NWS returns currently active alerts.

## `minMagnitude` (type: `string`):

USGS earthquakes only.

## `latitude` (type: `number`):

Center point for distance filter, e.g. 34.05.

## `longitude` (type: `number`):

Center point, e.g. -118.24.

## `radiusKm` (type: `integer`):

Only events within this distance of the point.

## `usState` (type: `string`):

Two-letter code, e.g. FL. Overrides point for NWS.

## `maxResults` (type: `integer`):

Cap.

## Actor input object example

```json
{
  "sources": [
    "usgs",
    "nws",
    "gdacs"
  ],
  "lookbackDays": 3,
  "minMagnitude": "4.5",
  "maxResults": 500
}
```

# Actor output Schema

## `results` (type: `string`):

Unified hazard events.

# 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 = {
    "sources": [
        "usgs",
        "nws",
        "gdacs"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("calculating_kitchen_h0b/natural-hazard-alerts").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 = { "sources": [
        "usgs",
        "nws",
        "gdacs",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("calculating_kitchen_h0b/natural-hazard-alerts").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 '{
  "sources": [
    "usgs",
    "nws",
    "gdacs"
  ]
}' |
apify call calculating_kitchen_h0b/natural-hazard-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,calculating_kitchen_h0b/natural-hazard-alerts"
        }
    }
}
```

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/Vvc3TLDM2DbDCi5HU/builds/bdQ4Qd7ydA8LVaRjw/openapi.json