Pull a Detailed Facility Report (DFR) for a specific NPDES or SDWA-regulated facility from EPA ECHO
domain: echo.epa.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the facility's ECHO registry ID or permit/PWSID via a prior facility search (CWA or SDW REST service)
Call the primary get_dfr endpoint with the ID and output=JSON to retrieve the full cross-program report
Optionally call narrower section-specific DFR endpoints if only part of the report (e.g., enforcement history) is needed
Parse the returned compliance, enforcement, and inspection history fields for the facility
Cross-check field meanings against the DFR Data Dictionary before using values in downstream logic
Known gotchas
get_dfr aggregates data from multiple EPA systems (ICIS-NPDES, SDWIS, RCRAInfo); a facility regulated under only one program returns empty sections for the others
DFR compliance/enforcement history is limited to the past ten years per EPA documentation
The Data Dictionary is maintained separately from the API and can lag actual API/field changes
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?