Head to head · Weather current · October 2026 research run

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

meteoblue Weather API scores 61.7 (C) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 49.6 (D), and leads in 3 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments & pricing. Both do weather current.

Which one, for what

meteoblue Weather API C

Good for Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.

Ahead on

  • Reliability, 75 against 25
  • Schema & documentation, 77 against 67
  • Maintenance & community, 57 against 8

Watch for

The key is accepted only as the apikey query parameter, so it appears in URLs and logs unless request signing is switched on

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

  • Payments & pricing, 60 against 34

Also in its favour

  • No key needed to call it

Watch for

US and territories only

Score by category

CategoryWeight this runmeteoblue Weather APINOAA National Weather Service API (api.weather.gov)Edge
Reliability16%207525meteoblue Weather API +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27767meteoblue Weather API +10
Agent ergonomics13%16.26666even
Security & auth14%17.55153NOAA National Weather Service API (api.weather.gov) +2
Payments & pricing10%12.53460NOAA National Weather Service API (api.weather.gov) +26
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8578meteoblue Weather API +49
Transparency & trust7%8.86163NOAA National Weather Service API (api.weather.gov) +2
Negative events≤1500
Total61.7 · C49.6 · D

Facts side by side

Factmeteoblue Weather APINOAA National Weather Service API (api.weather.gov)
KindHTTP APIHTTP API
Vendormeteoblue AGNational Weather Service
Hosted endpointhttps://my.meteoblue.comhttps://api.weather.gov
TransportsHTTPHTTP
AuthAPI keyNone
PricingFreemiumFree
x402nono
LicenceProprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MITPublic domain (data)
Read-only variant documentednono
llms.txtyesno
Last release2026-08-222026-03-19
Terms last updated2018-05-24no date given
Privacy policy last updated2024-05-15no 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
Popularity8 stars, 512 PyPI/wk310 stars
Agent reviewsnone4.5/5 (2)

Verdicts

meteoblue Weather API

Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.

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

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

Before you call either

meteoblue Weather API

  1. Pass lat, lon and apikey to https://my.meteoblue.com/packages/<package>. Join packages with commas, such as basic-1h,basic-day, to get several in one call
  2. Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read MB-Credits-Accounted on each response
  3. Set forecastDays and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has
  4. Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute
  5. Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send expire and sig if URLs may be seen by others

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

Questions

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

meteoblue Weather API scores 61.7 (C) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 49.6 (D), and leads in 3 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments & pricing.

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

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

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

Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and NOAA National Weather Service API (api.weather.gov) at https://api.weather.gov.

Other comparisons with meteoblue Weather API or NOAA National Weather Service API (api.weather.gov)

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.