# Earthquake Business Impact Monitor — USGS, By Location (`alaudinburki/earthquake-monitor`) Actor

Recent earthquakes near your specific business locations (lat/lon), not a global feed. USGS's own magnitude, PAGER alert level, and tsunami flag passed through directly. Free, keyless, real-time.

- **URL**: https://apify.com/alaudinburki/earthquake-monitor.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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/actors/running/actors-in-store.md#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 Business Impact Monitor — USGS, By Location

The seismic companion to the Severe Weather Business Impact Monitor (#72)
and Federal Disaster Declaration Monitor (#75): recent earthquakes near
your specific business locations, not a global feed. Free, public,
keyless, real-time via USGS's official event API.

### Input

```json
{
  "locations": [{ "label": "Tokyo Office", "lat": 35.68, "lon": 139.69 }],
  "minMagnitude": 4.5,
  "maxRadiusKm": 300
}
```

### Sample output

```json
{
  "locationLabel": "Tokyo Office",
  "place": "16 km ENE of Hasaki, Japan",
  "magnitude": 4.7,
  "time": "2026-08-29T15:17:06.003Z",
  "depthKm": 45.2,
  "alertLevel": null,
  "tsunami": false
}
```

### Typical uses

- **International operations risk** — check facilities, offices, or
  supply-chain nodes in seismically active regions.
- **Insurance / reinsurance exposure** — track seismic activity across a
  portfolio of insured locations.
- **Logistics / manufacturing continuity** — flag disruption risk near
  ports, plants, or warehouses.

### Pricing

**$0.002 per matched earthquake.**

### ⚠️ Read before you act

- **This is a real-time snapshot of RECENT events**, not a live push
  feed — re-run periodically (a schedule works well) rather than treating
  one run as an ongoing watch.
- **`alertLevel` (USGS's PAGER estimate) is null for most earthquakes** —
  it's only assigned to events USGS considers significant enough to
  assess impact for. A null alert doesn't mean "safe," just "not assessed."
- **Radius search is a straight-line distance from your coordinates**, not
  a business-relevant boundary — adjust `maxRadiusKm` to match what
  actually matters for your use case.

### FAQ

- **Do I need an API key?** No — USGS's earthquake API is free and keyless.
- **What does `significance` mean?** USGS's own composite score
  (magnitude, felt reports, and other factors) — higher means more
  newsworthy/impactful, independent of raw magnitude.
- **Can I search without a location, just globally?** Not with this
  actor — it's built for "near my specific locations," which is the
  business-relevant question. Omit `maxRadiusKm`'s narrow default (raise
  it) for broader regional coverage instead.

### Related actors

- **Severe Weather Business Impact Monitor** — the same by-location
  pattern, for active NWS weather alerts.
- **Federal Disaster Declaration Monitor** — the official, after-the-fact
  federal determination that follows a major event like this.

# Actor input Schema

## `locations` (type: `array`):

Business locations to check, each with a lat/lon and an optional label. Example: \[{"label": "Tokyo Office", "lat": 35.68, "lon": 139.69}]

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

Only return earthquakes at or above this magnitude.

## `maxRadiusKm` (type: `integer`):

How far from each location to search, in kilometers.

## `daysBack` (type: `integer`):

How many days of earthquake history to check, up to 365.

## `maxItems` (type: `integer`):

Hard cap on items returned. You are never charged beyond this.

## Actor input object example

```json
{
  "locations": [
    {
      "label": "Tokyo Office",
      "lat": 35.68,
      "lon": 139.69
    }
  ],
  "minMagnitude": 4.5,
  "maxRadiusKm": 300,
  "daysBack": 7,
  "maxItems": 1000
}
```

# Actor output Schema

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

Matched earthquakes, ranked by PAGER alert then magnitude.

## `qualityReport` (type: `string`):

Locations checked, parameters, problems.

# 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 = {
    "locations": [
        {
            "label": "Tokyo Office",
            "lat": 35.68,
            "lon": 139.69
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/earthquake-monitor").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 = { "locations": [{
            "label": "Tokyo Office",
            "lat": 35.68,
            "lon": 139.69,
        }] }

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/earthquake-monitor").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 '{
  "locations": [
    {
      "label": "Tokyo Office",
      "lat": 35.68,
      "lon": 139.69
    }
  ]
}' |
apify call alaudinburki/earthquake-monitor --silent --output-dataset

```

## MCP server setup

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

```

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/rxef22oMhDo1KokP9/builds/DG73KSEnpQL0dY0Nr/openapi.json