US Compliance & Regulatory Data API
Pricing
from $0.005 / actor start
US Compliance & Regulatory Data API
Search US enforcement, recall, sanctions, bank, complaint, disaster, and energy records in one run. Find public-risk signals faster.
Pricing
from $0.005 / actor start
Rating
0.0
(0)
Developer
kane liu
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
10 days ago
Last modified
Categories
Share
US Regulatory & Compliance Data Search
Search 33 US regulatory and compliance data sources in one query — EPA, NHTSA, OFAC, FDIC, Treasury, CFPB, FEMA, EIA, NREL, NRC, CAISO, and more.
- ✅ Search 33 US regulatory and compliance data sources across environmental, vehicle safety, financial, consumer, disaster, and energy datasets
- ✅ Get EPA facility and emissions records, NHTSA recalls and complaints, OFAC and FDIC records, CFPB complaints, FEMA records, and energy datasets in one workflow
- ✅ Covers 3 environmental sources, 3 vehicle-safety sources, 5 financial and regulatory sources, 1 consumer-protection source, 2 disaster sources, and 19 energy sources
- ✅ Export results as Excel, CSV, or JSON, or connect it to Apify MCP, API, Make, n8n, and Zapier
- ✅ Current Apify listing is pay per usage, so you can start with small runs and scale only when the workflow proves useful
US public-risk and compliance data is spread across many agencies. Environmental records sit with EPA. Vehicle-safety signals sit with NHTSA. Sanctions, banking, and Treasury data live elsewhere. Consumer complaints, disaster declarations, flood-insurance claims, and energy market records all come from different systems. This Actor combines those active public datasets into one search layer so you can run one query across the sources you care about, then export or automate the results.
What you can do with it
1. Search environmental, sanctions, bank, and complaint records for a company
Many compliance workflows start with a company or counterparty name. You may want to know whether the entity shows up in EPA facility or emissions records, OFAC sanctions data, FDIC data, or CFPB complaints.
This Actor lets you search those public sources together instead of opening each agency system separately.
What you enter:
| What | Example |
|---|---|
| Search term | Exxon, Wells Fargo, Boeing, or Tesla |
| Categories | Environmental + financial/regulatory + consumer protection |
| How many results | 50 per source |
What you get back:
| Source | Example fields |
|---|---|
| EPA TRI / GHG / drinking water | Facility name, state, chemical or emissions metadata, reporting year |
| OFAC / FDIC / Treasury | Entity or institution name, financial or sanctions metadata |
| CFPB complaints | Company, product, issue, complaint metadata |
This is useful for compliance screening, vendor review, onboarding checks, due diligence, and AI assistants that need one search layer across multiple US public-risk datasets.
2. Search EPA records for environmental and emissions workflows
The environmental side of this Actor includes EPA Toxic Release Inventory, greenhouse-gas reporting, and drinking-water-system records. That makes it useful when you need facility-level context, emissions-related records, or public water-system information from active EPA datasets.
You can use it for company-level review, location-level research, or environmental signal discovery.
What you enter:
| What | Example |
|---|---|
| Search term | Houston, DuPont, chemical plant, or water system |
| Categories | Environmental only |
| How many results | 100 per source |
What you get back:
| Source | Example fields |
|---|---|
| EPA TRI | Facility name, chemical, release values, reporting year |
| EPA GHG | Facility name, emissions values, year, reporting metadata |
| EPA drinking water | Water system name, state, service or compliance metadata |
This is useful for ESG support, facility research, environmental monitoring, location screening, and workflows that need raw EPA public records rather than a generic summary.
3. Search NHTSA recalls, complaints, and VIN data for vehicles
The vehicle-safety slice of this Actor includes NHTSA recalls, complaints, and VIN decoder data. That means you can look up a vehicle make, model, year, or identifier and pull related public-safety records from the active NHTSA source set.
This is useful for fleets, vehicle research, dealership workflows, safety reviews, or any assistant that needs recall and complaint discovery in one place.
What you enter:
| What | Example |
|---|---|
| Search term | Toyota Camry, Ford F-150, or a VIN-related identifier |
| Categories | Vehicle safety only |
| How many results | 50 per source |
What you get back:
| Source | Example fields |
|---|---|
| NHTSA recalls | Recall title, affected vehicles, issue metadata, dates |
| NHTSA complaints | Complaint text, vehicle details, complaint metadata |
| NHTSA VIN decoder | Vehicle attributes tied to VIN decoding records |
This is useful for fleet oversight, pre-purchase checks, service operations, automotive research, and compliance workflows that need one NHTSA search layer instead of several separate lookups.
4. Search FEMA and energy datasets for location, infrastructure, and market context
Some workflows are location-based rather than company-based. You may want to search FEMA disaster declarations and NFIP claims for a place, then combine that with energy data from EIA, NREL, NRC, BLS, or CAISO to get more operational context.
This Actor includes both disaster and energy groups, which makes it useful for place-based risk and infrastructure research.
What you enter:
| What | Example |
|---|---|
| Search term | Houston, California, solar, natural gas, or reactor |
| Categories | Disaster + energy |
| How many results | 50 per source |
What you get back:
| Source | Example fields |
|---|---|
| FEMA disasters / NFIP claims | Disaster name, county or state, declaration or claims metadata |
| EIA / NREL / NRC / CAISO / BLS | Energy series, plant or resource metadata, market or price context, dates |
This is useful for site research, infrastructure monitoring, insurance context, energy-market discovery, and geographic risk workflows that need multiple public datasets in one run.
5. Use one Actor for mixed US public-risk discovery in AI and automation workflows
The main advantage of this Actor is not that it behaves like one perfect database. It does not. The advantage is that it gives you one search layer across several important US public-risk and compliance domains.
Instead of wiring EPA, NHTSA, OFAC, FDIC, CFPB, FEMA, EIA, NREL, NRC, and CAISO separately into your assistant or automation stack, you can use one Actor to handle the search step.
What you enter:
| What | Example |
|---|---|
| Search term | Boeing |
| Categories | Environmental + vehicle safety + financial/regulatory |
| How many results | 25 per source |
What your assistant or automation gets back:
| Source family | Returned data |
|---|---|
| Environmental | EPA facility, emissions, or water-system records |
| Vehicle safety | NHTSA recall, complaint, or VIN-related records |
| Financial/regulatory | OFAC, FDIC, Treasury records |
| Consumer / disaster / energy | Additional public-risk records if those groups are enabled |
This is useful for internal compliance assistants, scheduled monitoring, risk research, public-data automation, and spreadsheet workflows that need one US regulatory-data entry point.
How to use (no code required)
- Click "Try for Free" at the top of this page
- Type one or more search terms — company names, locations, vehicle models, sanctions targets, facility keywords, or energy terms
- Choose which categories to search:
- environmental
- vehicle safety
- financial and regulatory
- consumer protection
- disaster
- energy
- Set how many results you want per source
- Click Start — the Actor queries the enabled US public-data sources and returns the results in the Dataset tab
You can then export the results as Excel, CSV, or JSON.
Because the Actor is listed as pay per usage, it is easy to begin with a small exploratory run, check which source families matter for your workflow, and then scale from there.
What you get back
Each result comes back as one dataset row. The exact columns vary by source family, because an EPA facility record, a vehicle recall, a sanctions entry, a FEMA disaster record, and an energy-market record do not share the same schema.
Across the dataset, you will typically see:
nametypestatuscountryauthority_product_id_source_search_term_collected_at
Then source-specific fields such as:
- EPA: facility, emissions, chemical, location, reporting metadata
- NHTSA: vehicle, recall, complaint, VIN-related metadata
- OFAC / FDIC / Treasury: sanctions, bank, or Treasury-related metadata
- CFPB: complaint product, issue, company, complaint details
- FEMA: disaster declarations or flood-insurance claims metadata
- Energy: production, pricing, forecast, plant, resource, or market-series fields
Every row keeps the source label and matched search term, so it is easy to separate source families, filter by authority, and move the results into downstream research or automation workflows.
Coverage
This Actor currently searches 33 active US regulatory and compliance data sources:
| Category | Count | Coverage |
|---|---|---|
| Environmental | 3 | EPA TRI, greenhouse-gas reporting, and drinking-water systems |
| Vehicle safety | 3 | NHTSA recalls, complaints, and VIN decoder |
| Financial and regulatory | 5 | OFAC, FDIC, and Treasury datasets |
| Consumer protection | 1 | CFPB complaints |
| Disaster | 2 | FEMA disaster declarations and NFIP claims |
| Energy | 19 | EIA, BLS, NRC, NREL, and CAISO datasets |
The current active maps in the Actor are:
3 environmental sources3 vehicle-safety sources5 financial and regulatory sources1 consumer-protection source2 disaster sources19 energy sources
That matters because this Actor is not one unified enforcement database. It is a combined public-data discovery layer across several different US regulatory and operational source families.
Pricing
This Actor is currently listed on Apify as pay per usage.
The safest place to confirm the live commercial terms is the pricing tab:
If you want to keep runs small, the easiest approach is to:
- search only the categories you actually need
- start with one or two search terms
- lower
maxResultsPerSourcefor exploratory runs
Connect to your tools
You can use this Actor directly in the Apify UI, or connect it to automation and AI workflows:
| Platform | How to connect |
|---|---|
| Apify UI | Run it directly and export results |
| Apify API | Trigger runs and fetch datasets programmatically |
| Make.com | Use the Actor ID lentic_clockss/us-compliance-search |
| n8n / Zapier / ChatGPT / Claude | Use the same Actor ID via Apify MCP or API |
Related Actors
- US Financial Data Search — US finance and institution datasets
- Global Regulatory & Compliance Search — cross-jurisdiction regulatory discovery
- Global Sanctions Screening — multi-country sanctions screening
- EU Health & Compliance Search — EU regulatory and compliance datasets
→ Browse all Actors: apify.com/lentic_clockss
Also Available
- Direct API:
https://opendata.best/api/v1/data - Postman Collection: Fork and test
- GitHub: Collection source files