shipapis
StarSubmit an APISubmit API

Hunter vs Keyvalue

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

APIHunterHEALTHY96KeyvalueHEALTHY79
Uptime · 30d
Uptime · 90d100%86.3%
Uptime · 30d100%80.0%
P50 · ms362855
P95 · ms8592051
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hunter vs Keyvalue: common questions

Which is more reliable, Hunter or Keyvalue?

On our scheduled checks, Hunter leads on measured uptime — Hunter at 100% versus Keyvalue at 86.3% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Hunter or Keyvalue?

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

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

Can I call Hunter and Keyvalue from the browser?

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

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