
Environmental Compliance Monitor — EPA ECHO
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.
Environmental Compliance Monitor — EPA ECHO returns 17 documented output fields, including matchedQuery, facilityName, registryId, city and state. Every field carries a declared type, a written description and an example value. 26 runs are recorded on Apify.
- 17
- Output fields
- 2
- Inputs
- 26
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| matchedQuery | stringnull | The query this row matched. | amazon product scraper |
| facilityName | stringnull | Facility Name as recorded for this row. | <facilityName> |
| registryId | stringnull | Identifier issued by the registry. | <registryId> |
| city | stringnull | City name. | Austin |
| state | stringnull | State, province or region name. | active |
| county | stringnull | County name. | Travis |
| complianceRisk | stringnull | Compliance Risk as recorded for this row. | <complianceRisk> |
| complianceNote | stringnull | Note about a compliance finding. | <complianceNote> |
| significantNoncompliance | booleannull | Whether the source records significant non-compliance. | true |
| inspectionCount | numbernull | How many inspections were recorded. | 0 |
| lastInspectionDate | stringnull | Date of the most recent inspection. | <lastInspectionDate> |
| penaltyCount | numbernull | How many penalties were recorded. | 0 |
| lastPenaltyDate | stringnull | Date of the most recent penalty. | <lastPenaltyDate> |
| caaHighPriorityViolation | booleannull | Whether a high-priority violation is recorded. | true |
| caaLastPenaltyAmount | numbernull | Monetary amount of the most recent civil penalty. | 0 |
| status | stringnull | Outcome recorded for this row. | ok |
| verdict | stringnull | The Actor's conclusion for this row, stated in words. | pass |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"matchedQuery": "amazon product scraper",
"facilityName": "<facilityName>",
"registryId": "<registryId>",
"city": "Austin",
"state": "active",
"county": "Travis",
"complianceRisk": "<complianceRisk>",
"complianceNote": "<complianceNote>"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| facilities | arrayrequired | Facility/company names to check, each with an optional state to narrow results. Example: [{"facilityName": "Apple", "state": "CA"}] |
| maxResultsPerFacility | integeroptional | How many matched facility records to return per query. |
04 — run
Run Environmental Compliance Monitor on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
15 of 17 fields described
- What does Environmental Compliance Monitor — EPA ECHO return?
- It returns 17 documented output fields: matchedQuery, facilityName, registryId, city, state, county, complianceRisk, complianceNote, significantNoncompliance, inspectionCount, lastInspectionDate and penaltyCount. Each field declares its type, a description of what it holds, and an example value. The remaining 5 are listed in the output schema below.
- What input does Environmental Compliance Monitor — EPA ECHO require?
- facilities is required. A further 1 input is optional. The full input schema, with types and defaults, is below.
- Does Environmental Compliance Monitor — EPA ECHO need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Environmental Compliance Monitor — EPA ECHO?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.