Get an audit

Head to head · Weather forecasts · October 2026 research run

Stormglass API vs Weatherbit API

Weatherbit API scores 57.7 (C) on agent readiness against Stormglass API's 39.9 (E), and leads in 5 of 7 scored categories. Stormglass API leads on security & auth. Both do weather forecasts.

Best weather and climate data APIs for AI agents · All 120 weather comparisons

Stormglass APIStorm Glass AB · HTTP API E39.9/100#914 of 950 Weatherbit APIWeatherbit LLC · HTTP API C57.7/100#599 of 950

Which one, for what

Stormglass API E

Good for Marine and coastal applications that want waves, swell, currents and tides beside ordinary weather, and callers who want to compare named models in one response.

Ahead on

  • Security & auth, 44 against 39

Watch for

No OpenAPI file, llms.txt, official SDK or changelog was found. The docs are eleven Markdown pages

Weatherbit API C

Good for An application that needs forecasts plus specialised datasets (air quality, lightning, soil and degree days) from one paid subscription, queried by coordinates.

Ahead on

  • Reliability, 91 against 34
  • Schema & documentation, 72 against 40
  • Payments & pricing, 30 against 25
  • Maintenance & community, 21 against 15
  • Transparency & trust, 63 against 45

Also in its favour

  • Free to start without a card

Watch for

The key is accepted only as the key query parameter, and the spec lists plain http as a scheme

Score by category

CategoryWeight this runStormglass APIWeatherbit APIEdge
Reliability16%203491Weatherbit API +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24072Weatherbit API +32
Agent ergonomics13%16.26561Stormglass API +4
Security & auth14%17.54439Stormglass API +5
Payments & pricing10%12.52530Weatherbit API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81521Weatherbit API +6
Transparency & trust7%8.84563Weatherbit API +18
Negative events≤1500
Total39.9 · E57.7 · C

Facts side by side

FactStormglass APIWeatherbit API
KindHTTP APIHTTP API
VendorStorm Glass ABWeatherbit LLC
Hosted endpointhttps://api.stormglass.io/v2https://api.weatherbit.io/v2.0
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Storm Glass AB's Terms and Conditions. The Free and Small plans are not for commercial useProprietary service under Weatherbit's terms of service. The free plan's data is under a Creative Commons non-commercial licence. The Python SDK is MIT
Read-only variant documentednono
llms.txtnono
Last release2026-02-262025-08-01
Terms last updatedno date given2025-05-01
Privacy policy last updatedno date given2023-12-26
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone78 PyPI/wk

Verdicts

Stormglass API

A read-only weather and marine API with about 70 hourly parameters, per-source values from named national models, tide data and ERA5 history from 2014. No OpenAPI file, status page, SDK or security page was found, the free plan allows 10 requests a day, and the docs and FAQ disagree on the status code for a spent quota.

Weatherbit API

A read-only weather API with a Swagger 2.0 spec, quota headers on every response and a status page showing 100 per cent on three API monitors over 90 days. The key travels only in the query string, the free plan allows 50 requests a day for non-commercial use, and the last dated API announcement is 1 August 2025.

Before you call either

Stormglass API

  1. Send the key as Authorization: KEY with no Bearer prefix. A missing or wrong key returns 403 with {"errors":{"key":"API key is invalid"}}
  2. Always pass source=sg or a short source list on /weather/point. The default is every source, which multiplies the size of each hourly record
  3. Treat 402 as a spent daily quota, not a billing failure, and stop until the next day. Read meta.requestCount against meta.dailyQuota on each response
  4. Use /historical/point for past dates, at most 10 days a call and nothing newer than about 7 days. /weather/point looks back 14 days only
  5. Send and read all times in UTC. Tide sea levels are relative to the chosen datum (MSL by default) and are not water depth

Weatherbit API

  1. Pass lat and lon. City, postal code and station lookups are accepted, but the docs recommend coordinates and mark station ID as use with caution
  2. Read X-RateLimit-Remaining and X-RateLimit-Reset on each response. Daily quotas reset at 00:00 UTC and a spent quota returns 429 until then
  3. Treat HTTP 204 with an empty body as no data found, not as an error
  4. Split historical requests into ranges of one month or less. History needs the Plus plan or higher and has its own daily quota
  5. Keep the key out of logs. It is part of the URL on every call, so always use https://api.weatherbit.io/v2.0

Questions

Which is better for AI agents, Stormglass API or Weatherbit API?

Weatherbit API scores 57.7 (C) on agent readiness against Stormglass API's 39.9 (E), and leads in 5 of 7 scored categories. Stormglass API leads on security & auth.

Do Stormglass API and Weatherbit API need an API key?

Both need an API key.

Can an agent call Stormglass API and Weatherbit API without installing anything?

Yes. Stormglass API has a hosted endpoint at https://api.stormglass.io/v2 and Weatherbit API at https://api.weatherbit.io/v2.0.

Other comparisons with Stormglass API or Weatherbit API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report