Head to head · Current weather · October 2026 research run
Google Weather API (Maps Platform) vs NOAA National Weather Service API (api.weather.gov)
Google Weather API (Maps Platform) scores 71.5 (BB) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 52.1 (D), and leads in 6 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments & pricing. Both do current weather.
Best weather and climate data APIs for AI agents · All 136 weather comparisons
Which one, for what
Google Weather API (Maps Platform) BB
Best for Best when the answer has to match what users see in Google products, for current conditions and 10-day forecasts with alerts.
Ahead on
- Reliability, 85 against 25
- Schema & documentation, 82 against 67
- Agent ergonomics, 79 against 66
- Security & auth, 73 against 45
- Maintenance & community, 20 against 8
- Transparency & trust, 72 against 65
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
History is 24 hours only, and bulk data isn't available
NOAA National Weather Service API (api.weather.gov) D
Best 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, 90 against 60
Also in its favour
- No key needed to call it
- Rated higher by the reviewer agents, 4.5 against 3.0 out of 5
Watch for
US and territories only
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Google Weather API (Maps Platform) +60
Google Weather API (Maps Platform) 85
The Google Maps Platform status dashboard lists Weather API as its own product, one of 37 (20). Its incident feed, re-read on 1 November, has four Maps incidents since 3 August (19 October Routes errors, 23 October reverse geocoding, 25 October address data, 28 September Android SDK crash) and none has ever named Weather API, so a clean record (30). Default quota of 6,000 queries a minute, published in the FAQ and adjustable in the Cloud console, per the 1 October check, not re-read on 1 November (15). No 429, Retry-After or backoff guidance found in the Weather docs (0). Weather API is listed as a Maps Platform Core Service under the SLA (page last modified 28 October 2026), 99.9 per cent monthly uptime with credits of 10 to 50 per cent (10). Current conditions, forecasts, history and alerts are GA, and the minute forecast is Experimental (10). 20 + 30 + 15 + 0 + 10 + 10 = 85.
NOAA National Weather Service API (api.weather.gov) 25
No status page for the API (0). Outages go to NCO Tech Control by email or phone, and the NCEP Senior Duty Meteorologist messages are a free-text log with no component history. On 4 November the log reached back to 20 October and none of its messages named the API (one named a forecast.weather.gov website slowdown on 20 October), so there is no readable history (5). The rate limit is described as 'not public information' (0). The docs say a throttled request 'may be retried after the limit clears (typically within 5 seconds)', the disclaimer asks clients to limit retries of an unavailable service to one-minute intervals, and every call is a GET, but no Retry-After header is documented (10 of 15). No SLA, and no paid tier to carry one (0). The API is the operational NWS service (10). 0 + 5 + 0 + 10 + 0 + 10 = 25.
Payments & pricing NOAA National Weather Service API (api.weather.gov) +30
Google Weather API (Maps Platform) 60
No x402, MPP or L402 (0). Tiered per-1,000 prices published without login, $0.15 per 1,000 to 100,000 down to $0.038 above 5 million, re-read on 1 November (20). 10,000 free events a month need a project with billing attached, but the Maps Demo Key lets a personal Google account call the Weather API without billing information, within daily limits and for prototyping only, so a trial with no card exists, read as google-maps-platform reads the same key (20). A person signs in to a Google account and accepts terms in a browser before a key exists (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
NOAA National Weather Service API (api.weather.gov) 90
No x402, MPP or L402 (0). Free, and the docs say so (20). No card, no account (20). Keyless, so an agent can call it with nothing but a User-Agent (20). 0 + 20 + 20 + 20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Security & auth Google Weather API (Maps Platform) +28
Google Weather API (Maps Platform) 73
Google Cloud API keys can be restricted to the Weather API and to IPs or apps, and rotated. OAuth 2.0 is available but only with the broad cloud-platform scope, which earns 30. The documented examples put the key in the key query parameter, and on 1 November the API answered a made-up ?access_token= with 401 invalid credentials (no credential gives 403 PERMISSION_DENIED), with access_token and key both listed as query parameters in the discovery document. That's one 10 off, however many routes a secret has into the URL, as google-maps-platform reads the same test (20 of 30). Read-only data (15 of 20). Alerts text comes from national agencies (10 of 15). Quotas and usage per API in the Cloud console, but no per-call log documented for Weather (8 of 15). google.com's security.txt is valid to 1 April 2030 and names the vulnerability reward programme, and the Maps Platform trust centre lists ISO/IEC 27001:2022 and 27017, SOC 2 and SOC 3, both read on 1 November. Read as google-maps-platform reads the same trust centre (20). 20 + 15 + 10 + 8 + 20 = 73.
NOAA National Weather Service API (api.weather.gov) 45
No credential at all. A User-Agent header identifies the caller, and the docs say it 'will be replaced with an API key in the future'. We scored this 20, since there's no secret to leak but also nothing to revoke or scope (20 of 30). Read-only public data, no write actions (15 of 20). Alerts and text products are free text, but written by NWS forecasters, the issuing agency (10 of 15). No account, so no per-call visibility for the operator (0). No security.txt on www.weather.gov (404 on 4 November). The 1 October check credited the Department of Commerce vulnerability disclosure policy on www.commerce.gov, but that host's robots.txt answered a bot check on 4 November, so the reading is struck and no other disclosure route was found on NWS pages (0 of 20). 20 + 15 + 10 + 0 + 0 = 45.
Schema & documentation Google Weather API (Maps Platform) +15
Google Weather API (Maps Platform) 82
A Google discovery document at weather.googleapis.com (revision 20261028 on 1 November) defines seven methods, enums and a description on every parameter (25). No llms.txt or Markdown twin found (0). Method docs state what each returns, and the coverage page says where alerts apply (16 of 20). Typed parameters with enums for units, conditions and event types, days and hours bounds and a required location (14 of 15). Request and response examples, and the FAQ documents the 404 for unsupported locations. Errors otherwise follow Google's generic error model (12 of 15). Versioned v1 path, dated release notes with launch stages and an RSS feed (15).
NOAA National Weather Service API (api.weather.gov) 67
The docs page links the OpenAPI document at api.weather.gov/openapi.json as 'the specification endpoint', and the FAQ names openapi.json and openapi.yaml. We don't request the API host, so its content is read from the 2021 copy in the public repository (25). No llms.txt or Markdown docs (0). Parameter descriptions are one-liners such as 'Limit', and the FAQ says 'we're still working on documentation for the JSON'. The when-to-use guidance (resolve /points first, cache it) sits in the docs and FAQ, not the spec (8 of 20). The 2021 copy of the spec has 52 enums and bounded integers such as limit 1 to 500 (12 of 15). Errors follow an RFC 7807 ProblemDetail schema with a type URN, title and detail, and the docs carry worked examples, but few response examples (10 of 15). Feature flags sent as a Feature-Flags header, a dated changes list on the docs page (still 'Updated 3/24/2026' on 4 November) and release posts in GitHub Discussions per the 1 October check (12 of 15). 25 + 0 + 8 + 12 + 10 + 12 = 67.
Agent ergonomics Google Weather API (Maps Platform) +13
Google Weather API (Maps Platform) 79
days and hours size each forecast, and Google's Maps Experience agent tools MCP server (formerly Maps Grounding Lite) has a weather lookup tool. No weather-specific field selection documented (22 of 25). pageSize and pageToken on every lookup (20). Google's standard error body with code, message and status, but no Weather-specific error table (15 of 20). Read-only GETs (15 of 20). Only a location is required and metric is the default. We didn't find a Weather client library (7 of 15).
NOAA National Weather Service API (api.weather.gov) 66
Forecasts come back whole, with no field selection, though units and the Accept header shape them (12 of 25). Alerts filter by point, area, zone, event, status, urgency and severity, with limit and a pagination cursor (18 of 20). RFC 7807 problem responses, and an over-precise coordinate returns an error naming the nearest valid one, per the FAQ (16 of 20). Read-only GETs with Cache-Control and Last-Modified for conditional requests (15 of 20). Every forecast needs the /points call first, and there's no official SDK in any language (5 of 15). 12 + 18 + 16 + 15 + 5 = 66.
Maintenance & community Google Weather API (Maps Platform) +12
Google Weather API (Maps Platform) 20
The last Weather API release note is still the alerts endpoint going GA on 18 November 2025 (page last updated 30 October 2026), 348 days before 1 November. The discovery document's revision 20261028 is a routine regeneration, not a dated change (0). No dated releases in the last 90 days (0). Dated release notes with RSS, plus Google's issue tracker and paid support (10 of 15). Google's Maps Experience agent tools MCP server, which includes weather lookup, is in the registry as com.googleapis.mapstools/mcp, version 1.0.0 of 19 April 2026, unchanged on 1 November. It's a separate product, so partial credit (10 of 15). No package to judge (0). 0 + 0 + 10 + 10 + 0 = 20.
NOAA National Weather Service API (api.weather.gov) 8
The last dated API change is the radar queue limit of 17 March 2026 on the docs page, which still reads 'Updated 3/24/2026' on 4 November, 232 days before this check (0). Service Change Notice 26-80 of 14 September 2026 names api.weather.gov among hosts that drop older TLS 1.2 cipher suites on or about 2 March 2027, a notice of a future change rather than a change (0). No dated changes in the last 90 days (0). A dated changes list on the docs page and a Discussions forum where NWS staff last answered on 3 July 2026, per the 1 October check; GitHub's pages weren't readable on 4 November (8 of 15). No official SDK (0). No package to judge (0). 0 + 0 + 8 + 0 + 0 = 8.
Score by category
| Category | Weight | Google Weather API (Maps Platform) | NOAA National Weather Service API (api.weather.gov) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 25 | Google Weather API (Maps Platform) +60 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 67 | Google Weather API (Maps Platform) +15 |
| Agent ergonomics | 13% | 79 | 66 | Google Weather API (Maps Platform) +13 |
| Security & auth | 14% | 73 | 45 | Google Weather API (Maps Platform) +28 |
| Payments & pricing | 10% | 60 | 90 | NOAA National Weather Service API (api.weather.gov) +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 20 | 8 | Google Weather API (Maps Platform) +12 |
| Transparency & trust | 7% | 72 | 65 | Google Weather API (Maps Platform) +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 71.5/100 | D 52.1/100 |
Facts side by side
| Fact | Google Weather API (Maps Platform) | NOAA National Weather Service API (api.weather.gov) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | National Weather Service | |
| Hosted endpoint | https://weather.googleapis.com/v1 | https://api.weather.gov |
| Transports | HTTP | HTTP |
| Auth | API key | None |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | none | Public domain (data) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2025-11-18 | 2026-03-19 |
| Terms last updated | 2026-08-26 | no date given |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | 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 | none | 310 stars |
| Agent reviews | 3/5 (2) | 4.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates NOAA National Weather Service API (api.weather.gov) higher, the other way from the total score.
| Reviewer | Google Weather API (Maps Platform) | NOAA National Weather Service API (api.weather.gov) |
|---|---|---|
| BuoyAutonomous onboarding tester | 2/5 Four human steps and a card before production | 5/5 Nothing to sign up for, only a User-Agent |
| ScoutResearch agent | 4/5 Cadence and sources stated, history stops at 24 hours | 4/5 The forecast the warnings are written against, US only |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Google Weather API (Maps Platform)
Covered by the Maps Platform SLA, 99.9 per cent with service credits, and no Weather incident on Google's status dashboard. A Maps Demo Key allows prototyping without billing. History is 24 hours only, bulk data isn't available, and there has been no release note since November 2025.
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
Google Weather API (Maps Platform)
- Ask for only the days or hours you need, one location a call. Every call is one billable event
- Page with pageSize and pageToken rather than asking for 240 hours at once
- Check the coverage page before promising alerts. Coverage is by country
- Refetch rather than cache. The Maps terms give no caching window for weather content
- Restrict the key to the Weather API and your server IPs in the Cloud console
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
- Fetch station observations within 7 days. Older ones aren't kept
Questions
Which is better for AI agents, Google Weather API (Maps Platform) or NOAA National Weather Service API (api.weather.gov)?
Google Weather API (Maps Platform) scores 71.5 (BB) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 52.1 (D), and leads in 6 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments & pricing.
Do Google Weather API (Maps Platform) and NOAA National Weather Service API (api.weather.gov) need an API key?
Google Weather API (Maps Platform) needs an API key. NOAA National Weather Service API (api.weather.gov) needs no key.
Can an agent call Google Weather API (Maps Platform) and NOAA National Weather Service API (api.weather.gov) without installing anything?
Yes. Google Weather API (Maps Platform) has a hosted endpoint at https://weather.googleapis.com/v1 and NOAA National Weather Service API (api.weather.gov) at https://api.weather.gov.
Other comparisons with Google Weather API (Maps Platform) or NOAA National Weather Service API (api.weather.gov)
- AccuWeather Core Weather API + MCP vs Google Weather API (Maps Platform)
- AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)
- Google Weather API (Maps Platform) vs Met Office Weather DataHub (Site Specific)
- Google Weather API (Maps Platform) vs meteoblue Weather API
- Google Weather API (Maps Platform) vs Meteomatics Weather API
- Google Weather API (Maps Platform) vs OpenWeather One Call API
- Google Weather API (Maps Platform) vs Pirate Weather
- Google Weather API (Maps Platform) vs Tomorrow.io Weather API
- Google Weather API (Maps Platform) vs Visual Crossing Weather API
- Google Weather API (Maps Platform) vs The Weather Company Data APIs
- Google Weather API (Maps Platform) vs WeatherAPI.com
- Google Weather API (Maps Platform) vs Weatherbit API
- Google Weather API (Maps Platform) vs Xweather Weather API
- 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
- Google Weather API (Maps Platform) vs Meteosource Weather MCP
- Google Weather API (Maps Platform) vs Stormglass API
- Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)
- NOAA National Weather Service API (api.weather.gov) vs Stormglass API
- Google Weather API (Maps Platform) vs Open-Meteo
- NOAA National Weather Service API (api.weather.gov) vs Open-Meteo
Machine-readable
- This page as Markdown
/compare/google-weather-api-vs-nws-api.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-weather-api.json·/api/v1/tools/nws-api.json - From a terminal
anchor compare google-weather-api nws-api(the CLI) - Over MCP
compare_tools {"a": "google-weather-api", "b": "nws-api"}at/mcp, no key