Provides access to current weather data, forecasts, and historical weather data for any location worldwide.
Provides access to current weather data, forecasts, and historical weather data for any location worldwide. On Nagent, OpenWeather API is exposed as a fully-configurable developer tools integration that any agent can call — 21 actions, and API key authentication. No code is required to wire OpenWeather API into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use OpenWeather API 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 OpenWeather API 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 OpenWeather API, with input parameters and output schema. Drop these into any step of an agent built in Helix.
OPENWEATHER_API_DELETE_WEATHER_STATIONTool to delete a registered weather station. Use after identifying a station to remove. Returns confirmation message upon success.
Input parameters
The unique ID of the weather station to delete.
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
OPENWEATHER_API_GET5_DAY_FORECASTTool to get a 5-day forecast every 3 hours (up to 40 UTC timestamps). Exactly one location identifier required per call: `q`, `id`, `zip`, or `lat`+`lon` pair. Use `city.timezone` offset to convert timestamps to local time before grouping into daily summaries.
Input parameters
City name and optional country code, e.g. 'London,uk'
OpenWeatherMap city ID
Latitude in degrees
Longitude in degrees
Zip code with country code, e.g. '94040,us'
Language code (ISO 639-1)
Response format
Units of measurement (standard, metric, imperial)
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
OPENWEATHER_API_GET_AIR_POLLUTION_CURRENTTool to fetch current air pollution data for a location. Use when you need real-time air quality details by latitude and longitude.
Input parameters
Latitude of the location, between -90 and 90
Longitude of the location, 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
OPENWEATHER_API_GET_AIR_POLLUTION_FORECASTTool to get forecasted air pollution data for a specific location. Use after confirming latitude and longitude. Forecast availability may be limited for remote or oceanic coordinates; verify response timestamps to confirm returned data represents a true forecast rather than a current snapshot.
Input parameters
Geographical latitude in decimal degrees (range -90 to 90)
Geographical longitude in decimal degrees (range -180 to 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
OPENWEATHER_API_GET_AIR_POLLUTION_HISTORYTool to retrieve historical air pollution data. Use when you need past air quality levels for a specific latitude/longitude and time range.
Input parameters
End UNIX timestamp (UTC seconds); must be >= start
Latitude of the location (range: -90 to 90)
Longitude of the location (range: -180 to 180)
Start UNIX timestamp (UTC seconds); must be <= end
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
OPENWEATHER_API_GET_CIRCLE_CITY_WEATHERTool to search for current weather data in cities around a geographic point. Use when you need to fetch weather within a radius circle after confirming latitude and longitude.
Input parameters
Number of cities to return within the circle (1–50). Default is 10.
Latitude of the circle center in degrees (-90 to 90)
Longitude of the circle center in degrees (-180 to 180)
Language of the response (ISO 639-1)
Response format: 'json' or 'xml'
Units of measurement: standard, metric, or imperial
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
OPENWEATHER_API_GET_CURRENT_WEATHERTool to retrieve current weather data for a location. Use when you need up-to-the-minute weather info. Exactly one location identifier must be provided per call: either `q`, `id`, `zip`, or the pair `lat`+`lon`. Passing multiple identifiers causes errors or ambiguous matches.
Input parameters
City name, state code and country code, e.g., 'London,uk'
City ID, e.g., 2172797
Geographic coordinate latitude, e.g., 35.0
Geographic coordinate longitude, e.g., 139.0
Zip code and country code, e.g., '94040,us'
Language for the response (ISO 639-1 code, e.g., 'en')
Units of measurement. 'standard' (default), 'metric', or 'imperial'
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
OPENWEATHER_API_GET_GEOCODING_BY_ZIPTool to convert zip/post code into geographic coordinates. Use when you need latitude and longitude for a specific postal code.
Input parameters
Zip/post code and country code divided by comma. Use ISO 3166 country codes (e.g., '10001,US' or 'E14,GB').
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
OPENWEATHER_API_GET_GEOCODING_DIRECTTool to convert a location name into geographic coordinates. Use when you need latitude and longitude for a given location after confirming the precise name.
Input parameters
Location query including city name, state code and country code separated by commas (e.g., 'London,UK'). Ambiguous queries can return multiple mismatched locations; use the full three-part format 'city,state_code,country_code' (e.g., 'Springfield,IL,US') and verify the returned country/region before using coordinates downstream.
Number of results to return (1 to 5). Defaults to 5. Use 1 only for unambiguous locations; for ambiguous queries review all returned results to select the correct match.
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
OPENWEATHER_API_GET_GEOCODING_REVERSETool to convert geographic coordinates into a location name. Use when you need city, state, and country info from latitude and longitude.
Input parameters
Latitude of the location in decimal degrees
Longitude of the location in decimal degrees
Number of results to return (1 to 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
OPENWEATHER_API_GET_STATION_MEASUREMENTSTool to retrieve aggregated measurements from a weather station with minute, hour, or day granularity. Use when you need historical weather data from a specific registered station.
Input parameters
End of time interval (Unix timestamp in seconds)
Start of time interval (Unix timestamp in seconds)
Aggregation type: m (minute), h (hour), or d (day)
Maximum number of measurement records to return
Internal station ID from OpenWeather
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
OPENWEATHER_API_GET_UV_INDEXTool to retrieve current UV index for a location. Use when you need up-to-the-minute UV index by latitude and longitude.
Input parameters
Latitude of the location, between -90 and 90
Longitude of the location, 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
OPENWEATHER_API_GET_UV_INDEX_FORECASTTool to retrieve UV index forecast for a specific location. Use when you need upcoming UV index values after confirming latitude and longitude. Returns up to 8 days of data. Data may be sparse or absent for ocean and remote locations; an empty response means no data available, not safe UV conditions.
Input parameters
Number of days to return (1-8); defaults to 8 if not specified
Latitude of the location, between -90 and 90
Longitude of the location, 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
OPENWEATHER_API_GET_UV_INDEX_HISTORYTool to retrieve historical UV index data for a specified location and time range. Use when you need to analyze past UV exposure trends after confirming coordinates and time period.
Input parameters
End UNIX timestamp (UTC seconds); must be >= start
Latitude of the location (range: -90 to 90)
Longitude of the location (range: -180 to 180)
Start UNIX timestamp (UTC seconds); must be <= end
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
OPENWEATHER_API_GET_WEATHER_MAP_TILETool to fetch Weather Maps 2.0 tile images. Use when you need dynamic weather layers at specific zoom and coordinates with advanced styling options.
Input parameters
Tile X coordinate (non-negative integer).
Tile Y coordinate (non-negative integer).
Zoom level of the tile (non-negative integer).
Color for empty-data fill areas (hex or named).
Color schema of the tiles, e.g., 'original', 'black'.
Weather layer name. Options: clouds, clouds_new, precipitation, precipitation_new, pressure, pressure_new, wind, wind_new, temp, temp_new.
Tile scale factor: 1 or 2 for retina.
Image format; only 'png' is supported.
Tile opacity value between 0.0 and 1.0.
Custom palette definition (comma-separated or JSON).
Fill tiles outside data coverage if true.
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
OPENWEATHER_API_GET_WEATHER_STATIONTool to get information about a specific weather station by its ID. Use when you need details about a particular station.
Input parameters
Internal station ID to retrieve information for.
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
OPENWEATHER_API_GET_WEATHER_STATIONSTool to list all weather stations added to your account. Use after setting up your OpenWeather API key.
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
OPENWEATHER_API_GET_WEATHER_TRIGGERSTool to retrieve weather triggers for specific conditions. Use after defining trigger criteria.
Input parameters
List of weather trigger definitions
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
OPENWEATHER_API_POST_ADD_WEATHER_STATIONTool to add a new weather station to your account. Use when you need to register a station before sending custom data.
Input parameters
Station name
Station altitude in meters above sea level
Station latitude, range -90 to 90 degrees
Station longitude, range -180 to 180 degrees
External station ID (your own reference)
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
OPENWEATHER_API_POST_SUBMIT_STATION_MEASUREMENTSTool to submit weather measurements from a registered station. Use when you need to send temperature, wind, pressure, humidity, or precipitation data for a station.
Input parameters
Array of measurement objects to submit
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
OPENWEATHER_API_UPDATE_WEATHER_STATIONTool to update weather station details. Use when you need to modify the name, location, or external ID of an existing station.
Input parameters
Human-readable name for the station
Altitude of the station above sea level in meters
Latitude of the station in degrees, between -90 and 90
Longitude of the station in degrees, between -180 and 180
Unique identifier of the weather station to update
Custom user-provided external identifier for the station
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 77 agents privately built on Nagent that already use OpenWeather API.
Build on Nagent
Connect OpenWeather API 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 OpenWeather API, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, OpenWeather API is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once OpenWeather API is connected, you configure its 21 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop OpenWeather API 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 OpenWeather API event fires, the agent kicks off automatically.
Every OpenWeather API 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 OpenWeather API ships with 21 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching OpenWeather API together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build OpenWeather API-based workflows tailored to your business.