canonical: https://jentic.com/apis/stormglass.io # Storm Glass APIs Storm Glass provides global marine and weather data from multiple forecast sources through a set of point-based APIs. Agents can retrieve weather, biological ocean, tide, astronomy, and elevation data for any coordinate, plus hourly marine forecasts, all returned as structured JSON keyed to a latitude and longitude. ## For AI agents An agent can fetch weather, tide extremes, sea level, astronomy, elevation, and biological ocean data for any point on the globe, list tide stations in an area, and pull hourly marine forecasts by coordinates across Storm Glass's two APIs. ## Scope Use for: Reading marine and weather data (weather, tide, sea level, astronomy, elevation, biological ocean, and hourly marine forecasts) for a point by coordinates Not supported: - writing data - payments - communications - crm - geocoding addresses ## APIs | API | Category | Endpoints | Description | | --- | --- | --- | --- | | Storm Glass API | data-enrichment | 7 | Programmatically get weather data for a point, get biological ocean data for a point. | | Storm Glass Marine Weather | data-enrichment | 1 | Programmatically get hourly forecasts by coordinates. | ## Which API to use | Need | API | Why | | --- | --- | --- | | Weather, tide, astronomy, elevation, or biological ocean data for a point | storm-glass | Exposes seven endpoints covering weather, bio, tide extremes, sea level, tide stations, astronomy, and elevation for any coordinate. | | A single hourly marine forecast for a coordinate | main | A one-endpoint API that returns hourly marine forecast values by latitude and longitude. | ## Cross-API use cases ### Full marine conditions brief for a coordinate An agent pulls the hourly marine forecast from the single-endpoint API and enriches it with tide extremes, sea level, and astronomy data from the multi-endpoint API to build one conditions brief for a location. Example prompt: Call the forecast endpoint on main for the coordinate, then call weather, tide, and astronomy point endpoints on storm-glass and merge the results into one brief. ### Cross-check forecasts across both APIs An agent retrieves the hourly forecast from one API and the weather point data from the other for the same coordinate, then compares the values to flag divergence between the two data sources. Example prompt: Fetch forecast from main and weather/point from storm-glass for the same latitude and longitude, then compare the overlapping fields and report any differences. ## Why Jentic - **Setup:** Wiring Storm Glass by hand means sending its API key in each API's expected header on every call and passing coordinate and parameter query fields for each request. Through Jentic you install once, add the Storm Glass APIs you need from the Jentic API Directory, store the API key once, and your agent calls them. - **Permission scoping:** Both Storm Glass APIs are read-only and take location in query parameters rather than a resource id in the path, so you scope by operation. Your own Jentic One rules decide which point lookups the agent may call, and only the operations you add are available to it. - **Credential handling:** Your Storm Glass API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search the Jentic directory by intent such as 'get weather data for a point' or 'get an hourly marine forecast for a location', and Jentic returns the matching Storm Glass operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related vendors - **OpenWeatherMap** — Alternative weather data provider offering point-based forecasts and current conditions by coordinate. - **WeatherAPI** — Alternative weather API with forecast, astronomy, and marine data lookups by location. - **NOAA** — Public source for marine, tide, and ocean observation data that complements Storm Glass forecasts. ## FAQ ### What can an agent do across the Storm Glass APIs? An agent can read weather, biological ocean, tide extreme, sea level, astronomy, and elevation data for any coordinate through the Storm Glass API, list tide stations in an area, and fetch hourly marine forecasts by coordinates through the Storm Glass Marine Weather API. All responses come back as structured JSON keyed to a latitude and longitude. ### Do the two Storm Glass APIs share one credential? Yes. Both APIs authenticate with the same Storm Glass API key tied to your account. They read the key from different request headers, but a single Storm Glass account credential works for both. ### Are the Storm Glass APIs read-only? Yes. Every operation across both APIs retrieves data by coordinate. There are no write, update, or delete operations, so an agent can only fetch marine and weather values, never modify anything. ### How do the two APIs differ in coverage? The Storm Glass API is broader, with seven endpoints spanning weather, bio, tide, astronomy, and elevation. The Storm Glass Marine Weather API has a single endpoint focused on hourly marine forecasts by coordinates. ### Can an agent combine data from both APIs in one workflow? Yes. Because both take a coordinate as input and return JSON, an agent can pull an hourly forecast from one API and enrich it with tide, astronomy, or weather point data from the other to assemble a single view for a location. ### Do the Storm Glass APIs handle addresses or geocoding? No. Every endpoint expects a latitude and longitude. Converting a place name or address into coordinates is outside the scope of these APIs and would need a separate geocoding service.