stormglass.io provides a global weather API offering high-resolution forecasts and historical data from trusted meteorological institutions.
stormglass.io provides a global weather API offering high-resolution forecasts and historical data from trusted meteorological institutions. On Nagent, Stormglass Io is exposed as a fully-configurable developer tools integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Stormglass Io into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Stormglass Io to automate the kinds of tasks developer tools 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 Stormglass Io 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 Stormglass Io, with input parameters and output schema. Drop these into any step of an agent built in Helix.
STORMGLASS_IO_GET_ELEVATION_POINTTool to fetch elevation data for a single geographic point. Use when you need bathymetry or topography for a specific latitude/longitude.
Input parameters
Latitude of the desired coordinate in decimal degrees, between -90 and 90.
Longitude of the desired coordinate in decimal degrees, between -180 and 180.
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
STORMGLASS_IO_GET_TIDE_EXTREMES_POINTTool to retrieve high and low tide times with corresponding sea level heights for a coordinate. Returns tide extreme points (high/low) for the specified time interval.
Input parameters
Timestamp in UTC for last forecast hour - UNIX format or URL encoded ISO format.
Latitude in decimal degrees (-90 to 90).
Longitude in decimal degrees (-180 to 180).
Datum values the tide heights will be relative to.
Timestamp in UTC for first forecast hour - UNIX format or URL encoded ISO format.
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
STORMGLASS_IO_GET_TIDE_STATIONS_AREATool to list tide stations within a defined geographic bounding box. Use when you need stations in a specific region defined by coordinates.
Input parameters
Bounding box defining the area. Format: top-right and bottom-left coordinates as 'lat,lng:lat,lng' (e.g., '38.0,-122.0:37.5,-122.5')
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
STORMGLASS_IO_GET_TIDE_STATIONS_LISTTool to list all available tide stations. Use when you need a catalog of stations before querying tide data.
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
STORMGLASS_IO_STORMGLASS_GET_SOLAR_POINTTool to fetch solar irradiation and sun-position data for a specific coordinate. Use after confirming lat/lng, desired parameters, and optional ISO-formatted start/end.
Input parameters
Optional end time (inclusive) in ISO8601 UTC format, e.g. '2022-02-01T23:00:00+00:00'
Latitude in decimal degrees (-90 to 90).
Longitude in decimal degrees (-180 to 180).
Optional start time (inclusive) in ISO8601 UTC format, e.g. '2022-02-01T00:00:00+00:00'
List of solar parameters to retrieve. Valid options: 'uvIndex' (UV index), 'downwardShortWaveRadiationFlux', 'solarDownwardRadiationFlux', 'surfaceNetShortwaveRadiationDownwardsFlux'.
Optional data source filter. Valid options: 'noaa' (NOAA), 'sg' (Storm Glass). If not specified, data from all available sources is 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
STORMGLASS_IO_STORMGLASS_GET_WEATHER_POINTTool to fetch marine and land weather data for a specific coordinate. Use after confirming latitude, longitude, and desired parameters.
Input parameters
Optional end time (inclusive) in ISO8601 UTC format, e.g. '2019-02-02T18:00:00+00:00'.
Latitude in decimal degrees (-90 to 90).
Longitude in decimal degrees (-180 to 180).
Optional start time (inclusive) in ISO8601 UTC format, e.g. '2019-02-02T15:00:00+00:00'.
List of weather parameters to retrieve. Valid parameters include: airTemperature, humidity (not 'relativeHumidity'), cloudCover, precipitation, windSpeed, windDirection, waveHeight, waterTemperature, pressure, visibility, snow, rain, gust, and many more (70+ total). See https://docs.stormglass.io/ for complete list.
Data source/provider filter. One of 'noaa','sg','meteo','dwd','fcoo','icon','hira','marine'.
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 84 agents privately built on Nagent that already use Stormglass Io.
Build on Nagent
Connect Stormglass Io 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 Stormglass Io, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Stormglass Io is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Stormglass Io 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 Stormglass Io 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 Stormglass Io event fires, the agent kicks off automatically.
Every Stormglass Io 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 Stormglass Io ships with 6 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Stormglass Io together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Stormglass Io-based workflows tailored to your business.