Nuclear Plant Risk Report

Nuclear plant risk assessment for any U.S. facility, completed in under 90 seconds. Enter a plant name or location and the actor queries 8 public data sources in parallel — USGS, FEMA, NOAA, the Federal Register, Congress, OpenAQ, OpenCorporates, and Data.gov — then runs four calibrated scoring models to produce a composite Nuclear Risk Score (0–100) with a structured verdict and actionable recommendations.

This actor covers the full risk surface that regulators, insurers, and investors actually care about: seismic and natural hazard proximity, NRC regulatory compliance, environmental contamination indicators, and operator corporate transparency. No manual data gathering, no expensive subscriptions. One run produces a structured JSON report ready for risk management workflows, catastrophe models, or investment due diligence.

What data can you extract?

Why use Nuclear Plant Risk Report?

Manually compiling a nuclear facility risk profile means hours of searching across federal databases — the NRC ADAMS system, FEMA disaster declarations, USGS seismic catalogs, Congressional bill trackers, OpenCorporates, and state air quality portals. A junior analyst can spend a full workday producing a report that a regulatory consultant might charge $2,000–5,000 to deliver.

This actor automates the entire data collection and scoring pipeline in a single API call. Eight sources run in parallel, four scoring models apply consistent rubrics derived from nuclear safety engineering principles, and the output is machine-readable JSON ready for downstream processing.

• Scheduling — run monthly, quarterly, or after any seismic event to keep facility risk profiles current
• API access — trigger assessments from Python, JavaScript, or any HTTP client as part of a risk management platform
• Proxy rotation — data is fetched from public government APIs using Apify's infrastructure, so no IP management needed
• Monitoring — configure Slack or email alerts when risk scores exceed thresholds via Apify webhooks
• Integrations — connect to Zapier, Make, Google Sheets, Tableau, or custom dashboards for portfolio-level monitoring

Features

• 8-source parallel data collection — USGS earthquake catalog, FEMA disaster declarations, NOAA weather alerts, Federal Register rules/orders, Congressional bill tracker, OpenAQ air quality, OpenCorporates corporate registry, and Data.gov dataset catalog, all queried simultaneously
• Plant proximity seismic scoring — M5.5+ earthquakes score 15 points each; M4.0+ events score 6 points each; seismic sub-score capped at 40, aligned with NRC design basis thresholds
• FEMA disaster type differentiation — flood events (6 points each) and hurricane/typhoon events (10 points each) weighted separately due to their distinct threat vectors for cooling systems versus external power grids
• NOAA tornado missile hazard detection — tornado alerts add 8 points each; extreme-severity weather events add 5 points; specifically flagged as containment structure missile threats
• Compound hazard detection — identifies Fukushima-type co-occurring seismic-plus-flood risk and adds up to 10 additional points for compound scenarios
• Federal Register NRC compliance tracking — scans against 15 nuclear-specific keywords including reactor, criticality, meltdown, spent fuel, and containment; emergency/immediately-effective actions score 12 points each
• Congressional nuclear pressure monitoring — distinguishes between general nuclear bills (3 points) and restrictive legislation — bans, moratoriums, phase-outs (8 points each)
• Waste management regulatory scoring — tracks 10 waste-specific keywords including dry cask, transuranic, yucca, and repository; emergency waste/contamination actions score 12 points each
• Operator corporate structure analysis — counts holding entities, LLCs, trusts, dissolved companies, and multi-jurisdiction registrations; missing corporate records trigger a 25-point opacity penalty
• Composite weighted scoring — plant proximity 30%, regulatory compliance 30%, environmental contamination 25%, operator transparency 15%; composite drives the five-tier verdict from LOW_RISK to CRITICAL
• Actionable recommendations — each scoring model triggers specific recommendations when thresholds are breached, such as design basis reassessment, PSHA updates, or compliance remediation
• Sub-1000-record dataset retrieval — up to 1,000 items fetched per data source to ensure signal coverage without excessive cost

Use cases for nuclear plant risk assessment

Nuclear safety regulatory analysis

NRC staff, state utility regulators, and independent safety reviewers can use this actor to rapidly profile any licensed facility before an inspection or license renewal hearing. Rather than manually cross-referencing ADAMS, USGS, and FEMA databases, a reviewer can run a single query and receive a structured risk profile in 90 seconds. The actor's signal output maps directly onto NRC's defense-in-depth framework: seismic, external events, environmental, and organizational factors.

