# EPA TRI Scraper: Toxic Releases by Facility & Chemical (`thoob/tri-toxic-release-feed`) Actor

Clean, flat EPA Toxics Release Inventory records from the official Envirofacts API: facility, chemical, CAS, release amounts by medium, year, and location, with a what-changed-since-last-run mode. Billed only per delivered record, no start fee.

- **URL**: https://apify.com/thoob/tri-toxic-release-feed.md
- **Developed by:** [Pono Data](https://apify.com/thoob) (community)
- **Categories:** Developer tools, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 release records

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/platform/actors/running/actors-in-store#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

## EPA TRI Toxic Release Feed

Clean, flat toxic-release records from the official EPA Toxics Release Inventory, pulled from the Envirofacts REST service. Filter by US state and reporting year, get one useful row per facility-chemical-year report, and run a changes-only mode that returns just what is new or revised since your last run.

You pay only for a delivered record that carries actual release amounts. Filtered-out rows, unchanged rows in changes mode, malformed records, and forms that reported no quantified release for any medium all cost nothing, and there is no per-run start fee. The release amounts are the product, so a record without them is never billed.

### What a record is

One flat row per TRI reporting form (one facility's report of one chemical for one year), assembled from four Envirofacts tables so you do not have to join them yourself:

- facility: `facilityName`, `streetAddress`, `city`, `county`, `state`, `zipCode`, `fipsCode`, `epaRegion`, `latitude`, `longitude`, `parentCompany`, `isFederalFacility`
- chemical: `chemicalName`, `casRegistryNumber`, `unitOfMeasure`, and the EPA hazard flags `isCarcinogen`, `isPfas`, `isPbt`, `isMetal`
- releases: `totalRelease` and `releasesByMedium` (one entry per environmental medium that reported a quantity, such as fugitive air, stack air, surface water, landfill, with its amount)
- identity and year: `docCtrlNum`, `triFacilityId`, `reportingYear`
- provenance: `sourceUrl`, `retrievedAt`, `confidence`, `dataSource`, `jurisdiction`, and in changes mode `changeType`

Every value is copied from an Envirofacts record. The one derivation is decoding EPA's packed degrees-minutes-seconds coordinates into decimal degrees, and that is only done when the packed value is structurally valid. Nothing is guessed.

### Sample output

A real slice, Colorado facilities reporting for 2022 (abbreviated):

| facilityName | state | chemicalName | casRegistryNumber | reportingYear | sourceUrl |
|---|---|---|---|---|---|
| DHARMACON INC | CO | Acetonitrile | 75-05-8 | 2022 | data.epa.gov/efservice/tri\_reporting\_form/doc\_ctrl\_num/1322220634909/JSON |

Each `sourceUrl` is the form's own record in the Envirofacts REST service, so any value can be checked against the source.

### Two modes

- **full**: every reporting form matching your filter.
- **changes**: only forms that are new, or whose release total or medium breakdown changed since this account's last run. The state is tracked per account, so it is your timeline. The first changes run has no baseline, so it returns everything matching once, then tracks deltas from there.

### Filters

- **state**: a two-letter US state or territory code, applied to the facility (CO, TX, CA, PR, and the rest). Leave empty for all states.
- **reportingYear**: a TRI reporting year, applied to the form. Leave empty for all years, which returns far more records.
- **maxRecords**: a cap on how many records a run delivers and bills. 0 means no cap; the platform spend cap is honored regardless.

State and year are applied server-side by the Envirofacts service.

### What to expect

- TRI covers more than 20,000 industrial and federal facilities reporting on a list of over 600 toxic chemicals, going back to 1987. A state-and-year filter narrows that to the slice you care about (Colorado 2022, for example, is a few hundred forms).
- The raw Envirofacts API is public and free directly from the EPA. What this actor sells is the assembled record: the four-table join, the release-by-medium aggregation, the decoded coordinates, the CAS lookup, and the per-account change feed, so you do not have to walk the normalized tables or diff them yourself.
- A state-and-year pull is a few dollars; a periodic changes feed is pennies a run.

### Source and scope

- Source: the official EPA Envirofacts REST service (`data.epa.gov/efservice`), public domain, no key, no anti-bot, paged with a declared identifying User-Agent.
- Scope: United States facilities and subjects only. Every row is stamped `jurisdiction=US`.
- These are public reports filed by regulated facilities about their own operations, at the business level. There is no consumer personal data here.
- This is a data tool, not legal, environmental, investment, or regulatory advice. A TRI report is a self-reported filing, not a finding.

### See also

More clean, pay-only-for-results data tools from Pono Data:

- [Clinical Trials Feed](https://apify.com/thoob/clinical-trials-feed) - studies, sponsors, and changes from ClinicalTrials.gov
- [Federal Spending Feed](https://apify.com/thoob/federal-spending-feed) - US federal award records with a changes mode

Full catalog: https://apify.com/thoob

# Actor input Schema

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

Two-letter US state or territory code to filter facilities by (for example CO, TX, CA, PR). Applied server-side on the facility. Leave empty to match facilities in any state.

## `reportingYear` (type: `string`):

TRI reporting year to filter by (for example 2022). Applied server-side on the reporting form. Leave empty to match every reporting year, which returns far more records.

## `mode` (type: `string`):

full returns every reporting form matching your filter. changes returns only forms that are new, or whose release total or medium breakdown changed since this account's last run, tracked per account. The first changes run has no baseline, so it returns everything matching once, then tracks deltas.

## `maxRecords` (type: `integer`):

Safety cap on how many reporting forms this run delivers and bills. The default of 1000 keeps a first run predictable, since an uncapped run on a wide query bills every form it finds in one go. Forms past the cap are not dropped, they are delivered on a later run and never billed twice. Set 0 for no cap once you know the volume you want. The platform spend cap (ACTOR\_MAX\_TOTAL\_CHARGE\_USD) is honored regardless.

## `pageSize` (type: `integer`):

How many reporting forms to request per Envirofacts page (1 to 1000). Larger pages are fewer requests; the default is a polite middle.

## Actor input object example

```json
{
  "state": "CO",
  "reportingYear": "2022",
  "mode": "full",
  "maxRecords": 1000,
  "pageSize": 200
}
```

# Actor output Schema

## `records` (type: `string`):

One row per facility-chemical-year reporting form matching your filter.

# 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": "CO",
    "reportingYear": "2022"
};

// Run the Actor and wait for it to finish
const run = await client.actor("thoob/tri-toxic-release-feed").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": "CO",
    "reportingYear": "2022",
}

# Run the Actor and wait for it to finish
run = client.actor("thoob/tri-toxic-release-feed").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": "CO",
  "reportingYear": "2022"
}' |
apify call thoob/tri-toxic-release-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=thoob/tri-toxic-release-feed",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/TvuAIU2nKFDJuurXZ/builds/dScRGapcIDsOsDfJC/openapi.json