# Natural Hazard Event Records — NASA EONET (`nexgensignal/natural-hazard-event-records`) Actor

Keyless, pay-per-record NASA EONET natural-event tracker — one row per event with category, open/closed status, date range, latest location and magnitude, and the reporting source. Public-domain NASA data; not for safety-of-life use; no person data.

- **URL**: https://apify.com/nexgensignal/natural-hazard-event-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, News, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 event records

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 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

## Natural Hazard Event Records — NASA EONET

**Keyless. Pay per record. Global natural-event tracking from NASA.**

This actor turns **NASA's Earth Observatory Natural Event Tracker (EONET)** into clean, per-event records — a structured feed of the world's ongoing and historical natural hazards. Each run reads NASA's keyless public EONET API and delivers one row per event: the title and category, whether it is open or closed, the first and last observation dates, the latest position, the reported magnitude, and the primary source that reported it. Event grain, structured for engineering use, in the public domain, with NASA's own fitness disclaimer on every record.

### What this is, in one paragraph

EONET is NASA's curated catalogue of natural events — wildfires, severe storms, volcanoes, floods, sea and lake ice, dust and haze, landslides, drought, and more — assembled from many authoritative sources into one consistent metadata layer. This actor reads EONET's events API category by category, de-duplicates events that appear under more than one category, and flattens each event into a single analysis-ready record: identity, category, status, the date range it has been tracked over, its most recent location and magnitude, and the source agency behind it. Values are exactly as served by NASA's public API. You are billed only for records actually delivered.

### Who buys this and for what job

- **Insurance, reinsurance, and catastrophe modellers** building a structured event log of global natural hazards for exposure and loss analysis.
- **Climate, environmental, and disaster researchers** studying the frequency, distribution, and duration of natural events across categories and years.
- **Data engineers and app builders** who want a clean, keyed event feed for dashboards and maps without writing an EONET client.
- **Supply-chain, logistics, and risk teams** watching open events — active storms, wildfires, volcanic activity — near assets and routes.

### Public-domain data — with NASA's fitness caveat

Two honesty riders travel on every record. First, **licensing**: NASA content, including EONET's curated event metadata, is generally **not subject to copyright in the United States** and is free to reuse — acknowledge NASA as the source. Second, **fitness**: EONET's own disclaimer states its metadata is intended for **visualization and general information only** and should not be construed as "official" with regard to spatial or temporal extent — event footprints and timings are drawn from multiple sources and are often approximations. This is not a feed for emergency, navigational, or safety-of-life decisions; verify against the cited primary source before acting.

### Event grain — no person data

