shipapis
StarSubmit an APISubmit API

ipapi.co vs PostalCodes

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

APIipapi.coNEW—PostalCodesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — quota not published; returns 429 when exceededFree — limits not published
Rate limitUnpublished (429 Quota exceeded)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ipapi.co vs PostalCodes: common questions

Which is more reliable, ipapi.co or PostalCodes?

On our scheduled checks, PostalCodes leads on measured uptime — ipapi.co at —% versus PostalCodes 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 ipapi.co and PostalCodes need an API key?

Neither needs a paid key — ipapi.co is callable with no signup, and PostalCodes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ipapi.co and PostalCodes from the browser?

Neither sends browser-friendly CORS headers reliably, so call ipapi.co and PostalCodes from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are ipapi.co and PostalCodes free for commercial use?

ipapi.co has unclear commercial terms, and PostalCodes 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.