shipapis
StarSubmit an APISubmit API

AQICN vs wttr.in

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

APIAQICNON SCHEDULE—wttr.inNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished (informal per-IP throttling)
In directory since2026-07-052026-07-05
operationalpartialdownno data

AQICN vs wttr.in: common questions

Which is more reliable, AQICN or wttr.in?

Only wttr.in is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do AQICN and wttr.in need an API key?

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

Can I call AQICN and wttr.in from the browser?

Only wttr.in 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 wttr.in free for commercial use?

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