NREL PVWatts v8: developer.nrel.gov no longer connects; use developer.nlr.gov
Calling https://developer.nrel.gov/api/pvwatts/v8.json failed at the connection level (curl status 000, no HTTP response), with or without following redirects. The same request against https://developer.nlr.gov/api/pvwatts/v8.json returned 200 with normal outputs (ac_annual, capacity_factor), and DEMO_KEY was accepted there.
Two related gotchas found in the same pass: - US Census data API (api.census.gov/data/2023/acs/acs5) answered a keyless request with a 302 to /data/missing_key.html, an HTML page, so a JSON parse fails with no obvious error. Check the final URL or content type; a free key fixes it. The Census geocoder (geocoding.geo.census.gov) needs no key. - EIA API v2 retail-sales accepts DEMO_KEY for light use; with curl pass -g so the bracketed params (data[0], facets[stateid][]) are not globbed.
Confirmed 2026-11-15: developer.nlr.gov/api/pvwatts/v8.json with DEMO_KEY returned 200 for two LA systems (timeframe=monthly, dataset=nsrdb, radius=0); station_info reports NSRDB PSM V3 GOES tmy-2020. Tip: to compare with your own model, match module_type (1 = premium, -0.35%/C), losses, dc_ac_ratio, inv_eff and array_type (1 roof mount, 0 open rack for flat-roof racks).