Ambee provides real-time, hyperlocal environmental data through APIs, offering insights into air quality, weather, pollen, and more.
Ambee provides real-time, hyperlocal environmental data through APIs, offering insights into air quality, weather, pollen, and more. On Nagent, Ambee is exposed as a fully-configurable developer tools integration that any agent can call — 27 actions, and API key authentication. No code is required to wire Ambee into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ambee 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 Ambee 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 Ambee, with input parameters and output schema. Drop these into any step of an agent built in Helix.
AMBEE_GEOCODE_BY_PLACETool to transform a place name or address into geographic coordinates. Use after confirming the location name to get precise latitude and longitude.
Input parameters
Name of the location to be searched.
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
AMBEE_GET_AIR_QUALITY_BY_CITYTool to retrieve real-time air quality data for a specific city. Use after obtaining a valid city name when current AQI and pollutant levels are needed.
Input parameters
Name of the city to search.
Number of records to return. Must be >=1. Defaults to 1.
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
AMBEE_GET_AIR_QUALITY_BY_COUNTRY_CODETool to retrieve real-time air quality data for a specific country using a 3-letter ISO code. Use after acquiring the country code and when you want a national overview of air quality.
Input parameters
Number of air quality records to return from different monitoring stations or time periods. Must be between 1 and 5. Defaults to 1.
3-letter ISO country code (e.g., 'GBR' for United Kingdom, 'USA' for United States, 'IND' for India). Returns air quality data from monitoring stations within the specified country.
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
AMBEE_GET_AIR_QUALITY_BY_LAT_LNGTool to retrieve real-time air quality data for a specific latitude and longitude. Use when you need hyper-local air quality readings for given coordinates.
Input parameters
Latitude of the search location. Must be between -90 and 90 degrees.
Longitude of the search location. Must be between -180 and 180 degrees.
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
AMBEE_GET_AIR_QUALITY_BY_POSTAL_CODERetrieve real-time air quality data for a specific postal code and country. Returns comprehensive air quality metrics including pollutant concentrations (PM2.5, PM10, CO, NO2, O3, SO2), Air Quality Index (AQI) with category (Good/Moderate/Unhealthy), and location details. Data is updated hourly with 500-meter spatial resolution following US EPA standards. Use this when you need hyper-local air quality insights for a specific postal code.
Input parameters
Postal code of the location (format varies by country, e.g., '560020' for India, '10001' for USA, 'SW1A 1AA' for UK).
3-letter ISO 3166-1 alpha-3 country code (e.g., 'IND' for India, 'USA' for United States, 'GBR' for United Kingdom).
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
AMBEE_GET_AIR_QUALITY_FORECAST_BY_LAT_LNGTool to retrieve air quality forecast for a specific latitude and longitude. Use when you need predicted air quality data up to 48 hours in advance based on geographic coordinates.
Input parameters
Latitude of the search location, must be between -90 and 90 degrees
Longitude of the search location, must be between -180 and 180 degrees
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
AMBEE_GET_AIR_QUALITY_HISTORY_BY_LAT_LNGTool to retrieve historical air quality data for a specific latitude and longitude. Use when you need past air quality readings for given coordinates within the last 2 days.
Input parameters
Ending timestamp of the period to search for in the format YYYY-MM-DD hh:mm:ss
Latitude of the search location, must be between -90 and 90 degrees
Longitude of the search location, must be between -180 and 180 degrees
Starting timestamp of the period to search for in the format YYYY-MM-DD hh:mm:ss. API only provides past 2 days of 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
AMBEE_GET_DISASTERS_BY_CONTINENT_LATESTTool to retrieve latest natural disaster data for a specific continent. Use when you need up-to-date disaster information by continent code.
Input parameters
Page number to retrieve
Number of results per page
Continent code: AFR (Africa), ANT (Antarctica), ASIA (Asia), AUS (Australia), EUR (Europe), NAR (North America), SAR (South America), OCEAN (Oceania)
Optional disaster event type code to filter results
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
AMBEE_GET_DISASTERS_HISTORYTool to retrieve global historical natural disaster data with date range filtering. Use when you need to search disaster events from a specific starting date onwards.
Input parameters
Starting timestamp of the search period in format 'YYYY-MM-DD hh:mm:ss' (e.g., '2024-07-01 15:00:00')
Page number for pagination
Number of records to return per page
Optional disaster event type code to filter results: TN (Tsunamis), EQ (Earthquakes), TC (Tropical cyclones), WF (Wildfires), FL (Floods), ET (Extreme Temperature), DR (Droughts), SW (Severe storms), SI (Sea Ice), VO (Volcano), LS (Landslides), Misc (Miscellaneous)
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
AMBEE_GET_DISASTERS_HISTORY_BY_COUNTRY_CODETool to retrieve historical natural disaster data for a country by ISO country code. Use when you need past disaster information for a specific country within a given date range.
Input parameters
Ending timestamp of the search period in format YYYY-MM-DD HH:MM:SS
Starting timestamp of the search period in format YYYY-MM-DD HH:MM:SS
Page number for pagination
Number of records to return
Optional disaster event type code to filter results
3-letter ISO country code (e.g., USA, GBR, IND)
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
AMBEE_GET_DISASTERS_HISTORY_BY_LAT_LNGTool to retrieve historical natural disaster data for a specific location by coordinates with date range. Use when you need historical disaster information for a geographic point within the past month.
Input parameters
Ending timestamp in format 'YYYY-MM-DD HH:MM:SS'. Cannot be in the future. Example: '2026-02-11 23:59:59'
Latitude of the search location. Must be between -90 and 90 degrees.
Longitude of the search location. Must be between -180 and 180 degrees.
Starting timestamp in format 'YYYY-MM-DD HH:MM:SS'. Must be within the last month. Example: '2026-02-08 00:00:00'
Page number for pagination
Number of disaster records to return per page
Optional disaster event type code to filter results
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
AMBEE_GET_DISASTERS_LATEST_BY_COUNTRY_CODETool to retrieve latest natural disaster data for a specific country using ISO country code. Use when you need up-to-date disaster information for a particular country.
Input parameters
Page number to retrieve
Number of results per page
Optional disaster event type code to filter results
3-letter ISO country code (e.g., USA for United States, GBR for United Kingdom, IND for India)
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
AMBEE_GET_DISASTERS_LATEST_BY_LAT_LNGTool to retrieve latest natural disaster data (earthquakes, floods, droughts, volcanic eruptions) for a specific location using geographic coordinates. Use when you need up-to-date disaster information for a particular latitude and longitude.
Input parameters
Latitude of the search location. Must be between -90 and 90 degrees.
Longitude of the search location. Must be between -180 and 180 degrees.
Page number for pagination
Number of results per page to return
Optional disaster event type code to filter results
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
AMBEE_GET_ELEVATION_BY_LAT_LNGTool to retrieve elevation statistics (min, max, mean) for a specific latitude and longitude. Use when you need geospatial elevation data for a location within North America.
Input parameters
Latitude of the search location. Must be between -90 and 90 degrees.
Longitude of the search location. Must be between -180 and 180 degrees.
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
AMBEE_GET_ELEVATION_BY_PLACERetrieve elevation statistics (minimum, maximum, and mean) for a location by place name. Returns elevation data in meters above sea level. This endpoint has global coverage and is updated every 6 months. Use this when you have a place name (like "San Francisco, USA" or "Tokyo") and need detailed elevation information.
Input parameters
Name of the location to search. Can be a city name (e.g., 'Tokyo'), city with country (e.g., 'Paris, France'), or a more specific location (e.g., 'San Francisco, USA'). Global coverage available.
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
AMBEE_GET_FIRE_RISK_BY_LAT_LNGTool to retrieve fire risk forecast and Fire Weather Index (FWI) data for specific geographic coordinates. Use when you need weekly fire risk predictions for a location over the next four weeks based on latitude and longitude.
Input parameters
Latitude of the search location, must be between -90 and 90 degrees
Longitude of the search location, must be between -180 and 180 degrees
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
AMBEE_GET_ILI_FORECAST_BY_LAT_LNGTool to retrieve up to 28-day forecast of Influenza-like Illness (ILI) risk using latitude and longitude. Use when you need daily ILI risk levels for a specific location, optionally including pollen and weather details.
Input parameters
Latitude of the search location, must be between -90 and 90 degrees
Longitude of the search location, must be between -180 and 180 degrees
If true, includes pollen (tree/grass/weed counts and risk levels) and weather (temperature, humidity, windSpeed) data alongside the ILI risk. Default is False.
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
AMBEE_GET_POLLEN_FORECAST_BY_PLACETool to retrieve 48-hour pollen forecast for a specific location by place name. Use when you need hourly pollen count predictions including grass, tree, and weed pollen levels with risk assessments.
Input parameters
Name of the location to search for pollen forecast data
Include species-level risk information in the response. When true, provides detailed pollen counts for individual tree, grass, and weed species
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
AMBEE_GET_POLLEN_HISTORY_BY_PLACETool to retrieve historical pollen data for a specific place name. Use after obtaining a valid place name and time range when historical pollen counts and risk levels are needed.
Input parameters
The ending timestamp of the period to search for in the format YYYY-MM-DD hh:mm:ss.
The starting timestamp of the period to search for in the format YYYY-MM-DD hh:mm:ss.
The name of the place to search.
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
AMBEE_GET_POLLEN_LATEST_BY_LAT_LNGTool to retrieve latest pollen data for a specific geographic location using latitude and longitude coordinates. Use when you need current pollen concentration levels and risk assessments for grass, tree, and weed pollen at a location.
Input parameters
Latitude of the search location. Must be between -90 and 90 degrees.
Longitude of the search location. Must be between -180 and 180 degrees.
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
AMBEE_GET_POLLEN_LATEST_BY_PLACETool to retrieve latest pollen data for a specific place by name. Use when current pollen count and risk levels are needed for allergy awareness.
Input parameters
The name of the place to search for pollen 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
AMBEE_GET_WEATHER_FORECAST_BY_LAT_LNGTool to retrieve weather forecast for a specific latitude and longitude (up to 72 hours). Use when you need predicted weather data based on geographic coordinates with customizable time intervals.
Input parameters
Latitude of the search location, must be between -90 and 90 degrees
Longitude of the search location, must be between -180 and 180 degrees
Averaging interval for forecast data. Can be 'minutely', 'hourly', or 'daily'. If not specified, defaults to the API's default interval.
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
AMBEE_GET_WEATHER_LATEST_BY_LAT_LNGTool to retrieve current weather data for a specific latitude and longitude, including temperature, pressure, humidity, and wind conditions. Use when you need real-time weather information for given coordinates.
Input parameters
Latitude of the search location. Must be between -90 and 90 degrees.
Longitude of the search location. Must be between -180 and 180 degrees.
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
AMBEE_GET_WILDFIRE_BY_LAT_LNGRetrieves real-time wildfire data for a specific geographic location using latitude and longitude coordinates. Returns nearby wildfire incidents including both detected fires (from satellite imagery) and reported fires (from official sources). Each record includes location, detection time, fire category, Fire Radiative Power (FRP), Fire Weather Index (FWI), and confidence level when available. Use this tool when you need to: - Monitor wildfire activity in a specific area - Get real-time fire detection data for coordinates - Check for fire hazards at a particular location - Filter fires by type (detected vs reported) The API returns fires within a radius of the specified coordinates.
Input parameters
Latitude of the search location, must be between -90 and 90 degrees
Longitude of the search location, must be between -180 and 180 degrees
Optional filter to specify fire type. 'detected' returns satellite-detected fires, 'reported' returns officially reported fires from authorities. If not specified, returns both types.
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
AMBEE_GET_WILDFIRE_BY_PLACERetrieves real-time wildfire data for a specific location by place name. Returns wildfire incidents from the last 7 days including both satellite-detected fires and officially reported fires. Each record includes precise location coordinates, detection time, fire intensity metrics (FRP, FWI), fire category, and confidence level. Use this tool when you need to: - Check for active wildfires in a city, state, or country - Monitor fire activity in a specific geographic area - Get recent wildfire detection data without knowing exact coordinates - Filter fires by type (satellite-detected vs officially reported) The API searches within a geographic area around the place name provided. More specific locations (e.g., "San Francisco, CA") return more localized results than broad queries (e.g., "California").
Input parameters
Optional filter for fire type. 'detected' returns satellite-detected fires, 'reported' returns officially reported fires from authorities. Omit to get both types.
Name of the location to search for wildfires. Can be a city, state, or country (e.g., 'San Francisco, CA', 'California', 'Greece'). More specific locations return more localized results.
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
AMBEE_GET_WILDFIRE_RISK_FORECAST_BY_PLACETool to retrieve wildfire risk forecast for a specific place. Use when you need weekly wildfire risk predictions for a location over the next four weeks.
Input parameters
Name of the location to be searched, e.g., 'Leon, Mexico'
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
AMBEE_REVERSE_GEOCODE_BY_LAT_LNGTool to convert geographic coordinates into human-readable location data (address, place name, postal code). Use when you have latitude and longitude and need to get the corresponding address or location details.
Input parameters
Latitude of the location to reverse geocode. Must be between -90 and 90 degrees.
Longitude of the location to reverse geocode. Must be between -180 and 180 degrees.
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 76 agents privately built on Nagent that already use Ambee.
Build on Nagent
Connect Ambee 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 Ambee, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Ambee is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ambee is connected, you configure its 27 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ambee 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 Ambee event fires, the agent kicks off automatically.
Every Ambee 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 Ambee ships with 27 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ambee together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ambee-based workflows tailored to your business.