Geocoder REST API vs Gyazo

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 — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocoder REST API vs Gyazo: common questions

Which is more reliable, Geocoder REST API or Gyazo?

On our scheduled checks, Gyazo leads on measured uptime — Geocoder REST API at —% versus Gyazo 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 Geocoder REST API and Gyazo need an API key?

Both ask you to authenticate — Geocoder REST API uses an API key and Gyazo 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 Gyazo from the browser?

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

Geocoder REST API has unclear commercial terms, and Gyazo 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.