# EPA Facility Compliance Records — Envirofacts (`nexgensignal/epa-facility-compliance-records`) Actor

Per-record EPA-regulated facilities from the official keyless Envirofacts service. Facility, program system, location, and Superfund/federal-facility flags. State-partitioned, public domain, no personal data.

- **URL**: https://apify.com/nexgensignal/epa-facility-compliance-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, News, Other
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

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 Facility Compliance Records — Envirofacts

**Official source. No API key. Pay per record.**

This actor turns the U.S. EPA's **Envirofacts** facility registry into clean, per-facility records — the regulated facilities in EPA's Integrated Compliance Information System (ICIS), the same underlying data the public ECHO site is built on. Each run reads the official, keyless Envirofacts Data Service and delivers one row per facility interest: the facility name and EPA registry id, the program system it falls under (NPDES water, Air, RCRA, and more), its location, and its status flags (federal facility, Superfund/NPL, tribal land, CAFO). Facility and organization grain, public-domain data, no person fields.

### What this is, in one paragraph

Every facility EPA regulates is recorded in the Facility Registry Service and the ICIS compliance system. EPA exposes this through the keyless Envirofacts Data Service. This actor reads that service, partitioned by state, and flattens each facility-interest row into a single analysis-ready record: what the facility is, where it is, which EPA program covers it, and the flags that matter for screening (is it a federal facility, is it on the Superfund National Priorities List, is it on tribal land). Values are verbatim. You are billed only for records actually delivered.

### Who buys this and for what job

- **Environmental, ESG, and compliance teams** screening facilities in a state by program (water/air/waste) and by risk flags (Superfund, federal facility).
- **Consultants and law firms** building facility inventories for due diligence, siting, or litigation support.
- **Researchers and journalists** mapping regulated facilities and Superfund sites by geography.
- **Data engineers** who want a keyless, one-call EPA facility feed already reduced to facility/org fields.

### Licence — public domain

EPA Envirofacts data is a U.S. Government work in the public domain — free to reuse, including commercially, with attribution. Every record carries: *"Source: U.S. EPA Envirofacts (ICIS facility registry), data.epa.gov."*

### Facility records are not verdicts

This is the honest core of the product. A facility's presence in ICIS, or its listing under a program, is **not** a determination of violation, a penalty, or a verdict about the company — it is the reported facility-interest record as held in EPA's data systems. That caveat is carried on every record: *"A facility's presence or program listing is NOT a determination of violation, penalty, or a verdict about the company."* These are records for screening and inventory, not compliance conclusions; verify against the official EPA ECHO / Envirofacts record before acting.

### Facility / organization grain — no person data

This actor works at facility and organization grain. The Envirofacts facility tables carry no natural-person contact fields; the only name-like fields (`created_by`, `updated_by`) are **system audit codes** (e.g. `FRS`, `AIR_2661`), and this actor never maps them — a person-key guard on every record backstops it, and an acceptance test asserts those audit fields never appear in output.

### Partition required — by state

EPA's facility registry spans **millions** of rows. To keep pulls bounded, honest, and cheap, this actor **requires a state partition**: every run must supply a 2-letter `stateCode`. A run with no state is refused at input validation rather than silently attempting a multi-million-row scan — the partition requirement is enforced in code and covered by an acceptance test. Within a state you can further narrow by program system.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `facility_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `stateCode` | string | — (**required**) | 2-letter US state/territory code to partition the pull (e.g. `CA`, `TX`, `NY`). |
| `programSystem` | string | — | Optional. Keep only facilities in this EPA program system (e.g. `NPDES`, `AIR`, `RCRA`, `ICIS`). Applied to delivered records. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per facility interest. Real example (values verbatim):

