shipapis
StarSubmit an APISubmit API

ApogeoAPI vs Zipcodestack

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

APIApogeoAPINEW—ZipcodestackNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ApogeoAPI vs Zipcodestack: common questions

Which is more reliable, ApogeoAPI or Zipcodestack?

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

Do ApogeoAPI and Zipcodestack need an API key?

Both ask you to authenticate — ApogeoAPI uses an API key and Zipcodestack uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call ApogeoAPI and Zipcodestack from the browser?

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

Are ApogeoAPI and Zipcodestack free for commercial use?

ApogeoAPI has unclear commercial terms, and Zipcodestack 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.