shipapis
StarSubmit an APISubmit API

GeoNet API vs Hunter

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

APIGeoNet APIHEALTHY75HunterHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms2533362
P95 · ms2808859
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoNet API vs Hunter: common questions

Which is more reliable, GeoNet API or Hunter?

Both are neck-and-neck — GeoNet API and Hunter 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, GeoNet API or Hunter?

Hunter has the lower median latency in our checks — GeoNet API responds in 2533 ms versus Hunter at 362 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 GeoNet API and Hunter need an API key?

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

Can I call GeoNet API and Hunter from the browser?

Only GeoNet API 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 GeoNet API and Hunter free for commercial use?

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