Storm Glass APIs for AI Agents
Data EnrichmentData TransformationContact EnrichmentMixed ProvenanceAPI keyAgent Ready
For Agents
APIs2 in catalogue
Endpoints8 indexed
AuthAPI key — 1 credential for all 2 APIs
ProvenanceMixed provenance
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.
Storm Glass aggregates marine and weather data from several forecast sources into point-based lookups, so an agent asks for a single coordinate and gets weather, ocean, tide, astronomy, and elevation values back rather than stitching together separate providers.
Storm Glass API Catalog
2 APIs across 1 product group. All share one credential.
Which Storm Glass API should I use?
| I want to... | Use |
|---|---|
| Weather, tide, astronomy, elevation, or biological ocean data for a point | Storm Glass API |
| A single hourly marine forecast for a coordinate | Storm Glass Marine Weather |
Install Jentic One Beta
Connect the Storm Glass APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Storm Glass APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstormglass.io" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstormglass.io" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “get marine weather and tide data for a coordinate”.
What AI Agents Can Do with Storm Glass
Each workflow spans multiple Storm Glass APIs. Jentic routes each operation to the right API automatically.
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.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
FAQs
Specific to using Storm Glass APIs through Jentic.
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.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.