```json
{
  "record_id": "3200015475",
  "facility_registry_id": "110011004590",
  "facility_name": "AGRICULTURE, FOREST SERVICE",
  "program_system": "NPDES",
  "program_system_id": "ORU000241",
  "state_code": "OR",
  "epa_region_code": "10",
  "city": null,
  "congressional_district": "02",
  "country_code": "US",
  "latitude": null,
  "longitude": null,
  "federal_facility_flag": "Y",
  "tribal_land_flag": "N",
  "npl_superfund_flag": null,
  "sensitive_data_flag": "N",
  "source": "U.S. EPA Envirofacts (ICIS facility registry)",
  "source_url": "https://echo.epa.gov/detailed-facility-report?fid=110011004590",
  "licence": "U.S. EPA facility data ... public-domain U.S. Government data ...",
  "attribution": "Source: U.S. EPA Envirofacts (ICIS facility registry), data.epa.gov.",
  "observed_at": "2026-08-19T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the state and program filters, rows seen and delivered, and whether charged equals delivered.

### Field reference

Each record is a flat set of screening fields. Identity: `record_id` (ICIS facility-interest id) and `facility_registry_id` (the FRS UIN that links to ECHO). What and where: `facility_name`, `program_system` and `program_system_id`, `state_code`, `epa_region_code`, `city`, `county_code`, `congressional_district`, `country_code`, `location_address`, `zip`, and `latitude`/`longitude`. Screening flags: `federal_facility_flag`, `tribal_land_flag`, `small_business_flag`, `npl_superfund_flag`, `unpermitted_cafo_indicator`, and `sensitive_data_flag`. Provenance and caveats: `source`, `source_url` (a direct ECHO detailed-facility-report link), `licence`, `attribution`, `disclaimer`, and `observed_at`.

### How a run works

A run first re-reads the source's robots posture from your runtime — `data.epa.gov` serves no directive robots file, a no-policy posture — and stops at the door if that ever changes. It then reads the Envirofacts facility table partitioned to your state, one page at a time through the service's `ROWS` range window. Each facility is flattened to one record — system audit fields dropped, placeholder `-` values normalized to null, coordinates coerced to numbers — and delivered **before** it is charged, so a run that is blocked or finds nothing costs you nothing. Your optional program filter is applied to each record before it is delivered, so you are billed only for facilities that pass it. The actor paces between pages (the service is deliberately unhurried), stops when a short page signals the end of the partition or your `maxRecords` ceiling is reached, and records `charge_equals_delivered` in the receipt so you can confirm you were billed for exactly what you received.

### Cost guidance

One `facility_record` per delivered facility: cost = facilities delivered × your plan's per-record price. A single state runs from a few thousand facilities to well over a hundred thousand (California alone is ~147,000 facility interests), so scope with `programSystem` and `maxRecords` to keep runs bounded. 1,000 facilities is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **Facility interests, not compliance verdicts.** This is the facility registry / program-interest record — not a violation, penalty, or enforcement determination.
- **State-partitioned by design.** Every run needs a `stateCode`; there is no unpartitioned national pull.
- **Program filter is applied to delivered records** (client-side), so you are billed only for facilities that pass it.
- **Point-in-time.** Facility records change; re-run to refresh.
- **No person data** is emitted — the only name-like fields are EPA system audit codes, which are dropped.

### Differentiation

This is EPA **facility** data specifically. It is distinct from **fda-recall-risk-records** and **fda-device-clearance-records** (a different agency and product domain entirely), and from the procurement and grant cells in this fleet. It reads EPA's Envirofacts data service directly, at facility grain, for screening and inventory.

### The NexGen Signal family

Part of the NexGen Signal family of official-source, pay-per-record products:

- [Federal Rulemaking Records — US Federal Register](https://apify.com/nexgensignal/federal-rulemaking-records)
- [FDA Device Clearance Records — 510(k)](https://apify.com/nexgensignal/fda-device-clearance-records)
- [FDA Recall Risk Records — openFDA](https://apify.com/nexgensignal/fda-recall-risk-records)
- [World Bank Project Records — Development Pipeline](https://apify.com/nexgensignal/world-bank-project-records)
- [Organization Sanctions & LEI Risk](https://apify.com/nexgensignal/organization-sanctions-lei-risk)

*Source: U.S. EPA Envirofacts Data Service (data.epa.gov), ICIS facility registry. Public-domain U.S. Government data. A facility record is not a determination of violation or a verdict about the company. Reformatted to facility/organisation records; values verbatim; no person data emitted (system audit fields dropped).*

# Actor input Schema

## `stateCode` (type: `string`):

Required. 2-letter US state/territory code to partition the pull (e.g. CA, TX, NY). Pulls must be partitioned by state.

## `programSystem` (type: `string`):

Optional. Keep only facilities in this EPA program system (e.g. NPDES, AIR, RCRA, ICIS). Applied to delivered records.

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

Maximum records delivered and billed. You are billed only for records delivered.

## Actor input object example

```json
{
  "maxRecords": 500
}
```

# Actor output Schema

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

The delivered EPA facility records.

# 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 = {
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/epa-facility-compliance-records").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 = { "maxRecords": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/epa-facility-compliance-records").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 '{
  "maxRecords": 500
}' |
apify call nexgensignal/epa-facility-compliance-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/epa-facility-compliance-records"
        }
    }
}

```

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/Y0jsLErQXX8IHFwEc/builds/WeUftnWPvAqNZTHgV/openapi.json