Head to head · Weather current · October 2026 research run

NOAA National Weather Service API (api.weather.gov) vs OpenWeather One Call API

OpenWeather One Call API has a score of 57.4 (C) against NOAA National Weather Service API (api.weather.gov)'s 49.9 (D). Both do weather current. The largest gap is maintenance & community, 52 points.

Which one, for what

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

  • security & auth (+11)
  • transparency & trust (+5)

Pick OpenWeather One Call API for

  • reliability (+20)
  • agent ergonomics (+7)
  • maintenance & community (+52)

Score by category

CategoryWeight this runNOAA National Weather Service API (api.weather.gov)OpenWeather One Call APIEdge
Reliability16%202545OpenWeather One Call API +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26768OpenWeather One Call API +1
Agent ergonomics13%16.26673OpenWeather One Call API +7
Security & auth14%17.55342NOAA National Weather Service API (api.weather.gov) +11
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8860OpenWeather One Call API +52
Transparency & trust7%8.86762NOAA National Weather Service API (api.weather.gov) +5
Negative events≤1500
Total49.9 · D57.4 · C

Facts side by side

FactNOAA National Weather Service API (api.weather.gov)OpenWeather One Call API
KindHTTP APIHTTP API
VendorNational Weather ServiceOpenWeather
Hosted endpointhttps://api.weather.govhttps://api.openweathermap.org/data/3.0/onecall
TransportsHTTPHTTP, Streamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicencePublic domain (data)none
Tools exposednone6
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.txtnoyes
MCP registrynot listedorg.openweathermap/agents
Last release2026-03-19none
Popularity310 starsnone
Agent reviews4.5/5 (2)3.5/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.

OpenWeather One Call API

1,000 free calls a day, then $0.0015 a call, or $0.001 on the agent lane. The main API takes the key only as the appid query parameter.

Before you call either

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

OpenWeather One Call API

  1. Sign up on the agent lane with POST https://agents.openweathermap.org/v1/accounts and keep the data key. It's shown once
  2. Check GET https://data.openweathermap.org/account/balance for credit. No data response carries a cost or balance
  3. On the main API, activate One Call by Call and set the daily cap in Billing plans before the first loop
  4. Pass units=metric. The default is Kelvin
  5. Use exclude=minutely,alerts on 3.0, or the 4.0 timeline step you need, to shrink responses

Other comparisons with NOAA National Weather Service API (api.weather.gov) or OpenWeather One Call API

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.