Head to head · Weather current · October 2026 research run

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

Visual Crossing Weather API has a score of 60.3 (C) against NOAA National Weather Service API (api.weather.gov)'s 49.9 (D). Both do weather current. The largest gap is maintenance & community, 50 points.

Which one, for what

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

  • security & auth (+13)
  • payments & pricing (+20)
  • transparency & trust (+6)

Pick Visual Crossing Weather API for

  • reliability (+41)
  • schema & documentation (+7)
  • agent ergonomics (+12)
  • maintenance & community (+50)

Score by category

CategoryWeight this runNOAA National Weather Service API (api.weather.gov)Visual Crossing Weather APIEdge
Reliability16%202566Visual Crossing Weather API +41
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26774Visual Crossing Weather API +7
Agent ergonomics13%16.26678Visual Crossing Weather API +12
Security & auth14%17.55340NOAA National Weather Service API (api.weather.gov) +13
Payments & pricing10%12.56040NOAA National Weather Service API (api.weather.gov) +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8858Visual Crossing Weather API +50
Transparency & trust7%8.86761NOAA National Weather Service API (api.weather.gov) +6
Negative events≤1500
Total49.9 · D60.3 · C

Facts side by side

FactNOAA National Weather Service API (api.weather.gov)Visual Crossing Weather API
KindHTTP APIHTTP API
VendorNational Weather ServiceVisual Crossing
Hosted endpointhttps://api.weather.govhttps://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline
TransportsHTTPHTTP, Streamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicencePublic domain (data)none
Tools exposednone1
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 listednot listed
Last release2026-03-19none
Popularity310 starsnone
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.

Visual Crossing Weather API

History from 1970, current conditions and a 15-day forecast from one endpoint. Key only in the query string on the REST API.

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

Visual Crossing Weather API

  1. Always pass include= and elements=. A bare call returns days, hours and current for every element and burns records
  2. Count records before a backfill. Hourly data is 24 records a day, so a year for one place is 8,760
  3. Pass unitGroup=metric. The default is US units
  4. Use the MCP server with X-VC-API-Key rather than pasting the key into a URL
  5. Keep to one request at a time on Free and Professional. A second concurrent job returns 429

Other comparisons with NOAA National Weather Service API (api.weather.gov) or Visual Crossing Weather 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.