AQICN vs Luchtmeetnet

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms224806
P95 · ms6651926
AuthapiKeynone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — no API key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AQICN vs Luchtmeetnet: common questions

Which is more reliable, AQICN or Luchtmeetnet?

Both are neck-and-neck — AQICN and Luchtmeetnet 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 Luchtmeetnet?

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

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

Can I call AQICN and Luchtmeetnet from the browser?

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

Are AQICN and Luchtmeetnet free for commercial use?

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