shipapis
StarSubmit an APISubmit API

Hunter vs IPGeolocation

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

APIHunterHEALTHY96IPGeolocationREACHABLE100
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms362259
P95 · ms859994
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — 1000 requests/day
Rate limitUnpublished1000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hunter vs IPGeolocation: common questions

Which is more reliable, Hunter or IPGeolocation?

Both are neck-and-neck — Hunter and IPGeolocation each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Hunter or IPGeolocation?

IPGeolocation has the lower median latency in our checks — Hunter responds in 362 ms versus IPGeolocation at 259 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Hunter and IPGeolocation need an API key?

Both ask you to authenticate — Hunter uses an API key and IPGeolocation uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Hunter and IPGeolocation from the browser?

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

Are Hunter and IPGeolocation free for commercial use?

Hunter has unclear commercial terms, and IPGeolocation 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.