openSenseMap vs Open-Meteo

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseOpen data (license set per senseBox; often public domain)CC-BY 4.0
Free tierFree (open-source citizen-science platform)<10,000 calls/day, no signup
Rate limitUnpublished600/min · 5,000/hour
In directory since2026-07-052026-05-02
operationalpartialdownno data

openSenseMap vs Open-Meteo: common questions

Which is more reliable, openSenseMap or Open-Meteo?

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

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

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

openSenseMap 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.