NDBC Buoy Data API vs wttr.in
Same instrument, two spec sheets — measured, not claimed.
NDBC Buoy Data API vs wttr.in: common questions
Which is more reliable, NDBC Buoy Data API or wttr.in?
On our scheduled checks, wttr.in leads on measured uptime — NDBC Buoy Data API at 84.3% versus wttr.in at 95.1% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, NDBC Buoy Data API or wttr.in?
NDBC Buoy Data API has the lower median latency in our checks — NDBC Buoy Data API responds in 575 ms versus wttr.in at 700 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
Do NDBC Buoy Data API and wttr.in need an API key?
Neither needs a paid key — NDBC Buoy Data API is callable with no signup, and wttr.in is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call NDBC Buoy Data API and wttr.in from the browser?
Only wttr.in is browser-friendly — it returns CORS headers over HTTPS. NDBC Buoy Data API needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are NDBC Buoy Data API and wttr.in free for commercial use?
NDBC Buoy Data API has unclear commercial terms, and wttr.in has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.