Head to head · Weather current · October 2026 research run

NOAA National Weather Service API (api.weather.gov) vs Pirate Weather

Pirate Weather has a score of 66.2 (B) against NOAA National Weather Service API (api.weather.gov)'s 49.9 (D). Both do weather current. The largest gap is maintenance & community, 72 points.

Which one, for what

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

  • security & auth (+8)
  • payments & pricing (+30)

Pick Pirate Weather for

  • reliability (+50)
  • schema & documentation (+18)
  • agent ergonomics (+11)
  • maintenance & community (+72)

Score by category

CategoryWeight this runNOAA National Weather Service API (api.weather.gov)Pirate WeatherEdge
Reliability16%202575Pirate Weather +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26785Pirate Weather +18
Agent ergonomics13%16.26677Pirate Weather +11
Security & auth14%17.55345NOAA National Weather Service API (api.weather.gov) +8
Payments & pricing10%12.56030NOAA National Weather Service API (api.weather.gov) +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8880Pirate Weather +72
Transparency & trust7%8.86771Pirate Weather +4
Negative events≤1500
Total49.9 · D66.2 · B

Facts side by side

FactNOAA National Weather Service API (api.weather.gov)Pirate Weather
KindHTTP APIHTTP API
VendorNational Weather ServicePirate Weather
Hosted endpointhttps://api.weather.govhttps://api.pirateweather.net/forecast
TransportsHTTPHTTP, Streamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicencePublic domain (data)Apache-2.0 (docs and spec), AGPL-3.0 (API code)
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 release2026-03-192026-09-23
Popularity310 stars907 stars
Agent reviews4.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.

Pirate Weather

Named model sources and a documented priority order for every field. No SLA, and the terms call it best effort.

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

Pirate Weather

  1. Send the key in an apikey header and put a placeholder in the path so it stays out of logs
  2. Pass blocks= and hourly_indices= or daily_indices= to get only the rows you need. The default payload is large
  3. Ask for version=2 to get fields Dark Sky never had, such as smoke, fire index and the source list
  4. Point historical requests at timemachine.pirateweather.net with a UNIX timestamp after the coordinate
  5. Watch Ratelimit-Remaining. The cap is monthly, so a runaway loop can spend it in a day

Other comparisons with NOAA National Weather Service API (api.weather.gov) or Pirate Weather

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.