Envirofacts data service

Envirofacts is the EPA's long-running integration layer: one queryable system that joins facility records from roughly 20 separate environmental program systems. Instead of querying TRI for toxics releases, RCRAInfo for hazardous-waste handlers, ICIS-AIR for air permits, SDWIS for drinking water or FRS for master facility identifiers separately, you hit one REST endpoint set that resolves a named site across them.

The cataloged example is the US EPA Envirofacts facility database in the paper-products slice, described as queryable through a free REST data service that resolves individual paper mills - 353 facility records match the string 'PAPER' in the TRI facility table alone, which holds tens of thousands of sites inside millions of records overall.

Responses come in six formats: JSON (REST API), CSV, Excel, Parquet, XML and HTML, so the same query can feed a pipeline or a spreadsheet. Two operational limits matter: updates land monthly, and no rate limit is documented beyond a 15-minute execution cap per request.

Facility identity is the hardest join in environmental data. Programs assign their own identifiers, so a mill's TRI record and its air permit often share no key until FRS ties them together:

• No-key access lowers integration cost. With no authentication step, a proof-of-concept takes minutes; vendors reselling 'environmental facility data' are usually repackaging this free service.
• Cross-program joins come built in. Because Envirofacts integrates the programs up front, you avoid stitching five APIs with five identifier schemes.
• Monthly refresh caps timeliness. Compliance events newer than the last monthly load are not here; enforcement trackers need faster sources.

1. Resolve a known facility by name. Querying 'PAPER' should return facility rows (353 match in the cataloged slice); failure to resolve names means the mirror dropped the name-matching layer.
2. Confirm program coverage. Ask which of TRI, RCRAInfo, ICIS-AIR, SDWIS and FRS the source integrates; partial mirrors lose the cross-program value.
3. Check format parity. The native service returns JSON, CSV, Excel, Parquet, XML and HTML - a vendor offering only HTML tables is adding scraping risk.

Where to see it in context: commodity-chemicals data, paper-products data.

• official-api - the provider-operated API pattern this service exemplifies, with documentation and stable endpoints rather than scraped pages.
• paper-mill-facility-records - the industry-specific application where named-facility resolution matters most in this catalog.
• toxics-release-inventory-tri - the largest single program feeding Envirofacts, with tens of thousands of reporting sites.