Emergency preparedness planning

County emergency management directors and FEMA regional staff responsible for nuclear facility emergency planning zones (EPZs) can assess natural hazard exposure for facilities within their jurisdiction. The actor surfaces concurrent threats — for example, a coastal facility subject to both seismic activity and hurricane flood risk — that require multi-hazard emergency response planning. Results can be scheduled to run automatically after any regional earthquake or major storm declaration.

Energy infrastructure investment due diligence

Private equity firms, infrastructure debt funds, and utility holding companies evaluating nuclear asset acquisitions or power purchase agreements need a rapid regulatory and environmental risk screen before commissioning full technical due diligence. This actor provides a structured first-pass risk signal covering all four dimensions — seismic, regulatory, environmental, and governance — within minutes rather than weeks, at a fraction of the cost of consultant-produced assessments.

Insurance and reinsurance catastrophe modeling

Insurers and reinsurers writing nuclear liability, property, or business interruption policies need to quantify compound hazard exposure. The actor's compound hazard detection logic — which specifically identifies co-occurring seismic and flood risk in the pattern of the Fukushima disaster — provides a structured signal for adjusting loss exceedance curves or exclusion language. Batch the actor across a portfolio of insured facilities for portfolio-level exposure mapping.

Environmental advocacy and community monitoring

Environmental organizations, anti-nuclear advocacy groups, and community coalitions near nuclear facilities can use this actor to systematically monitor waste management regulatory actions, contamination indicators from OpenAQ and Data.gov, and operator corporate transparency. The operator transparency scoring specifically flags holding-company structures that can obscure accountability in the event of a contamination incident.

Academic research and policy analysis

Researchers studying nuclear energy policy, environmental justice, or critical infrastructure risk can use this actor to rapidly generate comparable risk profiles across many facilities. The structured JSON output is suitable for statistical analysis, geographic visualization, and longitudinal tracking of regulatory and environmental indicators across the U.S. nuclear fleet.

How to assess nuclear plant risk

1. Enter the plant name or location — Type the facility name (e.g., "Diablo Canyon", "Palo Verde", "Vogtle") or a city/state location (e.g., "Waterford, LA") into the location field.
2. Optionally specify the plant name and radius — If you want to search corporate records under the operator's legal name (e.g., "Pacific Gas & Electric"), add it to plantName. Set radius in miles if you want environmental and seismic data pulled from a specific geographic radius rather than by name.
3. Click "Start" and wait — The actor calls all 8 data sources simultaneously. Most runs complete in 60–90 seconds depending on data source response times.
4. Download your report — Open the Dataset tab. Download as JSON for programmatic use, or CSV/Excel for spreadsheet analysis. One record is produced per run, containing all four risk dimension scores and the complete signal and recommendation list.

Input parameters

Input examples

Single facility assessment by plant name:

{
  "location": "Diablo Canyon",
  "plantName": "Diablo Canyon Power Plant",
  "radius": 50
}

Location-based assessment with radius:

{
  "location": "Waterford, LA",
  "radius": 75
}

Minimal input — name only:

{
  "location": "Palo Verde Nuclear Generating Station"
}

Input tips

• Use the common plant name for location — the Federal Register, Congress tracker, and Data.gov searches all use this name, so the facility's widely-known name (e.g., "Vogtle", "Seabrook") produces better signal coverage than a street address.
• Add plantName for operator-level corporate analysis — if the legal operating entity differs from the plant name (e.g., "Southern Company" vs. "Vogtle"), providing it in plantName improves OpenCorporates results.
• Set radius for geographic hazard coverage — a 50–100 mile radius is appropriate for seismic and FEMA disaster data, capturing regional events that affect the facility even if not centered exactly on it.
• Leave radius unset for national regulatory searches — the Federal Register and Congressional searches operate by keyword on the plant/operator name, not by geography, so radius does not affect them.

Output example

