Solar resource assessment and forecasting data for irradiance and PV power, globally.
Solar resource assessment and forecasting data for irradiance and PV power, globally. On Nagent, Solcast is exposed as a fully-configurable analytics integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Solcast into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Solcast to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Solcast into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Solcast, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SOLCAST_GET_DATA_HISTORIC_RADIATION_AND_WEATHERTool to get historical irradiance and weather estimated actuals for a requested location. Use when you need historical solar radiation and weather data from 2007-01-01 to 7 days ago, for up to 31 days at a time.
Input parameters
ISO 8601 ending datetime. Must be within 31 days of start date. Timezone handling same as start. Mutually exclusive with duration parameter.
Panel tilt angle in degrees from horizontal. Must be between 0 and 90. Defaults based on latitude if unspecified.
ISO 8601 compliant starting datetime for historical data (e.g., '2024-11-15T00:00:00Z'). If no timezone specified, inferred from time_zone parameter; otherwise UTC assumed.
Response format. Valid values: 'json' or 'csv'. Defaults to 'json'.
Averaging period length in ISO 8601 format (e.g., 'PT5M' for 5 minutes, 'PT30M' for 30 minutes, 'PT1H' for 1 hour).
Panel azimuth angle from true north in degrees. Defaults vary by hemisphere if unspecified.
ISO 8601 duration format (e.g., 'P7D' for 7 days, 'P1M' for 1 month). Must be within 31 days of start date. Mutually exclusive with end parameter.
Location latitude in decimal degrees. Must be between -90 and 90, where north is positive.
Location longitude in decimal degrees. Must be between -180 and 180, where east is positive.
Timezone specification. Accepted values: 'utc', 'longitudinal', or range -13 to 13 in 0.25 hour increments (e.g., '10' for UTC+10).
Sun-tracking or geometry configuration type (e.g., 'fixed', 'horizontal_single_axis').
Apply terrain-based irradiance modifications using 90m-resolution elevation model.
Specific output parameters to include in response (e.g., 'ghi', 'dni', 'dhi', 'air_temp', 'wind_speed_10m'). If not specified, all available parameters are returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SOLCAST_GET_RESOURCES_PV_POWER_SITETool to retrieve a specific PV power resource by its unique identifier. Use when you need to fetch complete resource configuration including capacity, orientation, tracking, and derating parameters.
Input parameters
The unique identifier of the resource to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SOLCAST_GET_RESOURCES_PV_POWER_SITESTool to list PV power resources available to authenticated user. Use when you need to retrieve the list of PV power sites with optional filtering by entitlement level.
Input parameters
Filter for site entitlement level. Valid values: 'advanced' or 'premium'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SOLCAST_PATCH_RESOURCES_PV_POWER_SITETool to partially update an existing PV power resource's technical specifications. Use when you need to modify specific resource configuration fields without replacing the entire resource.
Input parameters
Name of the PV power resource.
The off-horizontal tilt angle of modules for fixed-tilt sites (degrees).
The angle from true north the modules are facing (degrees).
Total AC inverter (nameplate) capacity in MW.
Location latitude coordinate, between -90 and 90.
Location longitude coordinate, between -180 and 180.
Total DC module capacity in MW.
Site entitlement level. Valid values: 'advanced' or 'premium'.
PV module technology/material type (e.g., 'mono-si', 'poly-si', 'cdte', 'cigs', 'asi').
PV module row width in metres.
The unique identifier of the resource to update.
System installation date in ISO 8601 format for age-based derating calculations.
PV module row height above ground in metres.
Average terrain slope in degrees.
Sun-tracking configuration type (e.g., 'fixed', 'horizontal_single_axis').
Enable bifacial module modeling for rear-side power generation.
Terrain downhill direction angle from true north (degrees).
Maximum power export to grid in MW.
Rear-to-front module efficiency ratio (0 to 1).
Metadata confirmation timestamp in ISO 8601 format.
Ground surface reflectivity proportion (0 to 1).
Annual system degradation rate (fraction per year).
Temperature coefficient of power (fraction per degree C).
Monthly dust soiling impact estimates as proportional losses (12 values, one per month).
Horizontal tracker axis azimuth angle from true north (degrees). For single-axis trackers.
Total non-temperature system losses as a fraction (0 to 1).
Proportion of ground area covered by PV modules (0 to 1).
Enable backtracking feature to avoid row-to-row shading.
Enable smart tracking to reposition trackers during cloudy periods.
Peak inverter conversion efficiency rating (0 to 1).
Cloudy sky zenith angle coefficients for advanced modeling.
Maximum off-horizontal rotation angle for trackers (degrees).
Clear sky zenith angle coefficients for advanced modeling.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SOLCAST_POST_RESOURCES_PV_POWER_SITETool to create a new PV power resource for Advanced PV Power forecasting. Use when you need to add a new solar installation site with comprehensive technical specifications including capacity, orientation, tracking parameters, and derating factors.
Input parameters
Name of the PV power resource.
The off-horizontal tilt angle of modules for fixed-tilt sites (degrees).
The angle from true north the modules are facing (degrees). North is 0, South is ±180.
Total AC inverter (nameplate) capacity in MW.
Location latitude coordinate, between -90 and 90.
Location longitude coordinate, between -180 and 180.
Total DC module capacity in MW.
Site entitlement level. Valid values: 'advanced' or 'premium'.
PV module technology/material type (e.g., 'mono-si', 'poly-si', 'cdte', 'cigs', 'asi').
PV module row width in metres.
System installation date in ISO 8601 format for age-based derating calculations.
PV module row height above ground in metres.
Ground terrain slope angle in degrees.
Sun-tracking configuration type (e.g., 'fixed', 'horizontal_single_axis', 'dual_axis').
Enable bifacial module modeling for rear-side power generation.
Direction of terrain slope from true north (degrees).
Maximum power export to grid in MW.
Rear-to-front module efficiency ratio (0 to 1).
Metadata confirmation timestamp in ISO 8601 format.
Ground surface reflectivity proportion (0 to 1).
Annual system degradation rate (fraction per year).
Temperature coefficient of power (fraction per degree C).
Monthly dust soiling impact estimates as proportional losses (12 values, one per month).
Direction tracking axis points from true north (degrees). For single-axis trackers.
Total non-temperature system losses as a fraction (0 to 1).
Proportion of ground area covered by PV modules (0 to 1).
Enable backtracking feature to avoid row-to-row shading.
Enable smart tracking to reposition trackers during cloudy periods.
Peak inverter conversion efficiency rating (0 to 1).
Zenith angle coefficients for cloudy conditions for advanced modeling.
Maximum rotation angle from horizontal for trackers (degrees).
Zenith angle coefficients for clear sky conditions for advanced modeling.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SOLCAST_PUT_RESOURCES_PV_POWER_SITETool to update an existing PV power resource with comprehensive technical specifications for solar installation site modeling. Use when you need to modify resource configuration including capacity, orientation, tracking parameters, derating factors, and bifacial system settings.
Input parameters
Name of the PV power resource.
The off-horizontal tilt angle of modules for fixed-tilt sites (degrees).
The angle from true north the modules are facing (degrees).
Total AC inverter (nameplate) capacity in MW.
Location latitude coordinate, between -90 and 90.
Location longitude coordinate, between -180 and 180.
Total DC module capacity in MW.
Site entitlement level. Valid values: 'advanced' or 'premium'.
PV module technology/material type (e.g., 'mono-si', 'poly-si', 'cdte', 'cigs', 'asi').
PV module row width in metres.
The unique identifier of the resource to update.
System installation date in ISO 8601 format for age-based derating calculations.
PV module row height above ground in metres.
Average terrain slope in degrees.
Sun-tracking configuration type (e.g., 'fixed', 'horizontal_single_axis').
Enable bifacial module modeling for rear-side power generation.
Terrain downhill direction angle from true north (degrees).
Maximum power export to grid in MW.
Rear-to-front module efficiency ratio (0 to 1).
Metadata confirmation timestamp in ISO 8601 format.
Ground surface reflectivity proportion (0 to 1).
Annual system degradation rate (fraction per year).
Temperature coefficient of power (fraction per degree C).
Monthly dust soiling impact estimates as proportional losses (12 values, one per month).
Horizontal tracker axis azimuth angle from true north (degrees). For single-axis trackers.
Total non-temperature system losses as a fraction (0 to 1).
Proportion of ground area covered by PV modules (0 to 1).
Enable backtracking feature to avoid row-to-row shading.
Enable smart tracking to reposition trackers during cloudy periods.
Peak inverter conversion efficiency rating (0 to 1).
Cloudy sky zenith angle coefficients for advanced modeling.
Maximum off-horizontal rotation angle for trackers (degrees).
Clear sky zenith angle coefficients for advanced modeling.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 89 agents privately built on Nagent that already use Solcast.
Build on Nagent
Connect Solcast to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Solcast, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Solcast is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Solcast is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Solcast steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Solcast event fires, the agent kicks off automatically.
Every Solcast action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Solcast ships with 6 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Solcast together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Solcast-based workflows tailored to your business.