# Environmental Compliance Monitor — EPA ECHO (`alaudinburki/epa-compliance-monitor`) Actor

EPA environmental compliance history per facility name: Significant Noncompliance flags, Clean Air Act high-priority violations, and penalty history — from free official EPA ECHO data. Word-boundary matched, not a raw substring search.

- **URL**: https://apify.com/alaudinburki/epa-compliance-monitor.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 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.

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

## Environmental Compliance Monitor — EPA ECHO

ESG/compliance teams, real-estate/M\&A due diligence, and insurers
currently check EPA compliance history by hand, on ECHO's own clunky UI.
Free, public, keyless. This turns a facility/company name into a
compliance summary, ranked by risk.

### The verdict that matters

| Risk | Meaning |
|---|---|
| `significant_noncompliance` | EPA's own "Significant Noncompliance" flag is set — active, serious |
| `high_priority_violation` | Clean Air Act High Priority Violation flag is set |
| `penalty_history` | No active flag, but has a penalty on record |
| `clear` | No significant noncompliance, HPV, or penalty flags found |

### Input

```json
{ "facilities": [{ "facilityName": "Apple", "state": "CA" }] }
```

### Sample output

```json
{
  "facilityName": "APPLE INC (AP)",
  "city": "CUPERTINO",
  "state": "CA",
  "complianceRisk": "clear",
  "complianceNote": "No significant noncompliance, high-priority violation, or penalty flags found.",
  "significantNoncompliance": false,
  "inspectionCount": 3
}
```

### Typical uses

- **ESG / compliance due diligence** — check a company's environmental
  compliance record before a partnership, investment, or acquisition.
- **Real estate / industrial site diligence** — check a property or
  tenant's compliance history before a lease or purchase.
- **Insurance underwriting** — environmental compliance flags are real
  underwriting signal for certain policies.

### Pricing

**$0.003 per facility record.**

### ⚠️ Read before you act — two real quirks found live, both handled

- **ECHO's own search is a raw substring match, not word-boundary.**
  Verified live: searching "Apple" also returned "Appleton," "Applegate,"
  and "Appleby" facilities alongside real Apple Inc. sites. This actor
  filters to real word-token matches before returning results — you will
  not see those false positives.
- **ECHO's documented `rows` limit parameter is not honored server-side**
  — verified live, a request for 5 rows against an 815-match query
  returned all 815. This actor fetches the full result set and truncates
  client-side to your `maxResultsPerFacility` after word-boundary
  filtering, so the limit is enforced correctly regardless.
- **A company name often matches multiple physical facilities** (different
  locations, subsidiaries, DBAs) — each row is one facility, not one
  company; check `registryId`/city/state to identify the specific site.

### FAQ

- **Do I need an API key?** No — EPA ECHO's API is free and keyless.
- **Why do I see multiple rows for the same company?** Large companies
  have many EPA-registered facilities (different locations, subsidiaries,
  "doing business as" names) — this is expected, not a duplicate.
- **What programs does this cover?** Clean Air Act, Clean Water Act, and
  RCRA (hazardous waste) compliance data, as ECHO itself tracks it.

### Related actors

- **Drug & Device Recall Monitor** — the same official-database,
  classified-severity pattern, for FDA recalls instead of environmental compliance.
- **Financial Complaint Monitor** — the same company-lookup-summarized
  pattern, for CFPB financial complaints.

# Actor input Schema

## `facilities` (type: `array`):

Facility/company names to check, each with an optional state to narrow results. Example: \[{"facilityName": "Apple", "state": "CA"}]

## `maxResultsPerFacility` (type: `integer`):

How many matched facility records to return per query.

## Actor input object example

```json
{
  "facilities": [
    {
      "facilityName": "Apple",
      "state": "CA"
    }
  ],
  "maxResultsPerFacility": 25
}
```

# Actor output Schema

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

Matched facilities, ranked by compliance risk.

## `qualityReport` (type: `string`):

Facilities queried, risk breakdown, and problems.

# 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 = {
    "facilities": [
        {
            "facilityName": "Apple",
            "state": "CA"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/epa-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 = { "facilities": [{
            "facilityName": "Apple",
            "state": "CA",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/epa-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 '{
  "facilities": [
    {
      "facilityName": "Apple",
      "state": "CA"
    }
  ]
}' |
apify call alaudinburki/epa-compliance-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/epa-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/BFSJucyx8y7wf1OXO/builds/X38pN3C8k2QT4Rr5Z/openapi.json