shipapis
StarSubmit an APISubmit API

Hunter vs ReqRes

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

APIHunterHEALTHY96ReqResHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms362256
P95 · ms859582
AuthapiKeynone
CORSnono
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 ReqRes: common questions

Which is more reliable, Hunter or ReqRes?

Both are neck-and-neck — Hunter and ReqRes 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 ReqRes?

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

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

Can I call Hunter and ReqRes from the browser?

Neither sends browser-friendly CORS headers reliably, so call Hunter and ReqRes from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Hunter and ReqRes free for commercial use?

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