shipapis
StarSubmit an APISubmit API

CloudConvert vs Geocoder REST API

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

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

CloudConvert vs Geocoder REST API: common questions

Which is more reliable, CloudConvert or Geocoder REST API?

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

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

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

Are CloudConvert and Geocoder REST API free for commercial use?

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