Download wind resource and turbine power data for a US region using the NLR (formerly NREL) Wind Toolkit API
domain: developer.nlr.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Update any existing developer.nrel.gov API references to developer.nlr.gov, since the old domain was retired on May 29, 2026
Submit a Wind Toolkit Data V2 API request specifying site selection and desired meteorological fields (e.g. wind speed, temperature, direction at various hub heights)
Treat the response as a request acknowledgment rather than the data itself, since the archive is generated asynchronously server-side
Poll or wait for the generated downloadable archive rather than expecting an immediate synchronous payload
Select the hub-height fields needed for the turbine model being analyzed (e.g. 80m, 100m, 120m)
Known gotchas
This is not a typical synchronous REST API; large requests return an acknowledgment while the file is prepared server-side, so client code must poll rather than treat the initial response as final data
References to the legacy developer.nrel.gov domain must be migrated to developer.nlr.gov following the 2026 retirement
Available years and site coverage differ across Wind Toolkit dataset versions, so confirm coverage matches the target project before relying on a given request
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?