BuyWhere vs OpenCaged Geocoder (Open Source option)

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnoyes
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

BuyWhere vs OpenCaged Geocoder (Open Source option): common questions

Which is more reliable, BuyWhere or OpenCaged Geocoder (Open Source option)?

On our scheduled checks, OpenCaged Geocoder (Open Source option) leads on measured uptime — BuyWhere at —% versus OpenCaged Geocoder (Open Source option) 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 BuyWhere and OpenCaged Geocoder (Open Source option) need an API key?

Both ask you to authenticate — BuyWhere uses an API key and OpenCaged Geocoder (Open Source option) 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 BuyWhere and OpenCaged Geocoder (Open Source option) from the browser?

Only OpenCaged Geocoder (Open Source option) is browser-friendly — it returns CORS headers over HTTPS. BuyWhere needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are BuyWhere and OpenCaged Geocoder (Open Source option) free for commercial use?

BuyWhere has unclear commercial terms, and OpenCaged Geocoder (Open Source option) 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.