# USGS Earthquake Events Scraper (`nexgenwatch/usgs-earthquake-event-feed`) Actor Scrape USGS earthquake events (FDSN): magnitude, location, depth, time and event ID. One record per result. Pay per result. - **URL**: https://apify.com/nexgenwatch/usgs-earthquake-event-feed.md - **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community) - **Categories:** Developer tools, News - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $13.40 / 1,000 seismic 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/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 Earthquake Events Scraper **Scrape USGS earthquake events (FDSN): magnitude, location, depth, time and event ID.** Run it once and you get the current records as a dataset; put it on a schedule to keep the list current. **Scrape USGS earthquake events (FDSN): magnitude, location, depth, time and event ID.** Run it once and you get the current records as a dataset; put it on a schedule to keep the list current. Structured **seismic event** records from the official U.S. Geological Survey **FDSN Event web service** (`earthquake.usgs.gov/fdsnws/event/1`), read keyless over GeoJSON. One record per event in your requested time window β€” official event parameters for **exposure joins**, carried source-native and **verbatim**. Output is one `seismic_event_record` row per result; billing is pay-per-event, the value event being one seismic event record (a $0.02 start fee per run, then $0.02 per seismic event record). Source: earthquake.usgs.gov. ### πŸ“Š Sample Output [![USGS Earthquake Events Scraper sample output β€” a table of real seismic event record rows (event\_id, event\_type, place, time\_epoch\_ms) from run Py4Ow3x6BlyKTWIt6 on build 0.1.8](https://api.apify.com/v2/key-value-stores/8gLgXMBveEI1tTz1z/records/usgs-earthquake-event-feed-sample)](https://apify.com/nexgenwatch/usgs-earthquake-event-feed?fpr=2ayu9b) Real rows from run `Py4Ow3x6BlyKTWIt6` on build 0.1.8 (2026-09-27), the same input as the Quick start below β€” every value is as the source published it (emails masked, long text shortened): | event\_id | event\_type | place | time\_epoch\_ms | updated\_epoch\_ms | status | |---|---|---|---|---|---| | hv74998796 | earthquake | 33 km SW of Laupāhoehoe, Hawaii | 1783468799850 | 1783469002940 | automatic | | nc75391711 | earthquake | 0 km SSW of Angwin, CA | 1783468344700 | 1784500643591 | reviewed | | tx2026nhcgxp | earthquake | 7 km NNW of Nordheim, Texas | 1783468343897 | 1783527550051 | reviewed | | nc75391706 | earthquake | 5 km NW of The Geysers, CA | 1783468294880 | 1784496034958 | reviewed | | aka2026njftrr | earthquake | 50 km SSE of Adak, Alaska | 1783468167682 | 1784177495329 | reviewed | | uu80144826 | earthquake | 17 km NE of Milford, Utah | 1783468025770 | 1783519782360 | reviewed | | uu80144821 | earthquake | 16 km NE of Milford, Utah | 1783467842050 | 1783518875250 | reviewed | | nn00921304 | earthquake | 17 km NNW of Indian Springs, Nevada | 1783467391025 | 1784053297945 | reviewed | The run finished with the status message: `NORMAL: 50 unique rows (0 duplicates collapsed) from 2026-07-08T00:00:00. billable=50` ### βœ… What you get Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`): - `record_type` (string/null) β€” e.g. `seismic_event_record` - `event_id` (string/null) β€” e.g. `hv74998796` - `event_type` (string/null) β€” e.g. `earthquake` - `magnitude` (number/integer/string/null) β€” e.g. `1.71` - `mag_type` (string/null) β€” e.g. `md` - `place` (string/null) β€” e.g. `33 km SW of Laupāhoehoe, Hawaii` - `time_epoch_ms` (string/integer/null) β€” e.g. `1783468799850` - `updated_epoch_ms` (string/integer/null) β€” e.g. `1783469002940` - `status` (string/null) β€” e.g. `automatic` - `net` (string/null) β€” e.g. `hv` - `code` (string/null) β€” e.g. `74998796` - `longitude` (number/integer/string/null) β€” e.g. `-155.419494628906` - `latitude` (number/integer/string/null) β€” e.g. `19.7403335571289` - `depth_km` (number/integer/string/null) β€” e.g. `24.8700008392334` - `significance` (string/integer/null) β€” e.g. `45` - `tsunami_flag` (string/integer/null) β€” e.g. `0` - `nst` (string/integer/null) β€” e.g. `20` - `event_url` (string/null) β€” e.g. `https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796` - `scope_note` (string/null) β€” e.g. `official USGS seismic event record for exposure joins; no PAGER alert, shaking i` - `source_url` (string/null) β€” e.g. `https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796` - `source` (string/null) β€” e.g. `usgs-earthquake-event-feed` - `release_date` (string/null) β€” e.g. `2026-07-08T00:00:00` - `observed_at` (string/null) β€” e.g. `2026-09-27T16:43:29Z` - `license` (string/null) β€” e.g. `U.S. Geological Survey (USGS) Earthquake Hazards Program, FDSN Event web service` - `attribution` (string/null) β€” e.g. `U.S. Geological Survey β€” Earthquake Hazards Program (https://earthquake.usgs.gov` - `release_checksum` (string/null) β€” null in every sample row - `terminal` (string/null) β€” null in every sample row - `scope` (string/null) β€” null in every sample row - `note` (string/null) β€” null in every sample row - `reported_total` (string/integer/null) β€” null in every sample row - `raw_seen` (string/integer/null) β€” null in every sample row - `duplicates` (string/integer/null) β€” null in every sample row - `unique_found` (string/integer/null) β€” null in every sample row - `delivered` (string/integer/null) β€” null in every sample row **βœ… What you get** Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`): - `record_type` (string/null) β€” e.g. `seismic_event_record` - `event_id` (string/null) β€” e.g. `hv74998796` - `event_type` (string/null) β€” e.g. `earthquake` - `magnitude` (number/integer/string/null) β€” e.g. `1.71` - `mag_type` (string/null) β€” e.g. `md` - `place` (string/null) β€” e.g. `33 km SW of Laupāhoehoe, Hawaii` - `time_epoch_ms` (string/integer/null) β€” e.g. `1783468799850` - `updated_epoch_ms` (string/integer/null) β€” e.g. `1783469002940` - `status` (string/null) β€” e.g. `automatic` - `net` (string/null) β€” e.g. `hv` - `code` (string/null) β€” e.g. `74998796` - `longitude` (number/integer/string/null) β€” e.g. `-155.419494628906` - `latitude` (number/integer/string/null) β€” e.g. `19.7403335571289` - `depth_km` (number/integer/string/null) β€” e.g. `24.8700008392334` - `significance` (string/integer/null) β€” e.g. `45` - `tsunami_flag` (string/integer/null) β€” e.g. `0` - `nst` (string/integer/null) β€” e.g. `20` - `event_url` (string/null) β€” e.g. `https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796` - `scope_note` (string/null) β€” e.g. `official USGS seismic event record for exposure joins; no PAGER alert, shaking i` - `source_url` (string/null) β€” e.g. `https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796` - `source` (string/null) β€” e.g. `usgs-earthquake-event-feed` - `release_date` (string/null) β€” e.g. `2026-07-08T00:00:00` - `observed_at` (string/null) β€” e.g. `2026-09-19T02:15:04Z` - `license` (string/null) β€” e.g. `U.S. Geological Survey (USGS) Earthquake Hazards Program, FDSN Event web service` - `attribution` (string/null) β€” e.g. `U.S. Geological Survey β€” Earthquake Hazards Program (https://earthquake.usgs.gov` - `release_checksum` (string/null) β€” null in every sample row - `terminal` (string/null) β€” null in every sample row - `scope` (string/null) β€” null in every sample row - `note` (string/null) β€” null in every sample row - `reported_total` (string/integer/null) β€” null in every sample row - `raw_seen` (string/integer/null) β€” null in every sample row - `duplicates` (string/integer/null) β€” null in every sample row - `unique_found` (string/integer/null) β€” null in every sample row - `delivered` (string/integer/null) β€” null in every sample row **βœ… What you get** Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`): - `record_type` (string/null) β€” e.g. `seismic_event_record` - `event_id` (string/null) β€” e.g. `hv74998796` - `event_type` (string/null) β€” e.g. `earthquake` - `magnitude` (number/integer/string/null) β€” e.g. `1.71` - `mag_type` (string/null) β€” e.g. `md` - `place` (string/null) β€” e.g. `33 km SW of Laupāhoehoe, Hawaii` - `time_epoch_ms` (string/integer/null) β€” e.g. `1783468799850` - `updated_epoch_ms` (string/integer/null) β€” e.g. `1783469002940` - `status` (string/null) β€” e.g. `automatic` - `net` (string/null) β€” e.g. `hv` - `code` (string/null) β€” e.g. `74998796` - `longitude` (number/integer/string/null) β€” e.g. `-155.419494628906` - `latitude` (number/integer/string/null) β€” e.g. `19.7403335571289` - `depth_km` (number/integer/string/null) β€” e.g. `24.8700008392334` - `significance` (string/integer/null) β€” e.g. `45` - `tsunami_flag` (string/integer/null) β€” e.g. `0` - `nst` (string/integer/null) β€” e.g. `20` - `event_url` (string/null) β€” e.g. `https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796` - `scope_note` (string/null) β€” e.g. `official USGS seismic event record for exposure joins; no PAGER alert, shaking i` - `source_url` (string/null) β€” e.g. `https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796` - `source` (string/null) β€” e.g. `usgs-earthquake-event-feed` - `release_date` (string/null) β€” e.g. `2026-07-08T00:00:00` - `observed_at` (string/null) β€” e.g. `2026-09-19T01:32:41Z` - `license` (string/null) β€” e.g. `U.S. Geological Survey (USGS) Earthquake Hazards Program, FDSN Event web service` - `attribution` (string/null) β€” e.g. `U.S. Geological Survey β€” Earthquake Hazards Program (https://earthquake.usgs.gov` - `release_checksum` (string/null) β€” null in every sample row - `terminal` (string/null) β€” null in every sample row - `scope` (string/null) β€” null in every sample row - `note` (string/null) β€” null in every sample row - `reported_total` (string/integer/null) β€” null in every sample row - `raw_seen` (string/integer/null) β€” null in every sample row - `duplicates` (string/integer/null) β€” null in every sample row - `unique_found` (string/integer/null) β€” null in every sample row - `delivered` (string/integer/null) β€” null in every sample row **What you get** One `seismic_event_record` per event: - `event_id`, `event_type`, `magnitude`, `mag_type`, `place`, `status`, `net`, `code` - `time_epoch_ms`, `updated_epoch_ms` β€” origin and last-revision timestamps - `longitude`, `latitude`, `depth_km` β€” location for spatial/exposure joins - `significance`, `tsunami_flag`, `nst`, `event_url`, `release_date`, `license`, `attribution` ### βš™οΈ Sample inputs **1. Quick start β€” the Store example (this is what the sample above came from)** ```json { "startTime": "2026-07-01", "endTime": "2026-07-08", "maxRecords": 50 } ``` The sample run charged exactly: 1 Γ— $0.02 apify-actor-start + 50 Γ— $0.02 seismic\_event\_record = **$1.02** on the Free tier β€” every delivered row was billed. **2. A smaller, narrowed run** ```json { "startTime": "2026-07-01", "endTime": "2026-07-08", "maxRecords": 5 } ``` Caps the run at 5 rows β€” about $0.12 on the Free tier ($0.02 start + 5 Γ— $0.02). `startTime` narrows what the source is asked for. **3. A full-size run** ```json { "startTime": "2026-07-01", "endTime": "2026-07-08", "maxRecords": 5000 } ``` Up to 5000 rows (the schema default for `maxRecords`) β€” about $100.02 on the Free tier ($0.02 start + 5000 Γ— $0.02) if the source has that many. ### 🧾 JSON sample record One real record from run `Py4Ow3x6BlyKTWIt6`, exactly as it lands in the dataset (emails masked, long text shortened): ```json { "record_type": "seismic_event_record", "event_id": "hv74998796", "event_type": "earthquake", "magnitude": 1.71, "mag_type": "md", "place": "33 km SW of Laupāhoehoe, Hawaii", "time_epoch_ms": 1783468799850, "updated_epoch_ms": 1783469002940, "status": "automatic", "net": "hv", "code": "74998796", "longitude": -155.419494628906, "latitude": 19.7403335571289, "depth_km": 24.8700008392334, "significance": 45, "tsunami_flag": 0, "nst": 20, "event_url": "https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796", "scope_note": "official USGS seismic event record for exposure joins; no PAGER alert, shaking intensity, or loss estimate is included or generated; this is a run-output feed, not a notification service", "source_url": "https://earthquake.usgs.gov/earthquakes/eventpage/hv74998796", "source": "usgs-earthquake-event-feed", "release_date": "2026-07-08T00:00:00", "observed_at": "2026-09-27T16:43:29Z", "license": "U.S. Geological Survey (USGS) Earthquake Hazards Program, FDSN Event web service β€” U.S. Government work, public domain. Official seismic event records only; no forecast, PAGER alert, shaking intensity, or loss estimate is generated or deliv", "attribution": "U.S. Geological Survey β€” Earthquake Hazards Program (https://earthquake.usgs.gov/)" } ``` ### πŸ”§ How it works **Source.** The actor reads earthquake.usgs.gov β€” endpoints: `https://earthquake.usgs.gov/`, `https://earthquake.usgs.gov/fdsnws/event/1`, `https://earthquake.usgs.gov/fdsnws/event/1/query`, `https://earthquake.usgs.gov/robots.txt`. Public pages and feeds only; nothing behind a login. **Transport.** Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: `CRAWL_DELAY`=0.0. **Terminal states.** A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE\_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape β€” the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success. **Charging.** Each seismic event record is charged at the moment it is pushed (`seismic_event_record`); a row that fails to charge is not delivered, so the dataset count always equals the charged count. **πŸ”§ How it works** **Source.** The actor reads earthquake.usgs.gov β€” endpoints: `https://earthquake.usgs.gov/`, `https://earthquake.usgs.gov/fdsnws/event/1`, `https://earthquake.usgs.gov/fdsnws/event/1/query`, `https://earthquake.usgs.gov/robots.txt`. Public pages and feeds only; nothing behind a login. **Transport.** Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: `CRAWL_DELAY`=0.0. **Terminal states.** A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE\_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape β€” the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success. **Charging.** Each seismic event record is charged at the moment it is pushed (`seismic_event_record`); a row that fails to charge is not delivered, so the dataset count always equals the charged count. **πŸ”§ How it works** **Transport.** Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: `CRAWL_DELAY`=0.0. **Terminal states.** A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE\_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape β€” the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success. **Charging.** Each seismic event record is charged at the moment it is pushed (`seismic_event_record`); a row that fails to charge is not delivered, so the dataset count always equals the charged count. **Window & the 20,000-event cap** `startTime` and `endTime` (ISO) are **required** β€” the feed is never queried unbounded. The FDSN service caps a single query at **20,000 events**; this actor COUNT-probes your window and **recursively partitions** it so every underlying query stays under the cap. A window that cannot be split below the cap fails loud (narrow it or add `minMagnitude`). Optional `minMagnitude` and a lat/long bounding box further scope the window. **Revisions & integrity** Records are **revision-aware**: deduped by `event_id` + `updated` timestamp, so a re-reviewed event is a distinct record and accidental boundary duplicates collapse. A non-JSON (HTML) or non-GeoJSON response fails loud and bills nothing. **Scope** This is a **run-output feed of official event records for exposure joins β€” not a notification service**. It generates and delivers **no forecast, PAGER alert, shaking-intensity, or loss estimate**; only the seismic event parameters are emitted (`scope_note` on every record states this). **Robots & door** `earthquake.usgs.gov/robots.txt` returns 404 (no policy); the actor re-reads it every run and STOPS loudly if USGS ever disallows `/fdsnws`. It never spoofs or works around a block. **Source & licence** U.S. Geological Survey, Earthquake Hazards Program β€” U.S. Government work, **public domain**. Acknowledgement: data from the U.S. Geological Survey (https://earthquake.usgs.gov/). **What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation. **What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation. **⏰ Optional: run it on a schedule** A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console β†’ **Schedules** β†’ **Create new**, add this actor with the input you want, and pick a cadence: - **Daily** β€” `0 7 * * *` (07:00 UTC): catch changes within a day. - **Weekly** β€” `0 7 * * 1`: a Monday digest. Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console β†’ Integrations). **What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation. ### ⏰ Optional: run it on a schedule A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console β†’ **Schedules** β†’ **Create new**, add this actor with the input you want, and pick a cadence: - **Daily** β€” `0 7 * * *` (07:00 UTC): catch changes within a day. - **Weekly** β€” `0 7 * * 1`: a Monday digest. Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console β†’ Integrations). ### πŸ’° Pricing example | Event | Free | Bronze | Silver | Gold | |---|---|---|---|---| | Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 | | Seismic event record (`seismic_event_record`) | $0.02 | $0.018 | $0.016 | $0.0134 | Worked at the live Free-tier price: - 8 seismic event records: $0.02 start + 8 Γ— $0.02 = **$0.18** - 25 seismic event records: $0.02 start + 25 Γ— $0.02 = **$0.52** - 5000 seismic event records: $0.02 start + 5000 Γ— $0.02 = **$100.02** A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB. Yield on the sample run: `NORMAL: 50 unique rows (0 duplicates collapsed) from 2026-07-08T00:00:00. billable=50`. `maxRecords` is a hard ceiling on what is delivered and billed, never a target. ### βš–οΈ Legal & ToS This actor reads public, logged-out pages and feeds published by earthquake.usgs.gov. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring. ### ❓ FAQ **Q: Do I need an API key or a login?**\ A: No. The source (earthquake.usgs.gov) is read logged-out; the input schema has no key field and the actor carries no secrets. **Q: Why did my run return 0 rows?**\ A: Read the run's status message. GENUINE\_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event β€” retry later or narrow the input. A zero-row run bills the start fee only. **Q: How many rows can one run return?**\ A: Up to `maxRecords` (default 5000). Raise the cap for a bigger run; you pay per delivered row. **Q: How fresh is the data?**\ A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed. **Q: What formats can I export?**\ A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration. **Q: How is this different from the other NexGen Watch actors actors?**\ A: Same output shape and billing model; this one covers earthquake.usgs.gov. The siblings under **Related Actors** cover the other sources or slices β€” run several on one schedule for a combined feed. **Q: Are there rate limits?**\ A: The actor paces itself against the source (`CRAWL_DELAY`=0.0) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency. ### πŸ†˜ Troubleshooting - **Run FAILED with BLOCKED** β†’ the source refused the request or changed its page shape β†’ nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id. - **Status says CAPPED** β†’ your cap (`maxRecords`) was reached β†’ raise it for a bigger run. - **Input validation error on start** β†’ a field is outside the schema's allowed values β†’ start from the Quick start block and change one field at a time. - **Run TIMED-OUT** β†’ a very wide request on a slow day β†’ raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset. ### πŸ”— Related Actors - [USDA FDC Portion / Serving Weight Master](https://apify.com/nexgenwatch/usda-fdc-portion-serving-weight-master?fpr=2ayu9b) β€” One food\_portion\_record per row of USDA FoodData Central's food\_portion table β€” a food's serving/portion definition: portion ID, food FDC ID, serving… - [USDA FDC Product Update Ledger](https://apify.com/nexgenwatch/usda-fdc-product-update-ledger?fpr=2ayu9b) β€” One food\_update\_record per entry in USDA FoodData Central's own product update log β€” the FDC id, the product description, and the last\_updated date,… - [USDA FNDDS Ingredient-Nutrient Matrix](https://apify.com/nexgenwatch/usda-fndds-ingredient-nutrient-matrix?fpr=2ayu9b) β€” One fndds\_nutrient\_record per row of USDA FoodData Central's fndds\_ingredient\_nutrient\_value table β€” a single nutrient value for an FNDDS ingredient… - [USGS MRDS Mineral Occurrence Master](https://apify.com/nexgenwatch/usgs-mrds-occurrence-master?fpr=2ayu9b) β€” One structured occurrence record per USGS Mineral Resource Data System (MRDS) deposit β€” the source-native dep\_id, deposit name, commodities, coordina… - [Washington Contractor License Registry](https://apify.com/nexgenwatch/washington-contractor-license-registry?fpr=2ayu9b) β€” One record per Washington L\&I contractor licence/registration (number, type, effective/expiry, licence status + suspension date, UBI, principal) from… - [Washington Transportation-Industry Business Licenses](https://apify.com/nexgenwatch/washington-transportation-business-licenses?fpr=2ayu9b) β€” One record per Washington Department of Licensing transportation-industry business licence (tow-truck operators, vehicle transporters, wreckers, deal… - 🏒 **About NexGenData** β€” NexGen Watch is NexGenData's fleet of 281 public data actors built on official sources, pay-per-result. Browse the catalog at [apify.com/nexgenwatch](https://apify.com/nexgenwatch?fpr=2ayu9b). ### ⭐ Found this useful? If this actor saved you a manual check, a quick **[review on the Apify Store](https://apify.com/nexgenwatch/usgs-earthquake-event-feed?fpr=2ayu9b)** helps other teams find it. Feature request or a source that changed? Open it from the **Issues** tab β€” every one is read. # Actor input Schema ## `startTime` (type: `string`): Window start, ISO e.g. 2026-07-01 or 2026-07-01T00:00:00. The FDSN feed is never queried unbounded. ## `endTime` (type: `string`): Window end, ISO e.g. 2026-08-01. Windows over the 20,000-event cap are auto-partitioned. ## `minMagnitude` (type: `string`): Optional minimum magnitude, e.g. "2.5". ## `minLatitude` (type: `string`): Optional bounding-box minimum latitude (decimal degrees). ## `maxLatitude` (type: `string`): Optional bounding-box maximum latitude (decimal degrees). ## `minLongitude` (type: `string`): Optional bounding-box minimum longitude (decimal degrees). ## `maxLongitude` (type: `string`): Optional bounding-box maximum longitude (decimal degrees). ## `maxRecords` (type: `integer`): Max event records delivered (buyer bound; one charge per delivered record). Hard-capped at 20000. ## `userAgent` (type: `string`): Override the transparent crawler UA. ## Actor input object example ```json { "startTime": "2026-07-01", "endTime": "2026-07-08", "maxRecords": 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startTime": "2026-07-01", "endTime": "2026-07-08", "maxRecords": 50 }; // Run the Actor and wait for it to finish const run = await client.actor("nexgenwatch/usgs-earthquake-event-feed").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startTime": "2026-07-01", "endTime": "2026-07-08", "maxRecords": 50, } # Run the Actor and wait for it to finish run = client.actor("nexgenwatch/usgs-earthquake-event-feed").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 '{ "startTime": "2026-07-01", "endTime": "2026-07-08", "maxRecords": 50 }' | apify call nexgenwatch/usgs-earthquake-event-feed --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/usgs-earthquake-event-feed" } } } ``` 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 ` 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/hTgtijZlPewCbTtu4/builds/ayVHrNVVi6LfjtyPv/openapi.json