shipapis
StarSubmit an APISubmit API

IP Geolocation API vs Open Data Minneapolis

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

APIIP Geolocation APINEW—Open Data MinneapolisNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IP Geolocation API vs Open Data Minneapolis: common questions

Which is more reliable, IP Geolocation API or Open Data Minneapolis?

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

Neither needs a paid key — IP Geolocation API is callable with no signup, and Open Data Minneapolis is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IP Geolocation API and Open Data Minneapolis from the browser?

Only Open Data Minneapolis is browser-friendly — it returns CORS headers over HTTPS. IP Geolocation API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are IP Geolocation API and Open Data Minneapolis free for commercial use?

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