{
  "entity": "Diablo Canyon Power Plant",
  "compositeScore": 58,
  "verdict": "ELEVATED",
  "plantProximity": {
    "score": 72,
    "seismicEvents": 14,
    "significantQuakes": 5,
    "disasterExposure": 4,
    "riskLevel": "HIGH",
    "signals": [
      "M5.8 earthquake — exceeds design basis for many reactors",
      "5 M4.0+ earthquakes — seismic hazard reassessment needed",
      "2 flood events — cooling water intake/discharge vulnerability",
      "1 hurricane events — external power grid vulnerability"
    ]
  },
  "regulatoryCompliance": {
    "score": 44,
    "nuclearRules": 9,
    "emergencyActions": 1,
    "legislativePressure": 7,
    "complianceLevel": "WATCH",
    "signals": [
      "1 emergency NRC actions — immediate safety concern",
      "7 nuclear-related bills — active legislative attention"
    ]
  },
  "environmentalContamination": {
    "score": 32,
    "airQualityImpact": 9,
    "wasteIndicators": 4,
    "contaminationLevel": "MINIMAL",
    "signals": [
      "4 waste management regulatory actions"
    ]
  },
  "operatorTransparency": {
    "score": 24,
    "corporateEntities": 6,
    "complexStructure": false,
    "transparencyLevel": "ADEQUATE",
    "signals": []
  },
  "allSignals": [
    "M5.8 earthquake — exceeds design basis for many reactors",
    "5 M4.0+ earthquakes — seismic hazard reassessment needed",
    "2 flood events — cooling water intake/discharge vulnerability",
    "1 hurricane events — external power grid vulnerability",
    "1 emergency NRC actions — immediate safety concern",
    "7 nuclear-related bills — active legislative attention",
    "4 waste management regulatory actions"
  ],
  "recommendations": [
    "Seismic zone — probabilistic seismic hazard analysis update recommended"
  ],
  "metadata": {
    "location": "Diablo Canyon",
    "plantName": "Diablo Canyon Power Plant",
    "radius": 50,
    "generatedAt": "2026-03-20T09:14:22.000Z",
    "dataSources": [
      { "actor": "usgs-earthquake-search", "recordCount": 14 },
      { "actor": "fema-disaster-search", "recordCount": 4 },
      { "actor": "noaa-weather-alerts", "recordCount": 2 },
      { "actor": "federal-register-search", "recordCount": 17 },
      { "actor": "congress-bill-search", "recordCount": 22 },
      { "actor": "openaq-air-quality", "recordCount": 8 },
      { "actor": "opencorporates-search", "recordCount": 6 },
      { "actor": "datagov-dataset-search", "recordCount": 11 }
    ]
  }
}

Output fields

How much does it cost to run a nuclear plant risk assessment?

Nuclear Plant Risk Report uses pay-per-run pricing — you pay approximately $0.10 per report. Platform compute costs are included. Apify's free tier includes $5 in monthly credits, which covers approximately 50 reports.

You can set a maximum spending limit per run to control costs. The actor stops when your budget is reached.

For comparison, a nuclear risk consulting report from a specialist firm typically costs $5,000–$25,000 per facility. With this actor, screening the entire U.S. commercial nuclear fleet costs under $10.

Nuclear plant risk assessment using the API

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")

run = client.actor("ryanclinton/nuclear-plant-risk-report").call(run_input={
    "location": "Diablo Canyon",
    "plantName": "Diablo Canyon Power Plant",
    "radius": 50
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(f"Plant: {item['entity']}")
    print(f"Composite Score: {item['compositeScore']} — Verdict: {item['verdict']}")
    print(f"Seismic Events: {item['plantProximity']['seismicEvents']}")
    print(f"NRC Emergency Actions: {item['regulatoryCompliance']['emergencyActions']}")
    for signal in item.get("allSignals", []):
        print(f"  Signal: {signal}")
    for rec in item.get("recommendations", []):
        print(f"  Recommendation: {rec}")

JavaScript

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "YOUR_API_TOKEN" });

const run = await client.actor("ryanclinton/nuclear-plant-risk-report").call({
    location: "Diablo Canyon",
    plantName: "Diablo Canyon Power Plant",
    radius: 50
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const item of items) {
    console.log(`Plant: ${item.entity}`);
    console.log(`Score: ${item.compositeScore} — Verdict: ${item.verdict}`);
    console.log(`Seismic risk level: ${item.plantProximity.riskLevel}`);
    console.log(`Compliance level: ${item.regulatoryCompliance.complianceLevel}`);
    item.allSignals.forEach(signal => console.log(`  Signal: ${signal}`));
    item.recommendations.forEach(rec => console.log(`  Recommendation: ${rec}`));
}

cURL

# Start the actor run
curl -X POST "https://api.apify.com/v2/acts/ryanclinton~nuclear-plant-risk-report/runs?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "location": "Diablo Canyon",
    "plantName": "Diablo Canyon Power Plant",
    "radius": 50
  }'

