shipapis
StarSubmit an APISubmit API

BigDataCloud Geocode vs ipapi.co

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

APIBigDataCloud GeocodeNEW—ipapi.coNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — quota not published; returns 429 when exceeded
Rate limitUnpublishedUnpublished (429 Quota exceeded)
In directory since2026-07-052026-07-05
operationalpartialdownno data

BigDataCloud Geocode vs ipapi.co: common questions

Which is more reliable, BigDataCloud Geocode or ipapi.co?

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

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

Can I call BigDataCloud Geocode and ipapi.co from the browser?

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

Are BigDataCloud Geocode and ipapi.co free for commercial use?

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