Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Storm Glass Marine Weather, 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.
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%2Fstorm-glass-marine-weather" | shStep 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%2Fstorm-glass-marine-weather" | 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.
What an agent can do with Storm Glass Marine Weather API.
Get hourly forecasts by coordinates
Manage data enrichment data programmatically
Integrate Storm Glass Marine Weather into automated workflows
Query and filter Storm Glass Marine Weather records by parameters
Monitor Storm Glass Marine Weather operational status and events
GET STARTED
Patterns agents use Storm Glass Marine Weather API for, with concrete tasks.
★ Data Enrichment Operations
Use the Storm Glass Marine Weather to perform data enrichment operations programmatically. The API provides 1 endpoints covering core functionality including get hourly forecasts by coordinates.
Call GET /forecast to get hourly forecasts by coordinates
Data Retrieval and Monitoring
Query Storm Glass Marine Weather resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Storm Glass Marine Weather endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Storm Glass Marine Weather endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get hourly forecasts by coordinates', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — global marine weather data from multiple sources in one single api with hourly resolution.
METHOD
PATH
DESCRIPTION
/forecast
Get hourly forecasts by coordinates
/forecast
Get hourly forecasts by coordinates
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Storm Glass Marine Weather by hand means sending its key in the Authentication-Token header on every call to api.stormglass.io and passing the coordinate and parameter query fields for each forecast yourself. Through Jentic you install once, import Storm Glass Marine Weather from the API Directory, store the API key once, and your agent calls it.
Permission scoping
This API takes the location in query parameters rather than a resource id in the URL path, so scope by operation: this endpoint exposes a single read operation, fetching a marine forecast by coordinates, and you decide whether the agent may call it. Nothing beyond the operations you add is available to the agent.
Credential isolation
Your Storm Glass Marine Weather 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 Jentic by intent such as 'get an hourly marine forecast for a location', and Jentic returns the matching Storm Glass Marine Weather operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Storm Glass Marine Weather API through Jentic.
What authentication does the Storm Glass Marine Weather use?
The Storm Glass Marine Weather uses an API key passed in the `Authentication-Token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get hourly forecasts by coordinates with the Storm Glass Marine Weather?
Yes. Use the GET /forecast endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Storm Glass Marine Weather?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get hourly forecasts by coordinates through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get hourly forecasts by coordinates'. Jentic returns the matching Storm Glass Marine Weather operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Storm Glass Marine Weather have?
The Storm Glass Marine Weather exposes 1 endpoints covering forecast operations.
Can I limit what my agent is allowed to do with the Storm Glass Marine Weather API?
Yes. Because you run Jentic One yourself, you decide which operations your agent may call, and the Storm Glass Marine Weather API exposes only a single read operation: GET /forecast, which fetches an hourly marine forecast by coordinates. Add that operation if you want the agent to retrieve forecasts, or leave it out entirely, since nothing beyond the operations you add is available to the agent. Your API key is held by your own instance and injected at call time, so the agent never gains access to the credential or to any endpoint you have not scoped in.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically get hourly forecasts by coordinates. Covers 1 operations with apiKey authentication.
Use for: I need to hourly forecasts by coordinates, Find available data enrichment operations, Get the current status of Storm Glass Marine Weather resources, List all records from Storm Glass Marine Weather
Not supported: Does not handle payments, communications, or crm - use for data enrichment only.
Global marine weather data from multiple sources in one single API with hourly resolution. Get your API key by visiting the Storm Glass web site. The API exposes 1 endpoints secured with apiKey authentication.