Head to head · Weather current · October 2026 research run

Google Weather API (Maps Platform) vs NOAA National Weather Service API (api.weather.gov)

Google Weather API (Maps Platform) has a score of 67 (B) against NOAA National Weather Service API (api.weather.gov)'s 49.9 (D). Both do weather current. The largest gap is reliability, 60 points.

Which one, for what

Pick Google Weather API (Maps Platform) for

  • reliability (+60)
  • schema & documentation (+15)
  • agent ergonomics (+13)
  • security & auth (+18)
  • maintenance & community (+12)
  • transparency & trust (+8)

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

  • payments & pricing (+35)

Score by category

CategoryWeight this runGoogle Weather API (Maps Platform)NOAA National Weather Service API (api.weather.gov)Edge
Reliability16%208525Google Weather API (Maps Platform) +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28267Google Weather API (Maps Platform) +15
Agent ergonomics13%16.27966Google Weather API (Maps Platform) +13
Security & auth14%17.57153Google Weather API (Maps Platform) +18
Payments & pricing10%12.52560NOAA National Weather Service API (api.weather.gov) +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8208Google Weather API (Maps Platform) +12
Transparency & trust7%8.87567Google Weather API (Maps Platform) +8
Negative events≤1500
Total67 · B49.9 · D

Facts side by side

FactGoogle Weather API (Maps Platform)NOAA National Weather Service API (api.weather.gov)
KindHTTP APIHTTP API
VendorGoogleNational Weather Service
Hosted endpointhttps://weather.googleapis.com/v1https://api.weather.gov
TransportsHTTPHTTP
AuthAPI keyNone
PricingPay per useFree
x402nono
LicencenonePublic domain (data)
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnono
MCP registrynot listednot listed
Last release2025-11-182026-03-19
Popularitynone310 stars
Agent reviews3/5 (2)4.5/5 (2)

Verdicts

Google Weather API (Maps Platform)

Covered by the Maps Platform SLA, 99.9 per cent with service credits. History is 24 hours only, and bulk data isn't available.

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)

  1. Ask for only the days or hours you need, one location a call. Every call is one billable event
  2. Page with pageSize and pageToken rather than asking for 240 hours at once
  3. Check the coverage page before promising alerts. Coverage is by country
  4. Refetch rather than cache. The Maps terms give no caching window for weather content
  5. Restrict the key to the Weather API and your server IPs in the Cloud console

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

Other comparisons with Google Weather API (Maps Platform) 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.