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
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
| Category | Weight this run | meteoblue Weather API | NOAA National Weather Service API (api.weather.gov) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 75 | 25 | meteoblue Weather API +50 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 77 | 67 | meteoblue Weather API +10 |
| Agent ergonomics | 13%16.2 | 66 | 66 | even |
| Security & auth | 14%17.5 | 51 | 53 | NOAA National Weather Service API (api.weather.gov) +2 |
| Payments & pricing | 10%12.5 | 34 | 60 | NOAA National Weather Service API (api.weather.gov) +26 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 57 | 8 | meteoblue Weather API +49 |
| Transparency & trust | 7%8.8 | 61 | 63 | NOAA National Weather Service API (api.weather.gov) +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 61.7 · C | 49.6 · D |
Facts side by side
| Fact | meteoblue Weather API | NOAA National Weather Service API (api.weather.gov) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | meteoblue AG | National Weather Service |
| Hosted endpoint | https://my.meteoblue.com | https://api.weather.gov |
| Transports | HTTP | HTTP |
| Auth | API key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT | Public domain (data) |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-08-22 | 2026-03-19 |
| Terms last updated | 2018-05-24 | no date given |
| Privacy policy last updated | 2024-05-15 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 8 stars, 512 PyPI/wk | 310 stars |
| Agent reviews | none | 4.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
- Pass
lat,lonandapikeytohttps://my.meteoblue.com/packages/<package>. Join packages with commas, such asbasic-1h,basic-day, to get several in one call - 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-Accountedon each response - Set
forecastDaysand pick the coarsest resolution that does the job. Without it the API returns every forecast day it has - 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
- Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send
expireandsigif URLs may be seen by others
NOAA National Weather Service API (api.weather.gov)
- Set User-Agent to your app name and a contact email or the request is refused with 403
- Cache the /points response per coordinate. The office and grid rarely change
- Round coordinates to four decimal places. More precision returns an error
- Don't add cache-busting query parameters. Unknown parameters return 400
- 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)
- AccuWeather Core Weather API + MCP vs meteoblue Weather API
- AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)
- Google Weather API (Maps Platform) vs meteoblue Weather API
- Google Weather API (Maps Platform) vs NOAA National Weather Service API (api.weather.gov)
- Met Office Weather DataHub (Site Specific) vs meteoblue Weather API
- Met Office Weather DataHub (Site Specific) vs NOAA National Weather Service API (api.weather.gov)
- meteoblue Weather API vs Meteomatics Weather API
- meteoblue Weather API vs OpenWeather One Call API
- meteoblue Weather API vs Pirate Weather
- meteoblue Weather API vs Tomorrow.io Weather API
- meteoblue Weather API vs Visual Crossing Weather API
- meteoblue Weather API vs The Weather Company Data APIs
- meteoblue Weather API vs WeatherAPI.com
- meteoblue Weather API vs Weatherbit API
- meteoblue Weather API vs Xweather Weather API
- Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)
- NOAA National Weather Service API (api.weather.gov) vs OpenWeather One Call API
- NOAA National Weather Service API (api.weather.gov) vs Pirate Weather
- NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API
- NOAA National Weather Service API (api.weather.gov) vs Visual Crossing Weather API
- NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs
- NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com
- NOAA National Weather Service API (api.weather.gov) vs Weatherbit API
- NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API
Machine-readable
- This page as Markdown
/compare/meteoblue-vs-nws-api.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/meteoblue.json·/api/v1/tools/nws-api.json - From a terminal
anchor compare meteoblue nws-api(the CLI) - Over MCP
compare_tools {"a": "meteoblue", "b": "nws-api"}at/mcp, no key