IP Geolocation API vs OpenCorporates

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IP Geolocation API vs OpenCorporates: common questions

Which is more reliable, IP Geolocation API or OpenCorporates?

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

IP Geolocation API needs no key, while OpenCorporates requires a free API key. If you want to start calling without signup, reach for IP Geolocation API first.

Can I call IP Geolocation API and OpenCorporates from the browser?

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

Are IP Geolocation API and OpenCorporates free for commercial use?

IP Geolocation API has unclear commercial terms, and OpenCorporates 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.