# EPA ECHO Facility Compliance Delta Monitor (`apex-nexus/epa-echo-facility-compliance-monitor`) Actor

Watchlist-free EPA Envirofacts facility compliance delta monitor: one alert per new or changed facility since the last run, free when nothing changes. Public EPA data only.

- **URL**: https://apify.com/apex-nexus/epa-echo-facility-compliance-monitor.md
- **Developed by:** [Valunex](https://apify.com/apex-nexus) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 epa echo facility compliance alerts

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?

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

## EPA ECHO Facility Compliance Delta Monitor

Watchlist-free delta monitor of U.S. EPA regulated facilities via the public
EPA Envirofacts Data Service (`envirofacts_site`). Emits one dataset alert per
facility that is new or changed since the last run — **"free when nothing
changes"** (unchanged replays emit nothing).

### Who it is for

Environmental consultants and engineering firms (site acquisition / due
diligence), ESG and supply-chain compliance teams, environmental law firms,
environmental-liability insurance underwriters, and industrial buyers siting
new facilities. Enforcement history and penalty exposure drive real
transaction and insurance decisions, so buyers pay for the signal — per-state
or per-facility monitoring — rather than re-polling EPA by hand.

### What makes it different

Existing Apify Store actors for EPA ECHO / Envirofacts are typically on-demand
scrapers: you run them, get a batch, and run again when you want an update.
This Actor keeps a checkpoint keyed by the facility registry ID (`site_id`),
so repeat runs emit only genuinely new or changed facilities — free when
nothing changes, pay only on signal.

### Data source

Public U.S. government data only, via the EPA Envirofacts Data Service:

- https://data.epa.gov/efservice/envirofacts_site

No credentials, no signup, no proxies, no scraping of rate-limited or anti-bot
pages, no commercial inference (no LLMs) inside the product.

### Output

One dataset item per new or changed facility since the last run. The full
schema is defined in `.actor/dataset_schema.json` and the Actor output schema
in `.actor/output_schema.json`.

Example output item:

```json
{
  "site_id": "0100001",
  "registry_id": "0100001",
  "epa_id": "CTD000604546",
  "facility_name": "CT RESOURCE RECOVERY AUTHORITY",
  "city": "SHELTON",
  "state": "CT",
  "zip": "06488",
  "county": "NEW HAVEN",
  "epa_region": "01",
  "latitude": null,
  "longitude": null,
  "archived": "Y",
  "regulated_programs": null,
  "compliance_status": null,
  "violations": null,
  "inspections": null,
  "formal_enforcement_actions": null,
  "assessed_penalties": null,
  "changeType": "new",
  "changedAt": "2026-11-02T22:00:00+00:00",
  "sourceUrl": "https://data.epa.gov/efservice/envirofacts_site/1:200/JSON",
  "checkpointKey": "epa_echo_facility_compliance"
}
```

Every field is `null` when it could not be parsed from the source — the Actor
never guesses. The `envirofacts_site` view provides `site_id`, `epa_id`,
`name`, `city`, `state`, `ZIP`, `county`, EPA region and lat/long; a separate
12-digit FRS `registry_id`, CAA/CWA/RCRA/SDWA program flags, compliance
status, violations, inspections, formal enforcement actions and assessed
penalties are not provided by that view and are emitted as `null`. On repeat
runs with no facility changes the dataset is empty ("free when nothing
changes").

### Checkpoint behaviour

The delta checkpoint key is the facility `site_id` (the stable Envirofacts
site / registry identifier). State (the previously seen field snapshot per
site_id) is kept in a named Actor key-value store
(`epa-echo-facility-compliance-checkpoints`), so repeat runs emit only
facilities that are new or whose tracked fields changed (`epa_id`,
`facility_name`, `city`, `state`, `zip`, `county`, `epa_region`, `latitude`,
`longitude`, `archived`). Resetting the store re-emits the full slice.

### Pricing (pay-per-event, Apify Store — publication task sets this)

- Actor start: $0.0001 per run (`apify-actor-start`)
- EPA ECHO facility compliance alert (dataset item): $0.005 per alert
  (`apify-default-dataset-item`, primary)
- Apify retains a 20% commission; payouts require completed identity
  verification (KYC) — an owner step at payout time.

Price changes are limited to no more than once per month, with at least 14
days' notice (per Apify Terms).

### Input

See `.actor/input_schema.json`. No required fields — the default input is
empty and monitors one facility registry slice with no filters.

- `sourceUrl`: EPA Envirofacts facility endpoint URL (default: the public
  `envirofacts_site` feed).

Example:

```json
{}
```

### Files

- `main.py` — Apify SDK Python Actor
- `requirements.txt` — pinned deps (`apify==4.1.0`, `httpx==0.27.2`); `pytest`/`ruff` are dev tools
- `tests/test_monitor.py` — deterministic unit tests, no network
- `.actor/actor.json`, `.actor/input_schema.json`, `.actor/output_schema.json`,
  `.actor/dataset_schema.json` — Apify platform metadata

Run `pytest tests` before release (builder acceptance criterion).

### Search terms

EPA ECHO monitor, Envirofacts facility data, EPA compliance violation tracker,
regulated facility monitor, environmental enforcement actions tracker, EPA
facility compliance data, Toxic Release Inventory facility monitor, ESG
supplier due diligence EPA.

# Actor input Schema

## `sourceUrl` (type: `string`):

EPA Envirofacts Data Service facility records endpoint (JSON). Defaults to the public `envirofacts_site` feed.

## Actor input object example

```json
{
  "sourceUrl": "https://data.epa.gov/efservice/envirofacts_site/1:200/JSON"
}
```

# Actor output Schema

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

All dataset items (EPA ECHO facility compliance alerts) emitted by the Actor run.

# 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 = {
    "sourceUrl": "https://data.epa.gov/efservice/envirofacts_site/1:200/JSON"
};

// Run the Actor and wait for it to finish
const run = await client.actor("apex-nexus/epa-echo-facility-compliance-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 = { "sourceUrl": "https://data.epa.gov/efservice/envirofacts_site/1:200/JSON" }

# Run the Actor and wait for it to finish
run = client.actor("apex-nexus/epa-echo-facility-compliance-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 '{
  "sourceUrl": "https://data.epa.gov/efservice/envirofacts_site/1:200/JSON"
}' |
apify call apex-nexus/epa-echo-facility-compliance-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apex-nexus/epa-echo-facility-compliance-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/VKxRLf1kIUfc9DDYf/builds/bufRyDQ1pdT6yQQy0/openapi.json