Storm Glass API

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

✓ Official Vendor SpecData 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.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 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

GET STARTED

Start building with Storm Glass API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Storm Glass API API for, with concrete tasks.

★ Data Enrichment Operations

Use the Storm Glass API to perform data enrichment operations programmatically. The API provides 7 endpoints covering core functionality including get weather data for a point, get biological ocean data for a point, get tide extreme data.

Call GET /weather/point to get weather data for a point

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Storm Glass API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get weather data for a point') and Jentic returns the matching Storm Glass API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Storm Glass API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Clearbit

Alternative data enrichment API

Choose Clearbit when you need a different approach to data enrichment operations

Alternative

Fullcontact

Alternative data enrichment API

Choose Fullcontact when you need a different approach to data enrichment operations

Complementary

Hunter

Complementary data enrichment API

Choose Hunter when you need a complementary approach to data enrichment operations

FAQs

Specific to using Storm Glass API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.