Stormglass Marine and Global Weather API
Stormglass marine and global weather REST API for maritime apps, fishing platforms, sailing tools, and outdoor recreation services to access point-based weather forecasts combining data from multiple meteorological sources (NOAA, ECMWF, Norwegian Meteorological Institute) with specialized marine parameters including wave height, wave direction, wave period, swell, wind speed, current, sea temperature, ice coverage, and tidal data. Enables AI agents to manage marine weather retrieval for boat and sailing route automation, handle wave forecast data for surf and water sports automation, access wind forecast for kite and sailing session planning automation, retrieve sea temperature for aquaculture and diving automation, manage tidal data for coastal navigation automation, handle astronomical data (sunrise, sunset, moon phase) for outdoor timing automation, access weather point forecast for fishing and outdoor recreation automation, retrieve historical marine data for backtesting and analysis automation, manage bio data (fish activity, solunar) for fishing optimization automation, and integrate Stormglass with maritime apps, fishing guides, and outdoor recreation platforms for end-to-end marine weather automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Marine weather. GDPR. API key. EU. Weather model data only, no PII.
⚡ Reliability
Best When
A maritime app, surf forecast, fishing guide, or sailing platform wanting AI agents to access multi-model marine weather including waves, swells, tides, and ocean conditions through Stormglass' developer-friendly marine weather API.
Avoid When
POINT-BASED FORECAST ONLY: Stormglass returns weather for a specific latitude/longitude point not area polygons; automated area weather assumption creates point-only response; automated area weather requires multiple point queries. REQUEST LIMIT IS PER DAY: Stormglass free and paid tiers have daily request limits; automated high-frequency polling exhausts daily limit; automated must implement caching with marine weather update intervals (typically 6-12h for model runs). MULTI-MODEL AGGREGATION MEANS VARYING PARAMETERS: Stormglass returns multiple source values per parameter (noaa, sg, dwd, meteo, icon, etc.); automated single-value assumption creates array of source values; automated must specify preferred source or handle multi-source aggregation. TIDAL DATA IS SEPARATE ENDPOINT: Stormglass tidal data is on a different endpoint (tide endpoint) not the weather endpoint; automated tidal retrieval from weather endpoint creates parameter_not_found; automated tidal integration must use dedicated tide endpoint.
Use Cases
- • Retrieving wave height and swell data for surf forecast app automation agents
- • Fetching wind and tidal data for sailing route planning automation agents
- • Accessing sea temperature and current data for diving and aquaculture automation agents
- • Querying solunar and fish activity data for fishing guide app automation agents
Not For
- • Land-based weather for consumer apps (use OpenWeatherMap or WeatherAPI for simpler land weather)
- • Aviation weather (use dedicated aviation weather APIs for TAF/METAR)
- • Real-time radar or satellite imagery (Stormglass is model-based forecast not live radar)
Interface
Authentication
Stormglass uses API key (Authorization header) for authentication. REST API with JSON. Umeå, Sweden HQ. Founded 2015. Bootstrapped indie developer product. Products: Marine weather, wave forecast, tide, solunar, bio, astronomy, air quality. SDKs: None official. GDPR. Serves maritime apps, surf forecasts, fishing guides, sailing platforms. Competes with NOAA's direct APIs and Windy for marine data.
Pricing
Umeå SE. Indie bootstrapped. Daily request quota pricing. GDPR. Developer-friendly.
Agent Metadata
Known Gotchas
- ⚠ MULTI-SOURCE RESPONSE ARRAY NOT SINGLE VALUE: Stormglass returns each weather parameter as an array of values from different sources (noaa, sg, dwd, icon, etc.); automated single-value assumption creates array response; automated must handle multi-source response and select preferred source or compute average
- ⚠ DAILY REQUEST QUOTA REQUIRES CACHING: Stormglass free tier is 10 requests/day and paid tiers also have daily limits; automated high-frequency polling exhausts quota within hours; automated must cache responses for marine weather update interval (typically 6h)
- ⚠ TIDAL DATA ON SEPARATE ENDPOINT: Stormglass tide data requires the /tide/extremes or /tide/sea-level endpoint not the /weather/point endpoint; automated tidal retrieval from weather endpoint creates empty tidal parameters
- ⚠ PARAMETER SELECTION REQUIRED IN PARAMS: Stormglass requires specifying exact weather parameters in request (waveHeight,swellHeight,windSpeed); automated all-parameters request creates very large response with unused data; automated must request only needed parameters
- ⚠ BIO AND SOLUNAR ARE SEPARATE ENDPOINTS: Stormglass fishing-specific data (solunar, bio) are separate endpoints; automated fishing data from weather endpoint creates missing solunar/bio parameters
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Stormglass Marine and Global Weather API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.