shipapis
StarSubmit an APISubmit API

IP Geolocation API vs REST Countries

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

APIIP Geolocation APINEW—REST CountriesHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedMPL-2.0
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone published
In directory since2026-07-052026-05-02
operationalpartialdownno data

IP Geolocation API vs REST Countries: common questions

Which is more reliable, IP Geolocation API or REST Countries?

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

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

Can I call IP Geolocation API and REST Countries from the browser?

Only REST Countries 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 REST Countries free for commercial use?

IP Geolocation API has unclear commercial terms, and REST Countries allows commercial use on its free tier. 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.