# USGS Global Earthquake and Seismic Activity Radar (`adaptive_nightmare/usgs-earthquake-radar`) Actor

Track real-time global seismic events, earthquake magnitudes, hypocenter depth, epicenter coordinates, tsunami alerts, and felt reports from the US Geological Survey.

- **URL**: https://apify.com/adaptive_nightmare/usgs-earthquake-radar.md
- **Developed by:** [Darim Quraishi](https://apify.com/adaptive_nightmare) (community)
- **Categories:** News, Education, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.15 / 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.

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

## USGS Global Earthquake and Seismic Activity Radar

Extract real-time global earthquake events, hypocenter depths, epicenter coordinates, and tsunami indicators from the United States Geological Survey (USGS).

### Features

- Collects seismic events across all global fault zones with magnitude, depth, and exact geographic coordinates.
- Captures community felt reports, Modified Mercalli Intensity (MMI), and Community Decimal Intensity (CDI) measurements.
- Tracks USGS PAGER alert color classifications and active tsunami warning flags.
- Connects directly to official USGS event pages and generates Google Maps coordinate references.
- Operates via official USGS GeoJSON endpoints with zero API keys and zero proxy requirements.
- Delivers structured records suitable for export to JSON, CSV, Excel, or automated emergency alerting pipelines.

### Input parameters

- Minimum Magnitude: Minimum earthquake strength on the Richter or moment magnitude scale. Default is 2.5.
- Time Window: Search interval covering the past hour, past 24 hours, past 7 days, or past 30 days. Default is past 24 hours.
- Alert Level Filter: Filter by PAGER economic alert color (green, yellow, orange, red, or all). Default is all.
- Maximum Events: Maximum number of earthquake records to collect, up to 200. Default is 50.

### Output dataset fields

Each dataset record contains:

- id: Unique USGS earthquake identifier (for example: us7000m9vx).
- place: Descriptive geographical location and distance from nearby populated settlements.
- magnitude: Numerical earthquake strength.
- magnitudeType: Primary measurement formula used (such as ml, mw, or md).
- time: ISO formatted timestamp when the seismic rupture occurred.
- updated: ISO formatted timestamp when USGS reviewed or revised the telemetry.
- latitude: Geographic latitude coordinate.
- longitude: Geographic longitude coordinate.
- depthKm: Hypocenter depth below Earth's surface measured in kilometers.
- tsunamiWarning: Boolean indicating whether a potential tsunami event was flagged.
- significance: Numerical score from 0 to 1000 describing overall event impact.
- feltReports: Number of citizen reports submitted to the USGS Did You Feel It portal.
- alertLevel: Impact classification color (green, yellow, orange, red).
- eventUrl: Direct link to the complete USGS technical overview.
- googleMapsUrl: Direct link to view the epicenter on Google Maps.
- scrapedAt: UTC timestamp when the data was extracted.

### Use cases

- Disaster risk modeling: Feed real-time tremor events into property insurance risk evaluation engines.
- Logistics monitoring: Detect disruptions across maritime shipping lanes, mountain passes, and railway corridors.
- Academic geophysics: Compile regional seismicity catalogs for fault slip rate research.
- Emergency alerts: Trigger automatic notifications when major shocks exceed regional safety thresholds.

# Actor input Schema

## `minMagnitude` (type: `number`):

Minimum earthquake magnitude on the Richter / moment magnitude scale (for example: 2.5 for noticeable shakes, 4.5 for moderate tremors).

## `timeframe` (type: `string`):

Historical search timeframe from the current moment.

## `alertLevel` (type: `string`):

Filter events by USGS PAGER economic and casualty impact color alert.

## `maxEvents` (type: `integer`):

Maximum number of seismic records to retrieve.

## Actor input object example

```json
{
  "minMagnitude": 2.5,
  "timeframe": "past_day",
  "alertLevel": "all",
  "maxEvents": 50
}
```

# Actor output Schema

## `results` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("adaptive_nightmare/usgs-earthquake-radar").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("adaptive_nightmare/usgs-earthquake-radar").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 '{}' |
apify call adaptive_nightmare/usgs-earthquake-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,adaptive_nightmare/usgs-earthquake-radar"
        }
    }
}
```

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/TzuNMRPMm0m4CeEFc/builds/1HQbeoNgUlHamrmIv/openapi.json