shipapis
StarSubmit an APISubmit API

BigDataCloud Geocode vs Smappee API

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

APIBigDataCloud GeocodeNEW—Smappee APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BigDataCloud Geocode vs Smappee API: common questions

Which is more reliable, BigDataCloud Geocode or Smappee API?

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

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

Can I call BigDataCloud Geocode and Smappee API from the browser?

Only BigDataCloud Geocode is browser-friendly — it returns CORS headers over HTTPS. Smappee API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are BigDataCloud Geocode and Smappee API free for commercial use?

BigDataCloud Geocode has unclear commercial terms, and Smappee 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.