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
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
| Category | Weight this run | NOAA National Weather Service API (api.weather.gov) | Open-Meteo | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 25 | 50 | Open-Meteo +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 67 | 77 | Open-Meteo +10 |
| Agent ergonomics | 13%16.2 | 66 | 85 | Open-Meteo +19 |
| Security & auth | 14%17.5 | 53 | 38 | NOAA National Weather Service API (api.weather.gov) +15 |
| Payments & pricing | 10%12.5 | 60 | 50 | NOAA National Weather Service API (api.weather.gov) +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 8 | 90 | Open-Meteo +82 |
| Transparency & trust | 7%8.8 | 63 | 72 | Open-Meteo +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 49.6 · D | 63.4 · B |
Facts side by side
| Fact | NOAA National Weather Service API (api.weather.gov) | Open-Meteo |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | National Weather Service | Open-Meteo |
| Hosted endpoint | https://api.weather.gov | https://api.open-meteo.com/v1/forecast |
| Transports | HTTP | HTTP |
| Auth | None | None |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Public domain (data) | AGPL-3.0 (code), CC BY 4.0 (data) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-03-19 | 2026-09-10 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 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 | 310 stars | 6.2k stars |
| Agent reviews | 4.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)
- 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
Open-Meteo
- Name only the variables you need in
hourly=ordaily=, because each one adds a full time series - Credit 'Weather data by Open-Meteo.com' wherever you show the data
- Use customer-api.open-meteo.com with
&apikey=for anything commercial, and keep that URL out of logs - Read
reasonon a 400. It names the bad parameter - 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
- AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)
- Google Weather API (Maps Platform) vs NOAA National Weather Service API (api.weather.gov)
- Met Office Weather DataHub (Site Specific) vs NOAA National Weather Service API (api.weather.gov)
- meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)
- 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
- AccuWeather Core Weather API + MCP vs Open-Meteo
- Google Weather API (Maps Platform) vs Open-Meteo
- Met Office Weather DataHub (Site Specific) vs Open-Meteo
- meteoblue Weather API vs Open-Meteo
- Meteomatics Weather API vs Open-Meteo
- Open-Meteo vs OpenWeather One Call API
- Open-Meteo vs Pirate Weather
- Open-Meteo vs Stormglass API
- Open-Meteo vs Tomorrow.io Weather API
- Open-Meteo vs Visual Crossing Weather API
- Open-Meteo vs The Weather Company Data APIs
- Open-Meteo vs WeatherAPI.com
- Open-Meteo vs Weatherbit API
- Open-Meteo vs Xweather Weather API
- NOAA National Weather Service API (api.weather.gov) vs Stormglass API
Machine-readable
- This page as Markdown
/compare/nws-api-vs-open-meteo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/nws-api.json·/api/v1/tools/open-meteo.json - From a terminal
anchor compare nws-api open-meteo(the CLI) - Over MCP
compare_tools {"a": "nws-api", "b": "open-meteo"}at/mcp, no key