AQICN vs Glax Weather API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms2241004
P95 · ms6652534
AuthapiKeynone
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AQICN vs Glax Weather API: common questions

Which is more reliable, AQICN or Glax Weather API?

Both are neck-and-neck — AQICN and Glax Weather API each measure 100% 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, AQICN or Glax Weather API?

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

Glax Weather API needs no key, while AQICN requires a free API key. If you want to start calling without signup, reach for Glax Weather API first.

Can I call AQICN and Glax Weather API from the browser?

Neither sends browser-friendly CORS headers reliably, so call AQICN and Glax Weather API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are AQICN and Glax Weather API free for commercial use?

AQICN has unclear commercial terms, and Glax Weather API 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.