EPA ECHO

EPA ECHO facility, compliance, and enforcement-case digests

This Actor fetches public EPA ECHO facility/compliance/enforcement pages from targets[] and emits source-linked digest rows for EHS and diligence research. Public ECHO only.

Not legal or environmental advice. Not FDA warning letters. Not a complete multi-media inspection. Unofficial research on public records.

from $8.00 / 1,000 EPA enforcement digest row ($0.008 per delivered apify-default-dataset-item). No Actor Start. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

Open EPA ECHO Enforcement Scraper on Apify

EPA ECHO Enforcement Scraper, not a neighboring Actor

Use this page for this Actor’s job. Use FDA Warning Letters Scraper for FDA warning-letter digests; Use Status Page Incident Digest Monitor for Vendor incidents; Use NHTSA Recall Scraper for NHTSA recalls/complaints.

Store ID: taroyamada/epa-enforcement-digest. Respect source terms, robots.txt, and rate limits.

Use cases

• Facility/registry watches
• Enforcement-case text diffs
• Scheduled snapshotKey EHS boards

How is EPA ECHO Enforcement Scraper different from FDA Warning Letters Scraper and Status Page Incident Digest Monitor?

EPA ECHO Enforcement Scraper (taroyamada/epa-enforcement-digest): This Actor fetches public EPA ECHO facility/compliance/enforcement pages from targets[] and emits source-linked digest rows for EHS and diligence research. Public ECHO only. Not legal or environmental advice. Not FDA warning letters. Not a complete multi-media inspection. Unofficial research on public records. FDA Warning Letters Scraper is for FDA warning-letter digests (input feeds / watchTerms; FDA public warning-letter feeds; warning-letter digest rows). Not ClinicalTrials.gov or HHS OCR. Status Page Incident Digest Monitor is for Vendor incidents (input status page feeds; status.io-style pages; incident digest rows). Not EPA ECHO facilities. NHTSA Recall Scraper is for NHTSA recalls/complaints (input vehicle feeds; NHTSA public APIs; recall digest rows). Not CPSC consumer-product recalls.

What input is required?

Live required fields: targets. Published exampleRunInput is shown below. Summary-first monitoring for EPA ECHO enforcement and compliance risk

Published Store example run input (omitted fields take schema defaults):

{
  "targets": [
    {
      "id": "basf-texas",
      "name": "BASF Texas EPA Watch",
      "criticality": "high",
      "owner": "EHS / Compliance",
      "tags": "chemical,texas,epa",
      "facilityName": "BASF",
      "state": "TX",
      "facilitySearch": {
        "nameMatchMode": "CONTAINS"
      },
      "complianceScreener": {
        "years": 5,
        "activeOnly": true,
        "nameMatchMode": "CONTAINS",
        "evidenceLimit": 5
      }
    },
    {
      "id": "delaware-afr-feed",
      "name": "Delaware Administrative Formal Cases",
      "criticality": "high",
      "owner": "Legal / Compliance",
      "tags": "case-feed,delaware,enforcement",
      "caseSearch": {
        "state": "DE",
        "caseCategory": "AFR",
        "fromDate": "01/01/2024",
        "toDate": "12/31/2024",
        "evidenceLimit": 5
      }
    }
  ],
  "delivery": "dataset",
  "datasetMode": "changes_only",
  "snapshotKey": "epa-enforcement-store-example",
  "diffMode": "line_summary",
  "summaryMaxLines": 12,
  "maxEvidenceItems": 5,
  "concurrency": 2,
  "batchDelayMs": 500,
  "dryRun": false
}

Run EPA ECHO Enforcement Scraper on Apify

How do dataset, webhook, and dry-run delivery work?

delivery defaults to dataset on the live schema. Dataset output is the billable surface when rows are written. webhookUrl is used when delivery is webhook (and typically not during dryRun). dryRun true validates or samples without the usual dataset/webhook side effects described on the Store schema. datasetMode can limit emits to changes_only / changed_only / action_needed versus all. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

What does a result contain?

Published README Output Example / Sample Output JSON. Treat README samples as illustrations, not a live coverage guarantee. There is no published output JSON schema on the Store page.

How is EPA ECHO Enforcement Scraper priced?

Billing is pay per event. The live Store card is from $8.00 / 1,000 EPA enforcement digest row ($0.008 per delivered apify-default-dataset-item). No Actor Start. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE. Current PPE:

The published README Cost block is stale versus the live Store pricing tab. README Cost still quotes actor-start $0.01. README Cost quotes dataset-item $0.003; live primary is $0.008 (EPA enforcement digest row). Live: EPA enforcement digest row $0.008. This page quotes live PPE only.

from $8.00 / 1,000 EPA enforcement digest row ($0.008 per delivered apify-default-dataset-item). No Actor Start. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

See EPA ECHO Enforcement Scraper pricing on Apify

Limits to keep in mind

• targets required
• Public ECHO HTML/APIs
• maxEvidenceItems cap
• Not professional advice
• Respect source terms, robots.txt, and rate limits.

Open EPA ECHO Enforcement Scraper on Apify

Related pages

• FDA Warning Letters Scraper — FDA letters, not EPA ECHO.
• NHTSA Recall Scraper — Vehicles, not ECHO facilities.
• Status Page Incident Digest Monitor — SaaS incidents, not EPA.
• EPA ECHO Facility Watch — enforcement and compliance alerts.
• FTC Enforcement Case Delta & Report — FTC cases, not ECHO.
• Tools