# Fetch results (replace DATASET_ID from the run response above)
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?token=YOUR_API_TOKEN&format=json"

How Nuclear Plant Risk Report works

Phase 1: Parallel data collection across 8 sources

The actor calls all eight sub-actors simultaneously using Promise.all(), with each sub-actor allocated 512 MB of memory and a 120-second timeout. The query for geographic sources (USGS, FEMA, NOAA, OpenAQ) is constructed from the location input and optionally appended with the radius in miles (e.g., "Diablo Canyon 50mi"). The query for regulatory and legislative sources (Federal Register, Congress, Data.gov) is constructed from the entity name (either plantName or location) concatenated with the term "nuclear". The OpenCorporates query uses the entity name alone to find corporate registry matches. Up to 1,000 records are retrieved from each source's dataset.

Phase 2: Four-dimensional risk scoring

Each of the four scoring models receives the full data collection results as a keyed record. The models operate independently and apply domain-specific logic:

Plant Proximity Risk (30% composite weight) scores seismic events from USGS with magnitude thresholds — M6.0+ events trigger individual signals; M5.5+ events score 15 points each; M4.0+ events score 6 points each (maximum 40 points for seismicity). FEMA disaster records are parsed for flood and hurricane incident types. NOAA alerts are scanned for tornado and extreme-severity events. A compound risk bonus of up to 10 points is applied when both major earthquakes and flood events are detected simultaneously, replicating the Fukushima scenario hazard pattern.

Regulatory Compliance (30% composite weight) matches Federal Register entries against 15 nuclear keywords and further classifies matches containing "emergency", "immediately effective", "enforcement", "penalty", or "violation" terms. Congressional bills are scanned for nuclear keywords and additionally flagged if they contain restrictive language such as "ban", "moratorium", "phase out", or "restrict". Data.gov datasets mentioning nuclear, NRC, or radiation contribute up to 20 sub-score points. A compound pressure bonus is applied when emergency NRC actions coincide with restrictive legislation.

Environmental Contamination (25% composite weight) applies AQI thresholds from OpenAQ data: readings above 100 count as poor-air-quality days (3 points each); readings above 200 count as extreme pollution events (10 points each). Federal Register entries are cross-referenced against 10 waste-specific keywords including "spent fuel", "dry cask", "transuranic", "repository", and "yucca mountain". Entries additionally containing "leak", "contamination", or "release" terms score 12 points each as emergency waste events. Data.gov datasets mentioning contamination, cleanup, Superfund, or radioactive material contribute to the environmental sub-score.

Operator Transparency (15% composite weight) analyzes OpenCorporates results for jurisdiction count, holding entity count, dissolved/inactive entities, and total corporate entity count. Missing corporate records trigger a 25-point base opacity penalty. Multi-jurisdiction complexity is penalized at 3 points per jurisdiction plus 10 additional points when 3 or more jurisdictions are detected.

Phase 3: Composite scoring and output assembly

The composite score is a weighted average of the four sub-scores rounded to the nearest integer. Verdicts are assigned at thresholds of 20 (LOW_RISK), 40 (ACCEPTABLE), 60 (ELEVATED), 80 (HIGH_RISK), and 100 (CRITICAL). Recommendations are generated programmatically when specific sub-score thresholds are breached — for example, an EXTREME plant proximity rating triggers a design basis reassessment recommendation, and an ENFORCEMENT compliance rating triggers an urgent compliance remediation recommendation. All signals from all four dimensions are concatenated into allSignals. The full report is pushed to the Apify dataset as a single record alongside metadata including the generation timestamp and per-source record counts.

Tips for best results

1. Use the NRC's standard facility name. The NRC uses specific plant names in its Federal Register publications. Using "Diablo Canyon" rather than "DCPP" or "Avila Beach plant" will improve signal coverage from the regulatory sources.

2. Run assessments after seismic events. USGS earthquake data is updated continuously. Scheduling a run immediately after a regional M4.0+ earthquake near a facility will capture the event in the seismic scoring.

3. Compare scores over time. Run the actor quarterly for the same facility and track composite score trends. Increasing scores indicate deteriorating risk profiles — useful for ongoing monitoring obligations.

