shipapis
StarSubmit an APISubmit API

wttr.in vs Open-Meteo

Same instrument, two spec sheets — measured, not claimed.

APIwttr.inNEW—Open-MeteoHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseUnverifiedCC-BY 4.0
Free tierFree — limits not published<10,000 calls/day, no signup
Rate limitUnpublished (informal per-IP throttling)600/min · 5,000/hour
In directory since2026-07-052026-05-02
operationalpartialdownno data

wttr.in vs Open-Meteo: common questions

Which is more reliable, wttr.in or Open-Meteo?

On our scheduled checks, Open-Meteo leads on measured uptime — wttr.in at —% versus Open-Meteo 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 Open-Meteo need an API key?

Neither needs a paid key — wttr.in is callable with no signup, and Open-Meteo is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call wttr.in and Open-Meteo from the browser?

Yes — both wttr.in and Open-Meteo 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 Open-Meteo free for commercial use?

wttr.in has unclear commercial terms, and Open-Meteo is personal/non-commercial only. 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.