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

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

Sample output

{
  "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.

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Environmental Compliance Monitor — EPA ECHO declares all 17 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Environmental Compliance Monitor include matchedQuery, facilityName, registryId, city, state and county.
• Environmental Compliance Monitor needs no API key, login or account of any kind before its first run.
• Every one of Environmental Compliance Monitor's 2 inputs is optional, so it runs with no configuration at all.
• Environmental Compliance Monitor documents state as: Current state of this record in its own lifecycle.
• Every number published about Environmental Compliance Monitor is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Environmental Compliance Monitor is filed under developer tools and business so that it is found by the people looking for that job, not by its internal name.

Limitations

• Environmental Compliance Monitor reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.