4. Batch facilities with sequential runs rather than modifying inputs. Each run is cheap at ~$0.10. Run one report per facility and store all results in the same dataset for portfolio-level analysis. You can trigger sequential runs programmatically with the Python or JavaScript client.

5. Feed results into a GIS tool. The location input combined with the composite score and sub-scores can be mapped in QGIS, Tableau, or Google Data Studio for geographic risk visualization across a fleet of facilities.

6. Use the allSignals field for narrative reporting. The signal strings are written in plain language suitable for direct inclusion in risk memos, board presentations, or regulatory submissions without further processing.

7. Combine with the Company Deep Research actor for operator profiles. After identifying an opaque operator structure via the transparency score, use Company Deep Research to build a full ownership and financial profile of the operating entity.

Combine with other Apify actors

Limitations

• No direct NRC ADAMS database access. The actor uses the Federal Register as a proxy for NRC regulatory activity. Direct NRC inspection reports, licensee event reports (LERs), and inspection findings require the NRC's ADAMS public document system, which is not queried.
• U.S.-centric data sources. USGS, FEMA, NOAA, the Federal Register, and Congress are U.S. government sources. The actor provides limited coverage for non-U.S. nuclear facilities. OpenCorporates and OpenAQ have some international coverage, but regulatory and legislative signals will be absent for facilities outside the U.S.
• No real-time radiation monitoring. The actor does not query real-time radiation monitoring networks (EPA RadNet, IAEA INES). Air quality from OpenAQ serves as a partial environmental proxy but does not directly measure radiation levels.
• Congressional bill coverage reflects bill introduction, not enactment. Many nuclear bills introduced in Congress do not pass. The legislative pressure score captures intent and political environment, not enacted law.
• OpenCorporates coverage varies by state. Corporate registry completeness differs significantly by state and entity type. Some nuclear operating entities, particularly public utilities with state-specific charter structures, may not appear in OpenCorporates.
• FEMA and USGS queries are keyword-based, not geospatial. Without a radius input, events are matched by name keyword, not by geographic proximity. For facilities in areas with generic place names, some unrelated events may be included.
• Scores reflect publicly available signals only. Internal NRC inspection findings, non-public enforcement letters, and confidential industry safety studies are not captured. A low score does not constitute an independent safety certification.
• Data source availability depends on third-party uptime. If any of the 8 sub-actors encounter API downtime during a run, those sources return empty results and their signals contribute zero points. The metadata.dataSources field shows record counts per source, making it easy to identify which sources returned data.

Integrations

• Zapier — trigger a nuclear risk report automatically when a new FEMA disaster is declared near a monitored facility location
• Make — build multi-step workflows that run risk reports, filter for HIGH_RISK or CRITICAL verdicts, and push alerts to a Slack channel or email distribution list
• Google Sheets — pipe risk scores for multiple facilities into a monitoring spreadsheet, with conditional formatting on composite score and compliance level columns
• Apify API — embed risk report generation into a risk management platform, ESG data pipeline, or regulatory compliance dashboard
• Webhooks — configure a webhook to notify a risk team when a run completes with a verdict of HIGH_RISK or CRITICAL
• LangChain / LlamaIndex — pass the allSignals and recommendations fields to an LLM to generate narrative risk summaries or regulatory briefing documents

Troubleshooting

• Score seems low despite known seismic activity. Check the metadata.dataSources field in the output. If usgs-earthquake-search shows a recordCount of 0, the USGS source returned no results — likely because the location name did not match USGS query terms. Try adding a radius (e.g., "radius": 100) or rephrasing the location as a city and state.
• Regulatory compliance score is zero for a known plant. The Federal Register search uses the entity name concatenated with "nuclear". If the plant's name does not appear in Federal Register publications verbatim, try entering the operator's legal name in the plantName field instead.
• All data sources show zero records. This typically indicates a run timeout on the sub-actors, which can occur during periods of high platform load. Re-run the actor. The parallel architecture means all sources retry simultaneously, and most runs complete successfully within 90 seconds.
• OpenCorporates returns no corporate entities. Some nuclear operating entities are structured as public utilities or government-owned authorities that do not have commercial corporate registry entries. A zero-entity result triggers the 25-point opacity penalty by design — the transparency score flags the absence of verifiable corporate records as a risk signal.

Responsible use

