Skip to content
The Register

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.

Run it on ApifyPay per result · no subscription
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.

FieldTypeWhat it holdsExample
matchedQuerystringnullThe query this row matched.amazon product scraper
facilityNamestringnullFacility Name as recorded for this row.<facilityName>
registryIdstringnullIdentifier issued by the registry.<registryId>
citystringnullCity name.Austin
statestringnullState, province or region name.active
countystringnullCounty name.Travis
complianceRiskstringnullCompliance Risk as recorded for this row.<complianceRisk>
complianceNotestringnullNote about a compliance finding.<complianceNote>
significantNoncompliancebooleannullWhether the source records significant non-compliance.true
inspectionCountnumbernullHow many inspections were recorded.0
lastInspectionDatestringnullDate of the most recent inspection.<lastInspectionDate>
penaltyCountnumbernullHow many penalties were recorded.0
lastPenaltyDatestringnullDate of the most recent penalty.<lastPenaltyDate>
caaHighPriorityViolationbooleannullWhether a high-priority violation is recorded.true
caaLastPenaltyAmountnumbernullMonetary amount of the most recent civil penalty.0
statusstringnullOutcome recorded for this row.ok
verdictstringnullThe 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

InputTypeDescription
facilitiesarrayrequiredFacility/company names to check, each with an optional state to narrow results. Example: [{"facilityName": "Apple", "state": "CA"}]
maxResultsPerFacilityintegeroptionalHow 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.

Open on Apify ↗

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.