This actor works at event grain: hazards, categories, dates, locations, and magnitudes. There are no natural-person fields in EONET event metadata, and this actor emits none, with a person-key guard on every record as a backstop.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `event_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `category` | string | — | Optional EONET category id (e.g. wildfires, severeStorms, volcanoes, floods, seaLakeIce). Blank for all. |
| `status` | string | all | `all`, `open` (ongoing), or `closed` (ended). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per event. Real example (values as served by NASA):

```json
{
  "record_id": "EONET_22926",
  "event_id": "EONET_22926",
  "title": "Tropical Storm Saudel",
  "category_id": "severeStorms",
  "category_title": "Severe Storms",
  "categories": "Severe Storms",
  "status": "open",
  "date_first": "2026-08-19T00:00:00Z",
  "date_last": "2026-08-20T18:00:00Z",
  "observation_count": 8,
  "latest_date": "2026-08-20T18:00:00Z",
  "latest_latitude": 13.7,
  "latest_longitude": 149.6,
  "latest_geometry_type": "Point",
  "magnitude_value": 40.0,
  "magnitude_unit": "kts",
  "source_ids": "JTWC",
  "source_urls": "https://www.metoc.navy.mil/jtwc/products/wp1726.tcw",
  "event_link": "https://eonet.gsfc.nasa.gov/api/v3/events/EONET_22926",
  "source": "NASA EONET (Earth Observatory Natural Event Tracker)",
  "licence": "NASA EONET ... NASA content is generally not subject to copyright ... acknowledge NASA as the source.",
  "disclaimer": "EONET metadata is intended for visualization and general information only ... not 'official' ...",
  "observed_at": "2026-08-21T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the category and status, unique events seen and delivered, whether charged equals delivered, and the public-domain / not-official notice.

### Field reference

Each record is one event. Identity: `record_id` / `event_id`, `title`, `description`, and the event link `event_link`. Classification: `category_id`, `category_title`, and `categories` (all category titles, comma-joined for cross-listed events). State: `status` (open/closed) and `closed_at`. Timing and track: `date_first`, `date_last`, `observation_count`, and `latest_date`. Location and size of the most recent observation: `latest_latitude`, `latest_longitude`, `latest_geometry_type`, `magnitude_value`, and `magnitude_unit`. Provenance and caveats: `source_ids`, `source_urls`, `source`, `source_url`, `licence`, `attribution`, `disclaimer`, and `observed_at`.

### How a run works

A run first re-reads the source host's robots posture from your runtime — EONET's host serves a permissive robots file — and stops at the door if that ever changes. It then reads EONET's events endpoint one category at a time (the combined all-category call is heavy and can transiently error; per-category reads are lighter and retried with backoff), de-duplicates any event listed under more than one category, and flattens each event to a single record: identity, classification, status, date range, latest position, and magnitude. Each record is delivered **before** it is charged, so a blocked or empty run costs you nothing. Your optional `category` and `status` filters bound the pull, and the actor stops at your `maxRecords` ceiling and records `charge_equals_delivered` in the receipt.

### Categories you can pull

EONET organizes events into a stable set of categories, and this actor surfaces the category on every row so a mixed pull stays self-describing. The categories span the natural-hazard spectrum: **Wildfires** (by far the largest category), **Severe Storms** (tropical cyclones and major storms, often with wind-speed magnitudes), **Volcanoes**, **Floods**, **Sea and Lake Ice** (including tracked icebergs), **Drought**, **Dust and Haze**, **Landslides**, **Earthquakes**, **Snow**, **Temperature Extremes**, **Water Color**, and **Manmade** events. Pass a single `category` to build a focused feed — say, only severe storms with their magnitudes — or pull across all categories and group by `category_title` downstream. Paired with `status`, you can narrow to just open events (a live hazard monitor) or just closed ones (a historical archive), which is the difference between an operational feed and a research dataset.

### Cost guidance

One `event_record` per delivered event: cost = events delivered × your plan's per-record price. EONET tracks tens of thousands of events across its full history, dominated by wildfires and severe storms, so scope with `category` and `status` to keep runs bounded — a single category's open events is typically a few dozen to a few hundred. 1,000 events is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **Not official.** EONET metadata is for visualization and general information; spatial and temporal extents are approximations, not authoritative determinations.
- **Not for safety-of-life use.** Do not use this feed for emergency, navigational, or evacuation decisions — consult the cited primary source and official warnings.
- **Event grain, latest observation.** Each record summarizes one event and carries its most recent position and magnitude, plus the tracked date range — not the full geometry track.
- **As served.** Values are exactly as NASA distributes them; this actor reformats, it does not recompute.
- **No person data** is emitted.

### Differentiation

This actor is the **natural-event catalogue** angle — global hazards as clean, category-keyed event records from NASA EONET, spanning wildfires, storms, volcanoes, floods, and more. It is distinct from any single-hazard or single-agency feed: EONET's value is the unified, cross-source event layer with a consistent schema, so one pull covers every category at once. The record names its underlying `source_ids` and `source_urls` so a buyer who needs the authoritative primary feed for a given event can follow through to it.

### The NexGen Signal family

Part of the NexGen Signal family of pay-per-record data products:

- [Air Quality Monitor Records — US EPA AQS](https://apify.com/nexgensignal/air-quality-monitor-records)
- [EPA Facility Compliance Records — Envirofacts](https://apify.com/nexgensignal/epa-facility-compliance-records)
- [National Macro Indicator Records — World Bank](https://apify.com/nexgensignal/national-macro-indicator-records)
- [US Treasury Fiscal Records — Rates & Debt](https://apify.com/nexgensignal/treasury-fiscal-records)
- [Federal Rulemaking Records — US Federal Register](https://apify.com/nexgensignal/federal-rulemaking-records)

*Source: NASA EONET (Earth Observatory Natural Event Tracker) public API. NASA content is generally not subject to copyright in the United States and is free to reuse with acknowledgement of NASA. EONET metadata is for visualization and general information only and is not "official" for spatial or temporal extent; not for emergency or safety-of-life use. Reformatted to event records; no person data emitted.*

# Actor input Schema

## `category` (type: `string`):

Optional EONET category id to restrict to, e.g. wildfires, severeStorms, volcanoes, floods, seaLakeIce, drought, earthquakes, landslides. Leave blank for all categories.

## `status` (type: `string`):

Which events to include: all (default), open (ongoing), or closed (ended).

## `maxRecords` (type: `integer`):

Maximum records delivered and billed. You are billed only for records delivered.

## Actor input object example

```json
{
  "status": "all",
  "maxRecords": 500
}
```

# Actor output Schema

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

The delivered NASA EONET natural-hazard event records.

# 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 = {
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/natural-hazard-event-records").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 = { "maxRecords": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/natural-hazard-event-records").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 '{
  "maxRecords": 500
}' |
apify call nexgensignal/natural-hazard-event-records --silent --output-dataset

```

## MCP server setup

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

```

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/7c7URv94gDhyKdldo/builds/pW7qS7mVMWlEp2zv2/openapi.json