# Earthquake Data Scraper — USGS Events (`ponderable_hydrometer/earthquakes-scraper`) Actor

Fetch earthquake events from USGS — magnitude, place, coordinates, depth, tsunami & alert. Filter by time, magnitude, bbox or radius. Free keyless API.

- **URL**: https://apify.com/ponderable\_hydrometer/earthquakes-scraper.md
- **Developed by:** [Ponderable Hydrometer](https://apify.com/ponderable_hydrometer) (community)
- **Categories:** Developer tools, Automation, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 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/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

## Earthquake Data Scraper — USGS Events

**Fetch earthquake events from the USGS FDSN catalogue with the full filter surface** — magnitude, location, coordinates, depth, tsunami flag, PAGER alert level, felt reports and significance. Filter by time window, magnitude range, bounding box, or radius around a point. Free keyless official government API.

For risk/insurance analytics, news feeds, seismic research and mapping apps. Schedule it for a live seismic alert feed.

### What you get

Per event:

- **Magnitude** — `magnitude`, `magType`
- **Location** — `place`, `longitude`, `latitude`, `depthKm`
- **Timing** — `time`, `updated` (ISO 8601)
- **Impact** — `tsunami` flag, `alert` (PAGER green/yellow/orange/red), `significance`, `felt`, `cdi`, `mmi`
- **Meta** — `id`, `status`, `type`, `title`, `url`, `detailUrl`

### Output sample

```json
{
  "id": "us7000abcd",
  "magnitude": 6.2,
  "magType": "mww",
  "place": "125 km SW of Tokyo, Japan",
  "time": "2026-07-11T22:14:03.000Z",
  "updated": "2026-07-11T23:02:41.000Z",
  "longitude": 139.7,
  "latitude": 35.4,
  "depthKm": 32.5,
  "tsunami": 0,
  "alert": "green",
  "significance": 592,
  "felt": 1204,
  "cdi": 5.2,
  "mmi": 6.1,
  "status": "reviewed",
  "type": "earthquake",
  "title": "M 6.2 - 125 km SW of Tokyo, Japan",
  "url": "https://earthquake.usgs.gov/earthquakes/eventpage/us7000abcd",
  "detailUrl": "https://earthquake.usgs.gov/.../us7000abcd.geojson"
}
```

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `starttime` / `endtime` | string | — | Event time range (ISO or `YYYY-MM-DD`) |
| `minmagnitude` / `maxmagnitude` | string | — | Magnitude range, e.g. `4.5` |
| `minlatitude` / `maxlatitude` / `minlongitude` / `maxlongitude` | string | — | Bounding-box search |
| `latitude` / `longitude` / `maxradiuskm` | string | — | Circle search around a point |
| `mindepth` / `maxdepth` | string | — | Depth range (km) |
| `alertlevel` | string | — | PAGER alert: `green`, `yellow`, `orange`, `red` |
| `orderby` | string | `time` | `time`, `time-asc`, `magnitude`, `magnitude-asc` |
| `maxResults` | integer | `1000` | Cap on events returned |

### Example input

```json
{
  "starttime": "2026-07-01",
  "minmagnitude": "4.5",
  "orderby": "time",
  "maxResults": 500
}
```

Region (California bbox): `{"minlatitude":"32","maxlatitude":"42","minlongitude":"-125","maxlongitude":"-114","minmagnitude":"2.5"}`. Around a point (200km): `{"latitude":"35.7","longitude":"139.7","maxradiuskm":"200","minmagnitude":"3"}`.

### Why this actor

- **Full filter surface** — time, magnitude, bbox, radius, depth and PAGER alert, all in one actor.
- **Clean normalized schema** — ISO timestamps and split lat/lon/depth from the raw GeoJSON, ready for spreadsheets and maps.
- **Official & keyless** — the USGS FDSN government API; no key, reliable, schedulable as an alert feed.

### Pricing

Pay per result — **$1.00 per 1,000 results** (one result = one earthquake event). No subscription; you pay only for what you get.

### Notes & limits

- Source is the USGS FDSN event API — free public government data. Impact fields (`felt`, `cdi`, `mmi`, `alert`) are populated only for events with those reports.
- Public data; you are responsible for compliant use. Not affiliated with USGS.

### Related actors

- **NOAA Tides & Currents Scraper** — tide and current predictions.
- **USGS Water Data Scraper** — streamflow, gage height and water temperature.
- **Open-Meteo Weather Scraper** — geocoding + forecast.

# Actor input Schema

## `starttime` (type: `string`):

Earliest event time, ISO or YYYY-MM-DD, e.g. "2026-07-01". Default: USGS default (~30 days ago).

## `endtime` (type: `string`):

Latest event time, ISO or YYYY-MM-DD, e.g. "2026-07-12".

## `minmagnitude` (type: `string`):

Minimum magnitude, e.g. "4.5".

## `maxmagnitude` (type: `string`):

Maximum magnitude.

## `minlatitude` (type: `string`):

Bounding box south edge, e.g. "32".

## `maxlatitude` (type: `string`):

Bounding box north edge, e.g. "42".

## `minlongitude` (type: `string`):

Bounding box west edge, e.g. "-125".

## `maxlongitude` (type: `string`):

Bounding box east edge, e.g. "-114".

## `latitude` (type: `string`):

Circle search center latitude (use with radius).

## `longitude` (type: `string`):

Circle search center longitude (use with radius).

## `maxradiuskm` (type: `string`):

Circle search radius in km around center.

## `mindepth` (type: `string`):

Minimum depth in km.

## `maxdepth` (type: `string`):

Maximum depth in km.

## `alertlevel` (type: `string`):

Filter by USGS PAGER alert: green, yellow, orange or red.

## `orderby` (type: `string`):

Sort order.

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

Cap on number of events returned.

## Actor input object example

```json
{
  "starttime": "2026-07-01",
  "minmagnitude": "4.5",
  "alertlevel": "",
  "orderby": "time",
  "maxResults": 1000
}
```

# 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 = {
    "starttime": "2026-07-01",
    "minmagnitude": "4.5"
};

// Run the Actor and wait for it to finish
const run = await client.actor("ponderable_hydrometer/earthquakes-scraper").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 = {
    "starttime": "2026-07-01",
    "minmagnitude": "4.5",
}

# Run the Actor and wait for it to finish
run = client.actor("ponderable_hydrometer/earthquakes-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "starttime": "2026-07-01",
  "minmagnitude": "4.5"
}' |
apify call ponderable_hydrometer/earthquakes-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=ponderable_hydrometer/earthquakes-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xaUsayJmOwPaNcZgS/builds/6jOcjBJjtdLe5oJFB/openapi.json