shipapis
StarSubmit an APISubmit API

positionstack vs US ZipCode

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

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

positionstack vs US ZipCode: common questions

Which is more reliable, positionstack or US ZipCode?

On our scheduled checks, US ZipCode leads on measured uptime — positionstack at —% versus US ZipCode 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 positionstack and US ZipCode need an API key?

Both ask you to authenticate — positionstack uses an API key and US ZipCode 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 positionstack and US ZipCode from the browser?

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

Are positionstack and US ZipCode free for commercial use?

positionstack has unclear commercial terms, and US ZipCode 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.