Install Jentic One Beta

Connect the Storm Glass API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Storm Glass API, 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-api" | sh

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%2Fstorm-glass-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Storm Glass API.

Get weather data for a point

List tide stations in area

Integrate Storm Glass API into automated workflows

Query and filter Storm Glass API records by parameters

Monitor Storm Glass API operational status and events

GET STARTED

Start building with Storm Glass API

Explore with Jentic One

View OpenAPI Document

Automated Weather Management

Automate weather operations by combining multiple Storm Glass API endpoints. Agents can get biological ocean data for a point and then get tide extreme data in a single workflow.

Call GET /bio/point to get biological ocean data for a point, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Storm Glass API 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 weather data for a point', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — global marine weather data from multiple sources.

METHOD

PATH

DESCRIPTION

GET

/weather/point

Get weather data for a point

GET

/bio/point

Get biological ocean data for a point

GET

/tide/extremes/point

Get tide extreme data

GET

/tide/sea-level/point

Get sea level data

GET

/tide/station/area

List tide stations in area

GET

/astronomy/point

Get astronomy data for a point

GET

/elevation/point

Get elevation data for a point

GET

/weather/point

Get weather data for a point

GET

/bio/point

Get biological ocean data for a point

GET

/tide/extremes/point

Get tide extreme data

GET

/tide/sea-level/point

Get sea level data

GET

/tide/station/area

List tide stations in area

GET

/astronomy/point

Get astronomy data for a point

GET

/elevation/point

Get elevation data for a point

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Storm Glass API by hand means sending its key in the Authorization header on every call to api.stormglass.io/v2 and passing the coordinate and parameter query fields for each point request yourself. Through Jentic you install once, import the Storm Glass API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Storm Glass takes the location in query parameters rather than a resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as reading weather, tide, or astronomy data for a point. This is a read-only data API, and only the operations you add are available to the agent.

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 Jentic by intent such as 'get weather data for a point' or 'get tide extremes for a location', and Jentic returns the matching Storm Glass API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Storm Glass API through Jentic.

What authentication does the Storm Glass API use?

The Storm Glass API uses an API key passed in the `Authorization` 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 weather data for a point with the Storm Glass API?

Yes. Use the GET /weather/point endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Storm Glass API?

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 weather data for a point through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get weather data for a point'. Jentic returns the matching Storm Glass API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Storm Glass API have?

The Storm Glass API exposes 7 endpoints covering weather, bio, tide operations.

Can I limit what my agent is allowed to do with the Storm Glass API?

Yes. Because Jentic One is self-hosted, you decide which Storm Glass operations your agent can call, and only the ones you add are available to it. Since Storm Glass is a read-only data API that takes the location in query parameters rather than a resource id in the path, you scope access by operation, for example allowing weather data for a point while withholding tide or astronomy reads. Your API key is held by your own Jentic One instance and injected at execution time, so the agent never sees the raw credential.

Storm Glass API

Name: Storm Glass API
Brand: Storm Glass API
Availability: InStock

Browse all Stormglass APIs

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey7 EndpointsREST

For Agents

Programmatically get weather data for a point, get biological ocean data for a point. Covers 7 operations with apiKey authentication.

Use for: I need to weather data for a point, I want to biological ocean data for a point, Search for tide extreme data, Find all sea level data

Not supported: Does not handle payments, communications, or crm - use for data enrichment only.

Global marine weather data from multiple sources. Provides weather, bio, tide, astronomy, and elevation data for any point on the globe. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Storm Glass API to your agent

Capabilities

Start building with Storm Glass API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Storm Glass API