Gyazo vs Hunter

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Gyazo vs Hunter: common questions

Which is more reliable, Gyazo or Hunter?

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

Do Gyazo and Hunter need an API key?

Both ask you to authenticate — Gyazo 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 Gyazo and Hunter from the browser?

Neither sends browser-friendly CORS headers reliably, so call Gyazo 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 Gyazo and Hunter free for commercial use?

Gyazo 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.