# EPA ECHO Scraper: Facility Violations & Penalties (`thoob/epa-echo-facility-feed`) Actor

Clean, flat environmental-compliance records for regulated facilities from the official EPA ECHO web services: compliance status, violations, inspections, formal actions, and penalties, with a what-changed-since-last-run mode. Billed only per delivered record.

- **URL**: https://apify.com/thoob/epa-echo-facility-feed.md
- **Developed by:** [Pono Data](https://apify.com/thoob) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$12.00 / 1,000 facility records

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

## EPA ECHO Facility Compliance & Enforcement Feed

Clean, flat environmental-compliance records for regulated facilities, pulled from the official EPA ECHO web services. Filter by state, county, and industry, get one useful row per facility with its compliance status, violations, inspections, enforcement actions, and penalties, and run a changes-only mode that returns just what changed since your last run.

You pay only for a delivered facility record. Filtered-out rows, unchanged rows in changes mode, and malformed records cost nothing. There is no start fee.

### What a record is

One flat row per facility, pulled from the EPA ECHO facility report:

- identity and location: `facilityName`, `registryId` (the EPA Facility Registry ID), `street`, `city`, `state`, `zip`, `county`, `latitude`, `longitude`
- classification: `naicsCodes`, `sicCodes`, `federalFacilityFlag`
- compliance status: `complianceStatus`, plus per-program status for Clean Air Act (`caaComplianceStatus`), Clean Water Act (`cwaComplianceStatus`), hazardous waste / RCRA (`rcraComplianceStatus`), and Safe Drinking Water Act (`sdwaComplianceStatus`)
- non-compliance signals: `significantNonComplianceFlag`, `quartersWithNonCompliance`, `programsWithSignificantNonCompliance`
- inspections: `inspectionCount`, `lastInspectionDate`
- enforcement: `formalActionCount`, `lastFormalActionDate`
- penalties: `totalPenalties`, `penaltyCount`, `lastPenaltyDate`, `lastPenaltyAmount`
- provenance: `sourceUrl`, `retrievedAt`, `confidence`, `jurisdiction`, `dataSource`, and in changes mode `changeType`

Every value appears verbatim at the facility's own ECHO Detailed Facility Report in `sourceUrl`. Dates are normalized to ISO (YYYY-MM-DD) and penalty amounts to numbers. Nothing is guessed.

### Sample output

A real slice of Delaware facilities, with one carrying enforcement (abbreviated):

| facilityName | city | naicsCodes | complianceStatus | formalActionCount | totalPenalties | sourceUrl |
|---|---|---|---|---|---|---|
| ADESIS, INC. | NEW CASTLE | 54171 | No Violation Identified | 1 | 10000 | echo.epa.gov/detailed-facility-report?fid=110006816936 |
| 1-711 - SALEM CHURCH RD. OVER I-95 | NEWARK | 238320 | No Violation Identified | 0 | 0 | echo.epa.gov/detailed-facility-report?fid=110072036227 |

A facility can show "No Violation Identified" as its current headline status while still carrying recent quarters of non-compliance and a past penalty. Both are reported, so you see the full picture, not just the headline.

### Two modes

- **full**: every facility matching your filter.
- **changes**: only facilities that are new, have a changed compliance status, a new enforcement action or penalty, or a newer inspection date since this account's last run. The state is tracked per account in a named store, so it is your timeline. The first changes run has no baseline, so it returns everything matching once, then tracks deltas from there.

### Filters

- **states**: US state or territory codes. ECHO runs one state per query, so this is required; pass one or many. Non-US or invalid codes are turned away unbilled.
- **counties**: keep only facilities in these counties.
- **naics**: keep only facilities whose NAICS industry code starts with one of these prefixes (for example 3241 for petroleum, 562 for waste management).
- **sic**: keep only facilities with one of these legacy SIC codes.
- **onlyWithViolations**: keep only facilities the record shows as out of compliance, flagged for significant non-compliance, or carrying quarters of non-compliance.
- **onlyActive**: restrict to active facilities (default on) rather than the full historical registry.
- **federalOnly**: keep only federal-government facilities.
- **maxRecords**: a cap on how many records a run delivers and bills. Defaults to 1000, because a state can be large: California alone is about 496,000 active facilities. Set 0 for no cap. In changes mode nothing is lost to the cap; the rest arrives on a later run and is never billed twice. The platform spend cap is honored regardless.

### What to expect

- ECHO covers about 1.65 million regulated US facilities, refreshed by EPA on its own schedule. A filter narrows that to the slice you care about.
- Large states are delivered, across runs. ECHO's bulk download refuses any query over 100,000 rows, so this actor walks the stored query page by page instead whenever a state is that big. Measured on California, about 496,000 active facilities: a run scans 80,000 to 112,000 of them before it either fills your record cap or EPA throttles the walk, and it stops cleanly either way, delivering everything it fetched and billing nothing else. In changes mode the next run resumes where the last one stopped, so a large state arrives over several runs and nothing is billed twice. Before this, California delivered nothing at all.
- The raw ECHO web services are public and free directly from EPA. What this actor sells is the flat, typed record, the client-side industry and violation filtering, and the per-account change feed, so you do not have to walk the service, page its map endpoint one row at a time, or diff it yourself.
- A state pull is a few dollars at most; a daily changes feed on one state is pennies a run.

### Source and scope

What this collects: public environmental-compliance records on regulated facilities (businesses and government sites).
Source: the official EPA ECHO REST web services (echo.epa.gov), a US EPA system, public domain, no key, no anti-bot, called with a declared identifying User-Agent.
Scope: United States facilities only. `jurisdiction=US` is stamped on every row.
Billing: charged only on a delivered facility record; rejects are free; no start fee.
Provenance: every row carries its source URL (the facility's ECHO report) and retrieval time.

These are business-level and government-facility public records, not consumer data. This is a data tool, not legal, environmental, or investment advice. A compliance record is a public filing, not a verdict.

### See also

More clean, pay-only-for-results data tools from Pono Data:

- [Federal Spending Feed](https://apify.com/thoob/federal-spending-feed) - US federal awards from USAspending.gov
- [Regulatory Change Monitor](https://apify.com/thoob/regulatory-change-monitor) - federal rulemaking from the Federal Register

Full catalog: https://apify.com/thoob

# Actor input Schema

## `states` (type: `array`):

US state or territory codes to pull facilities for (for example CA, TX, NY). ECHO runs one state per query; this actor loops them. At least one is required. Non-US or invalid codes are turned away unbilled.

## `counties` (type: `array`):

Optional. Keep only facilities in these counties (applied by ECHO). County names as ECHO spells them, for example NEW CASTLE.

## `naics` (type: `array`):

Optional. Keep only facilities whose NAICS industry code starts with one of these (for example 3241 for petroleum, 562 for waste management). Applied by ECHO and re-checked on the record.

## `sic` (type: `array`):

Optional. Keep only facilities with one of these SIC industry codes (legacy classification). Applied by ECHO.

## `onlyWithViolations` (type: `boolean`):

When on, keep only facilities the record shows as out of compliance, flagged for significant non-compliance, or carrying quarters of non-compliance. Off returns every matching facility regardless of status.

## `onlyActive` (type: `boolean`):

When on (default), restrict to facilities ECHO marks active, rather than the full historical registry which includes closed sites.

## `federalOnly` (type: `boolean`):

When on, keep only federal-government facilities. Off returns all facility types.

## `mode` (type: `string`):

full returns every facility matching your filter. changes returns only facilities that are new, have a changed compliance status, a new enforcement action or penalty, or a newer inspection since this account's last run, tracked per account. The first changes run has no baseline, so it returns everything matching once, then tracks deltas.

## `maxRecords` (type: `integer`):

Cap on how many facilities this run delivers and bills. Defaults to 1000, because a whole state can be large: California alone is about 496,000 active facilities. Set 0 for no cap. In changes mode, facilities beyond the cap are not dropped: they are delivered on a later run, never billed twice. The platform spend cap (ACTOR\_MAX\_TOTAL\_CHARGE\_USD) is honored regardless.

## Actor input object example

```json
{
  "states": [
    "DE"
  ],
  "counties": [],
  "naics": [],
  "sic": [],
  "onlyWithViolations": false,
  "onlyActive": true,
  "federalOnly": false,
  "mode": "full",
  "maxRecords": 1000
}
```

# Actor output Schema

## `facilities` (type: `string`):

One row per regulated facility matching your filter.

# 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 = {
    "states": [
        "DE"
    ],
    "counties": [],
    "naics": [],
    "sic": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("thoob/epa-echo-facility-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "states": ["DE"],
    "counties": [],
    "naics": [],
    "sic": [],
}

# Run the Actor and wait for it to finish
run = client.actor("thoob/epa-echo-facility-feed").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 '{
  "states": [
    "DE"
  ],
  "counties": [],
  "naics": [],
  "sic": []
}' |
apify call thoob/epa-echo-facility-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=thoob/epa-echo-facility-feed",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/nxsVNw7gJDDX5x2CB/builds/c4qfmfe3r2vdqTc2E/openapi.json