# US Industrial Facility & Public Contact Discovery (`neurolab_works/us-industrial-facility-discovery`) Actor

Discover US industrial facilities using official EPA data with normalized facility records and public regulatory contact information when available.

- **URL**: https://apify.com/neurolab\_works/us-industrial-facility-discovery.md
- **Developed by:** [Neuro Lab](https://apify.com/neurolab_works) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$7.50 / 1,000 industrial facility results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Industrial Facility & Public Contact Discovery

**Disclaimer:** This is an independent, unofficial tool and is not affiliated with, sponsored by, or endorsed by the U.S. EPA. Data is obtained from official EPA public data sources.

**What it does:** Queries EPA's official TRI (Toxics Release Inventory) registry, normalizes the result into a stable schema, deduplicates by facility, and includes each facility's public regulatory contact information when the registry publishes one.

**Who it's for:** Sales teams selling into US industrial/chemical-handling facilities (safety equipment, environmental compliance services, industrial supplies), and researchers who need a reliable, structured view of regulated facilities without hand-parsing EPA's own API quirks.

**Data source:** EPA's TRI (Toxics Release Inventory), via data.epa.gov Envirofacts -- the official US government registry of facilities that manufacture, process, or use listed toxic chemicals above federal reporting thresholds.

**What makes it useful:**

- Stable, normalized schema across every facility -- no need to learn EPA's own field names or handle its upstream quirks.
- Deduplicated by facility -- a multi-branch operator shows up once, with an establishment count.
- Public named contact, email, and phone included when the official registry publishes them.

**Important -- what `public_contact_name` means:** `public_contact_name` is a **public EPA/regulatory contact** -- the person EPA's own registry lists for the facility, typically for regulatory correspondence. It is **not necessarily a buyer, decision maker, or procurement contact**, and no purchasing role or authority is implied or claimed. `public_contact_role` is always returned as `null` because EPA's registry does not publish a title/role for this contact.

### Input example

```json
{
  "state": "TX",
  "keyword": null,
  "limit": 10
}
```

### Output example

```json
{
  "facility_name": "HEP JAVELINA SMR LLC",
  "operator": "HEP JAVELINA SMR LLC",
  "facility_type": "Industrial facility",
  "industry_activity": "Petroleum refining",
  "state": "TX",
  "city": "Corpus Christi",
  "address": "1000 EXAMPLE RD",
  "public_contact_name": "DENNIS WILLIAMS",
  "public_contact_role": null,
  "public_email": null,
  "public_phone": null,
  "source": "EPA TRI",
  "source_id": "12345TXEXAMPLE",
  "freshness": "Live EPA Envirofacts query on each run."
}
```

### Pricing

Pay-per-event: **$0.0075 USD per `facility_result`** delivered. You are only charged for normalized, deduplicated records actually returned to your dataset -- never for the run itself, and never for a failed or empty run.

### Data freshness

Every run queries EPA's live Envirofacts API directly -- results reflect EPA's currently published TRI data at the moment you run the Actor.

### Limitations

- Covers EPA TRI-listed facilities only -- not a general US business directory.
- `keyword` matches only against facility name, never address or activity text.
- Public contact fields are only as complete as EPA's own registry -- a meaningful share of facilities have no named contact, email, or phone on file.
- `public_contact_name` reflects EPA's regulatory point of contact only -- never a confirmed purchasing role.

### Contact/support

Built and maintained by NeuroLab Works. For issues or questions, use the Actor's Issues tab on Apify Console.

# Actor input Schema

## `state` (type: `string`):

2-letter US state abbreviation, e.g. 'TX', 'CA', 'OH'.

## `keyword` (type: `string`):

Optional keyword matched only against the facility name (never the address) -- avoids false-positive matches. Leave empty to return the state's facilities in registry order.

## `limit` (type: `integer`):

Maximum number of deduplicated facility records to return (and be charged for).

## Actor input object example

```json
{
  "state": "TX",
  "limit": 10
}
```

# Actor output Schema

## `facilityResults` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "state": "TX"
};

// Run the Actor and wait for it to finish
const run = await client.actor("neurolab_works/us-industrial-facility-discovery").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "state": "TX" }

# Run the Actor and wait for it to finish
run = client.actor("neurolab_works/us-industrial-facility-discovery").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "state": "TX"
}' |
apify call neurolab_works/us-industrial-facility-discovery --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neurolab_works/us-industrial-facility-discovery"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Qrq5Q3k14icEtNtIh/builds/7KNEHhZoRLTezn5uj/openapi.json