Glax Weather API vs openSenseMap

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

Uptime · 30d
Uptime · 90d100%90.2%
Uptime · 30d100%90.0%
P50 · ms1004655
P95 · ms25344139
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen data (license set per senseBox; often public domain)
Free tierFree — limits not publishedFree (open-source citizen-science platform)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Glax Weather API vs openSenseMap: common questions

Which is more reliable, Glax Weather API or openSenseMap?

On our scheduled checks, Glax Weather API leads on measured uptime — Glax Weather API at 100% versus openSenseMap at 90.2% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Glax Weather API or openSenseMap?

openSenseMap has the lower median latency in our checks — Glax Weather API responds in 1004 ms versus openSenseMap at 655 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 Glax Weather API and openSenseMap need an API key?

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

Only openSenseMap is browser-friendly — it returns CORS headers over HTTPS. Glax Weather API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Glax Weather API and openSenseMap free for commercial use?

Glax Weather API 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.