# EMSC Global Earthquakes Scraper (`parseforge/emsc-earthquakes-scraper`) Actor

Scrapes earthquake events from the EMSC public feed. Returns each event as a flat row with magnitude, depth, coordinates, region, and time. Filter by magnitude range, time window, and geographic bounding box.

- **URL**: https://apify.com/parseforge/emsc-earthquakes-scraper.md
- **Developed by:** [ParseForge](https://apify.com/parseforge) (community)
- **Categories:** Business, Automation, Integrations
- **Stats:** 2 total users, 1 monthly users, 90.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $7.50 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner.jpg)](https://apify.com/parseforge?fpr=vmoqkp)

### EMSC Global Earthquakes Scraper

**Scrape global earthquake data from the EMSC public feed, filtered by magnitude, time, and geographic bounding box.** Each event includes its magnitude, depth, coordinates, region name, and UTC timestamp. No API key required. Export to CSV, JSON, Excel, or XML.

The EMSC publishes real-time earthquake information for Europe, the Mediterranean, and the world, but their web interface makes it hard to pull bulk historical data or filter precisely. This Actor reads the public EMSC feed directly and lets you narrow results by magnitude range, a time window, and a lat/lon bounding box, so you only collect the events that matter to your analysis.

| Who uses it | What they scrape EMSC for |
|---|---|
| Seismology researchers | Building a regional event catalog for a specific time period and magnitude threshold. |
| Insurance risk analysts | Monitoring recent seismic activity within a portfolio's geographic bounding box. |
| Newsroom data journalists | Pulling the latest felt earthquakes above a certain magnitude for a breaking-news map. |
| Disaster response coordinators | Tracking aftershock sequences in a defined area after a major event. |

### What it does

This Actor collects earthquake events from the EMSC public feed and returns each one as a flat row with magnitude, depth, location, and time.

- 📊 **Magnitude filtering:** set a minimum and maximum magnitude to exclude microseisms or focus on significant events.
- 🗺️ **Geographic bounding box:** restrict results to a rectangle defined by min/max latitude and longitude.
- 📅 **Time window:** supply ISO 8601 start and end times to scrape historical or recent earthquake data.
- 🔢 **Result cap:** limit the total number of earthquakes collected per run, up to one million.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

### What you can do with EMSC data

**📈 Build a regional seismicity catalog.**

A researcher sets a bounding box over the Aegean Sea, a start time of 2020-01-01, and a minimum magnitude of 3.0 to compile a multi-year event list for a tectonic study.

**📰 Feed a live earthquake map.**

A news developer runs the Actor every 15 minutes with a minimum magnitude of 4.5 and no geographic filter to populate a global map of newsworthy earthquakes.

**📉 Assess portfolio exposure after a mainshock.**

An insurance analyst sets a tight bounding box around insured properties and a start time immediately after a large event to count aftershocks above magnitude 2.5.

**🔬 Filter out quarry blasts.**

A seismologist sets a minimum magnitude of 2.0 and a maximum depth of 5 km over a mining region to isolate suspected anthropogenic events from the natural catalog.

### Why choose this scraper

| | What you get |
|---|---|
| **No API key** | Reads the public EMSC feed with no registration or authentication. |
| **Fixed schema** | Every earthquake returns the same flat fields for easy database import. |
| **Precise filtering** | Combine magnitude, time, and location filters in a single run. |

### How it compares

No other Store actor targets EMSC the same way, so the honest comparison is with the alternatives teams actually weigh.

| | EMSC Global Earthquakes Scraper | Build it in-house | By hand |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When EMSC changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |

### Configure the run

Drive the Actor with magnitude thresholds, a time window, and a geographic bounding box, alone or together, and filters run as each event is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

```json
{
 "maxItems": 10
}
```

A larger pull:

```json
{
 "maxItems": 200
}
```

### Pricing

Pay-per-result: **$0.0085 per result** collected. You pay only for the results written to your dataset.

| Results collected | Approximate cost |
|---|---|
| 100 results | $0.85 |
| 1,000 results | $8.50 |
| 10,000 results | $85.00 |

New Apify accounts start with $5 in free credit.

### Free users

Free-plan runs return up to 10 results as a preview. [Upgrade your Apify plan](https://console.apify.com/sign-up?fpr=vmoqkp) to collect up to 1,000,000 results per run.

### Run it

1. [Create a free Apify account with $5 in credit](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Open the [EMSC Global Earthquakes Scraper](https://apify.com/parseforge/emsc-earthquakes-scraper?fpr=vmoqkp).
3. Set your inputs and any filters, then click **Start**.
4. Export the results as CSV, Excel, JSON, or XML from the **Dataset** tab.

Run it programmatically through the [Apify API](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) for JavaScript and Python.

### Use with AI agents (MCP)

Give an AI agent live access to EMSC through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

```bash
claude mcp add --transport http apify "https://mcp.apify.com/?tools=parseforge/emsc-earthquakes-scraper"
```

Then prompt it in plain language to run the scraper and read back the results.

### Troubleshooting

**Why am I getting no results?**

Check that your time window is within the last 30 days and that your magnitude and bounding-box filters are not too restrictive. Try widening the filters or removing the time constraint to see if any events match.

**Why are my results missing very recent earthquakes?**

The EMSC feed updates every few minutes. A small delay between an event occurring and appearing in the feed is normal. Run the Actor again after a few minutes.

**The bounding box is not returning the area I expect.**

Remember that min/max latitude and longitude define a rectangle. Ensure minLat is less than maxLat and minLon is less than maxLon. For areas crossing the antimeridian, you may need two separate runs.

**I set a maximum magnitude but still see larger events.**

The maxMagnitude filter is inclusive. If you want to exclude a magnitude, set the maximum slightly below that value, for example 4.9 to exclude magnitude 5.0 and above.

### FAQ

| Question | Answer |
|---|---|
| What is the EMSC? | The European-Mediterranean Seismological Centre is a non-profit that collects real-time earthquake data from seismological networks worldwide and publishes it as a public feed. |
| Do I need an API key or account? | No. This Actor reads the same public data feed that the EMSC website uses, so no registration or API key is required. |
| How far back can I get earthquake data? | The EMSC public feed typically provides events from the past 30 days. For older data, you would need to use a different source or a historical catalog. |
| Can I filter by country or region name? | The Actor filters by geographic bounding box (latitude and longitude), not by named region. You can set a bounding box that covers the country or area you need. |
| What magnitude scale is used? | The EMSC reports magnitude as a unified value, typically the moment magnitude (Mw) or local magnitude (ML) depending on what the contributing network provides. |
| Does this include depth and coordinates? | Yes. Each earthquake row includes the hypocentral depth in kilometers and the latitude and longitude of the epicenter. |
| Can I get the felt reports or damage information? | No. The public feed provides the seismic parameters. Felt reports and damage assessments are not included in this dataset. |
| How many earthquakes can I collect in one run? | You can set a maximum of up to one million events per run, though the actual number returned depends on how many match your filters in the feed. |
| What time format should I use for start and end times? | Use ISO 8601 format, for example 2026-06-01T00:00:00. The time is interpreted as UTC. |
| Can I run this on a schedule? | Yes. You can set up an Apify schedule to run the Actor every hour or every day to collect the latest earthquakes automatically. |

### Related actors

Browse the full [ParseForge collection](https://apify.com/parseforge?fpr=vmoqkp) for more scrapers.

🆘 **Need help?** Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ **Disclaimer.** This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by European-Mediterranean Seismological Centre. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

# Actor input Schema

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

Only include events at or above this magnitude.

## `maxMagnitude` (type: `number`):

Upper magnitude bound.

## `startTime` (type: `string`):

ISO start time (e.g. 2026-06-01T00:00:00).

## `endTime` (type: `string`):

ISO end time.

## `minLat` (type: `number`):

Bounding-box min latitude.

## `maxLat` (type: `number`):

Bounding-box max latitude.

## `minLon` (type: `number`):

Bounding-box min longitude.

## `maxLon` (type: `number`):

Bounding-box max longitude.

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

How many earthquakes to collect per run.

## Actor input object example

```json
{
  "minMagnitude": 2.5,
  "maxItems": 10
}
```

# 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 = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/emsc-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 = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("parseforge/emsc-earthquakes-scraper").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 '{
  "maxItems": 10
}' |
apify call parseforge/emsc-earthquakes-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parseforge/emsc-earthquakes-scraper"
        }
    }
}

```

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/djAPxRpnFpE8Wft19/builds/NNfMrT5VFbKUMsAcV/openapi.json