shipapis
StarSubmit an APISubmit API

Open-Meteo vs openSenseMap

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

APIOpen-MeteoHEALTHY—openSenseMapNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial usenounclear
Data licenseCC-BY 4.0Open data (license set per senseBox; often public domain)
Free tier<10,000 calls/day, no signupFree (open-source citizen-science platform)
Rate limit600/min · 5,000/hourUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

Open-Meteo vs openSenseMap: common questions

Which is more reliable, Open-Meteo or openSenseMap?

On our scheduled checks, openSenseMap leads on measured uptime — Open-Meteo 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 Open-Meteo and openSenseMap need an API key?

Neither needs a paid key — Open-Meteo 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 Open-Meteo and openSenseMap from the browser?

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

Open-Meteo is personal/non-commercial only, 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.