• This actor only accesses publicly available data from U.S. government databases and open corporate registries.
• Nuclear facility risk scores are indicators derived from public signals, not independent safety assessments. Do not use scores as a substitute for qualified nuclear engineering analysis or NRC-certified inspection programs.
• Comply with applicable laws when using output data for regulatory submissions, investment decisions, or public communications. Risk scores should be clearly attributed as algorithmic assessments of public data, not official government or regulator findings.
• For guidance on web scraping legality, see Apify's guide.

FAQ

How does nuclear plant risk assessment work with this actor? The actor queries 8 public data sources in parallel — USGS earthquake catalog, FEMA disaster declarations, NOAA weather alerts, the Federal Register, Congressional bill tracker, OpenAQ air quality, OpenCorporates corporate registry, and Data.gov — then applies four scoring models to produce a composite Nuclear Risk Score (0–100) and a structured verdict from LOW_RISK to CRITICAL.

How many facilities can I assess in one run? Each run assesses one facility. For multi-facility portfolio screening, trigger sequential runs via the API. At $0.10 per run, screening all 93 U.S. commercial nuclear facilities costs under $10.

Does this actor access NRC inspection reports directly? No. It uses the Federal Register as a proxy for NRC regulatory activity, which captures published rules, emergency orders, and enforcement actions. For direct NRC inspection reports, consult the NRC's ADAMS public document system at nrc.gov.

How accurate is the seismic scoring for nuclear plant risk? The seismic model applies magnitude thresholds derived from NRC design basis parameters: M5.5+ events score 15 points each because most U.S. reactors have design basis seismic loads in the range of 0.1–0.3g, which M5.5+ events can approach or exceed at short distances. The model correctly identifies high-seismicity regions but does not perform site-specific ground motion calculations.

Can I assess decommissioned nuclear plants? Yes. Decommissioned facilities continue to generate Federal Register waste management actions (spent fuel storage, license termination), FEMA/USGS natural hazard data for the site location, and Data.gov contamination and cleanup dataset entries. The actor will detect and score this regulatory and environmental activity.

What nuclear plant risk score indicates a critical situation? A composite score of 80 or above receives a CRITICAL verdict. Scores of 60–79 are HIGH_RISK. CRITICAL scores typically reflect a combination of high seismicity, active NRC enforcement actions, and environmental contamination signals occurring simultaneously.

How is nuclear plant risk assessment different from an official NRC inspection? This actor aggregates publicly available data signals and applies a consistent algorithmic scoring model. An NRC inspection involves qualified nuclear engineers physically reviewing plant systems, operator logs, and maintenance records against license conditions. The actor's output is a research and monitoring tool, not an inspection substitute.

Is it legal to scrape nuclear facility data? Yes. All data sources used by this actor — USGS, FEMA, NOAA, the Federal Register, Congress.gov, OpenAQ, OpenCorporates, and Data.gov — are publicly accessible databases with open data policies. The actor uses their published APIs, not web scraping techniques.

Can I schedule this actor to run automatically after seismic events? Yes. Use Apify scheduling to run the actor at regular intervals, or combine it with a NOAA/USGS monitoring workflow that triggers runs via Apify webhooks when a seismic event of a specified magnitude is detected near a monitored facility.

How long does a typical nuclear plant risk assessment run take? Most runs complete in 60–90 seconds. The eight sub-actors run in parallel, so total time is approximately equal to the slowest individual source response. Runs occasionally extend to 120 seconds during high API load periods.

What happens if one data source fails during a run? Failed sub-actor calls return an empty array and contribute zero points to that dimension's score. The run still completes and produces an output record. The metadata.dataSources field lists each source with its recordCount, making it easy to identify which sources returned data and which failed.

How is the operator transparency score useful if many utilities aren't on OpenCorporates? The transparency model is designed to flag opacity as a risk signal, not to confirm corporate legitimacy. When a nuclear operating entity has no OpenCorporates records, the model assigns a 25-point base penalty precisely because the absence of verifiable corporate registry data is itself a transparency concern for a safety-critical regulated industry.

Help us improve

If you encounter issues, you can help us debug faster by enabling run sharing in your Apify account:

1. Go to Account Settings > Privacy
2. Enable Share runs with public Actor creators

This lets us see your run details when something goes wrong, so we can fix issues faster. Your data is only visible to the actor developer, not publicly.

Support

Found a bug or have a feature request? Open an issue in the Issues tab on this actor's page. For custom solutions or enterprise integrations, reach out through the Apify platform.