EPA Facility Scraper — Violations & Penalties | $9.9/1K

EPA Facility Scraper — Violations, Enforcement & Penalties

Search US EPA regulated facilities by state. Returns compliance status, violation history, enforcement actions, and penalties across Clean Water Act, Clean Air Act, RCRA, and Drinking Water programs.

What it does

This actor extracts structured public data via official/public endpoints — no login, no API key required from you. Results are returned as clean JSON dataset items, one row per record, with a parse_confidence field for quality.

Use cases

• Lead generation, market research, and competitive intelligence.
• Feeding pipelines, dashboards, and AI agents with fresh structured data.
• Monitoring changes over time on a schedule.

Input

Provide the search/query parameters (see the input schema). Bound the run with maxItems.

Fields returned

Each record includes the facility name and address, registry ID, current compliance status, counts of recent violations and formal enforcement actions, total assessed penalties, the regulatory programs in scope (Clean Water Act, Clean Air Act, RCRA hazardous waste, Safe Drinking Water Act), and a parse_confidence score so you can filter on data quality.

Data source

Data comes from the EPA's official public compliance and enforcement records — the same authoritative source regulators publish — so results are accurate and require no credentials or scraping of locked pages.

Output

One dataset item per record with the key fields and parse_confidence. Export to JSON/CSV/Excel or pull via the Apify API/MCP. Schedule the actor to track compliance changes over time and feed alerts, dashboards, or AI agents with fresh structured environmental data.

💰 Pricing & how we compare

Pay-per-result (PPE): $9.90 / 1K facilities ($0.0099 each). You are billed per facility-record actually returned — plus the tiny apify-actor-start fee Apify waives for short runs. No subscription, no API key, no proxy fee on top.

Our edge: Official EPA public compliance data · violations + enforcement + penalties + programs · parse_confidence.

Pricing examples (pay only for what you get, minus Apify's 20%):

Volume	Cost
100 facilities	$0.99
1,000 facilities	$9.90
10,000 facilities	$99.00

How rivals price the same job (live Apify Store, checked 2026-06-09)

Actor	Their price	What they lack vs us
fortuitous_pirate/epa-echo-facilities	$0.01 / facility	we charm-undercut to $0.0099 + add parse_confidence
ryanclinton/epa-echo-search	$0.03 / result	3× our price
compute-edge/epa-echo-scraper	$0.004 / result	cheaper but 0 monthly users / unproven

Prices above are competitors' live Store prices at the time of writing; ours is set to sit just below the strongest comparable while returning richer, quality-scored data.

🤖 Use with AI agents (MCP)

This actor is agent-ready (category MCP_SERVERS). Point any MCP client (Claude Desktop, Cursor, n8n AI, LangGraph) at it:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?actors=bovi/epa-data-scraper",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Firmy Cz Scraper
• Gelbeseiten Directory
• Google Maps Leads
• Google Maps Scraper
• Hiring Signal Monitor
• Linkedin Profile Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.