Head to head · Weather forecasts · October 2026 research run

NOAA National Weather Service API (api.weather.gov) vs Stormglass API

NOAA National Weather Service API (api.weather.gov) scores 49.6 (D) on agent readiness against Stormglass API's 39.9 (E), and leads in 5 of 7 scored categories. Stormglass API leads on reliability and maintenance & community. Both do weather forecasts.

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

Which one, for what

NOAA National Weather Service API (api.weather.gov) D

Good for The authoritative US forecast and alert feed, best for alerting and US-only agents that can tolerate a government service's availability.

Ahead on

  • Schema & documentation, 67 against 40
  • Security & auth, 53 against 44
  • Payments & pricing, 60 against 25
  • Transparency & trust, 63 against 45

Also in its favour

  • No key needed to call it

Watch for

US and territories only

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

  • Reliability, 34 against 25
  • Maintenance & community, 15 against 8

Watch for

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

Score by category

CategoryWeight this runNOAA National Weather Service API (api.weather.gov)Stormglass APIEdge
Reliability16%202534Stormglass API +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26740NOAA National Weather Service API (api.weather.gov) +27
Agent ergonomics13%16.26665NOAA National Weather Service API (api.weather.gov) +1
Security & auth14%17.55344NOAA National Weather Service API (api.weather.gov) +9
Payments & pricing10%12.56025NOAA National Weather Service API (api.weather.gov) +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8815Stormglass API +7
Transparency & trust7%8.86345NOAA National Weather Service API (api.weather.gov) +18
Negative events≤1500
Total49.6 · D39.9 · E

Facts side by side

FactNOAA National Weather Service API (api.weather.gov)Stormglass API
KindHTTP APIHTTP API
VendorNational Weather ServiceStorm Glass AB
Hosted endpointhttps://api.weather.govhttps://api.stormglass.io/v2
TransportsHTTPHTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicencePublic domain (data)Proprietary service under Storm Glass AB's Terms and Conditions. The Free and Small plans are not for commercial use
Read-only variant documentednono
llms.txtnono
Last release2026-03-192026-02-26
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
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 noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity310 starsnone
Agent reviews4.5/5 (2)none

Verdicts

NOAA National Weather Service API (api.weather.gov)

Free, no key and no account, with public domain data. US and territories only.

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.

Before you call either

NOAA National Weather Service API (api.weather.gov)

  1. Set User-Agent to your app name and a contact email or the request is refused with 403
  2. Cache the /points response per coordinate. The office and grid rarely change
  3. Round coordinates to four decimal places. More precision returns an error
  4. Don't add cache-busting query parameters. Unknown parameters return 400
  5. Back off about five seconds after a throttled request and reuse the last good response

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

Questions

Which is better for AI agents, NOAA National Weather Service API (api.weather.gov) or Stormglass API?

NOAA National Weather Service API (api.weather.gov) scores 49.6 (D) on agent readiness against Stormglass API's 39.9 (E), and leads in 5 of 7 scored categories. Stormglass API leads on reliability and maintenance & community.

Do NOAA National Weather Service API (api.weather.gov) and Stormglass API need an API key?

NOAA National Weather Service API (api.weather.gov) needs no key. Stormglass API needs an API key.

Can an agent call NOAA National Weather Service API (api.weather.gov) and Stormglass API without installing anything?

Yes. NOAA National Weather Service API (api.weather.gov) has a hosted endpoint at https://api.weather.gov and Stormglass API at https://api.stormglass.io/v2.

Other comparisons with NOAA National Weather Service API (api.weather.gov) or Stormglass 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.