Open-Meteo vs wttr.in
Same instrument, two spec sheets — measured, not claimed.
Open-Meteo vs wttr.in: common questions
Which is more reliable, Open-Meteo or wttr.in?
Both are neck-and-neck — Open-Meteo and wttr.in each measure 95.1% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, Open-Meteo or wttr.in?
Open-Meteo has the lower median latency in our checks — Open-Meteo responds in 673 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 Open-Meteo and wttr.in need an API key?
Neither needs a paid key — Open-Meteo 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 Open-Meteo and wttr.in from the browser?
Yes — both Open-Meteo and wttr.in 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 Open-Meteo and wttr.in free for commercial use?
Open-Meteo is personal/non-commercial only, 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.