Geocoder REST API vs Hunter
Same instrument, two spec sheets — measured, not claimed.
Geocoder REST API vs Hunter: common questions
Which is more reliable, Geocoder REST API or Hunter?
Both are neck-and-neck — Geocoder REST 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, Geocoder REST API or Hunter?
Hunter has the lower median latency in our checks — Geocoder REST API responds in 739 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 Geocoder REST API and Hunter need an API key?
Both ask you to authenticate — Geocoder REST API uses an API key and Hunter 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 Geocoder REST API and Hunter from the browser?
Neither sends browser-friendly CORS headers reliably, so call Geocoder REST API and Hunter from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are Geocoder REST API and Hunter free for commercial use?
Geocoder REST 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.