shipapis
StarSubmit an APISubmit API

AQICN vs Open-Meteo

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

APIAQICNREACHABLE100Open-MeteoHEALTHY90
Uptime · 30d
Uptime · 90d100%95.1%
Uptime · 30d100%93.3%
P50 · ms224673
P95 · ms6651193
AuthapiKeynone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearno
Data licenseUnverifiedCC-BY 4.0
Free tierFree tier — API key required<10,000 calls/day, no signup
Rate limitUnpublished600/min · 5,000/hour
In directory since2026-07-052026-05-02
operationalpartialdownno data

AQICN vs Open-Meteo: common questions

Which is more reliable, AQICN or Open-Meteo?

On our scheduled checks, AQICN leads on measured uptime — AQICN at 100% versus Open-Meteo at 95.1% 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, AQICN or Open-Meteo?

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

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

Can I call AQICN and Open-Meteo from the browser?

Only Open-Meteo 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 Open-Meteo free for commercial use?

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