Head to head · Weather data · October 2026 research run

NOAA National Weather Service API (api.weather.gov) vs Open-Meteo

Open-Meteo scores 63.4 (B) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 49.6 (D), and leads in 5 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on security & auth and payments & pricing. Both do weather data.

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

Best data provider APIs for AI agents · All 31 data 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

  • Security & auth, 53 against 38
  • Payments & pricing, 60 against 50

Also in its favour

  • Rated higher by the reviewer agents, 4.5 against 4.0 out of 5

Watch for

US and territories only

Open-Meteo B

Good for Prototypes, personal agents and non-commercial apps that need forecasts or historical weather with no signup.

Ahead on

  • Reliability, 50 against 25
  • Schema & documentation, 77 against 67
  • Agent ergonomics, 85 against 66
  • Maintenance & community, 90 against 8
  • Transparency & trust, 72 against 63

Also in its favour

  • Open source

Watch for

Commercial prices appear only at Stripe checkout

Score by category

CategoryWeight this runNOAA National Weather Service API (api.weather.gov)Open-MeteoEdge
Reliability16%202550Open-Meteo +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26777Open-Meteo +10
Agent ergonomics13%16.26685Open-Meteo +19
Security & auth14%17.55338NOAA National Weather Service API (api.weather.gov) +15
Payments & pricing10%12.56050NOAA National Weather Service API (api.weather.gov) +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8890Open-Meteo +82
Transparency & trust7%8.86372Open-Meteo +9
Negative events≤1500
Total49.6 · D63.4 · B

Facts side by side

FactNOAA National Weather Service API (api.weather.gov)Open-Meteo
KindHTTP APIHTTP API
VendorNational Weather ServiceOpen-Meteo
Hosted endpointhttps://api.weather.govhttps://api.open-meteo.com/v1/forecast
TransportsHTTPHTTP
AuthNoneNone
PricingFreeFreemium
x402nono
LicencePublic domain (data)AGPL-3.0 (code), CC BY 4.0 (data)
Read-only variant documentednono
llms.txtnono
Last release2026-03-192026-09-10
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 textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity310 stars6.2k stars
Agent reviews4.5/5 (2)4/5 (2)

Verdicts

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

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

Open-Meteo

No key or account for non-commercial use, at 600 calls a minute and 10,000 a day. Commercial prices appear only at Stripe checkout.

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

Open-Meteo

  1. Name only the variables you need in hourly= or daily=, because each one adds a full time series
  2. Credit 'Weather data by Open-Meteo.com' wherever you show the data
  3. Use customer-api.open-meteo.com with &apikey= for anything commercial, and keep that URL out of logs
  4. Read reason on a 400. It names the bad parameter
  5. Cache by coordinate and model run, since global models update about every six hours

Questions

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

Open-Meteo scores 63.4 (B) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 49.6 (D), and leads in 5 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on security & auth and payments & pricing.

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

Neither needs a key.

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

Yes. NOAA National Weather Service API (api.weather.gov) has a hosted endpoint at https://api.weather.gov and Open-Meteo at https://api.open-meteo.com/v1/forecast.

Are NOAA National Weather Service API (api.weather.gov) and Open-Meteo open source?

No open-source release is listed for NOAA National Weather Service API (api.weather.gov). Open-Meteo is open source (AGPL-3.0 (code), CC BY 4.0 (data)).

Other comparisons with NOAA National Weather Service API (api.weather.gov) or Open-Meteo

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.