shipapis
StarSubmit an APISubmit API

Geocoder REST API vs IPLocate.io

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

APIGeocoder REST APINEW—IPLocate.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished50 req/window · 49 remaining · resets 1783555200
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocoder REST API vs IPLocate.io: common questions

Which is more reliable, Geocoder REST API or IPLocate.io?

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

IPLocate.io needs no key, while Geocoder REST API requires a free API key. If you want to start calling without signup, reach for IPLocate.io first.

Can I call Geocoder REST API and IPLocate.io from the browser?

Only IPLocate.io is browser-friendly — it returns CORS headers over HTTPS. Geocoder REST API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Geocoder REST API and IPLocate.io free for commercial use?

Geocoder REST API has unclear commercial terms, and IPLocate.io 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.