wttr.in vs openSenseMap
Same instrument, two spec sheets — measured, not claimed.
wttr.in vs openSenseMap: common questions
Which is more reliable, wttr.in or openSenseMap?
On our scheduled checks, openSenseMap leads on measured uptime — wttr.in at —% versus openSenseMap at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Do wttr.in and openSenseMap need an API key?
Neither needs a paid key — wttr.in is callable with no signup, and openSenseMap is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call wttr.in and openSenseMap from the browser?
Yes — both wttr.in and openSenseMap send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.
Are wttr.in and openSenseMap free for commercial use?
wttr.in has unclear commercial terms, and openSenseMap 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.