shipapis
StarSubmit an APISubmit API

Geocodify.com vs Smappee API

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

APIGeocodify.comREACHABLE—Smappee APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesno
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

Geocodify.com vs Smappee API: common questions

Which is more reliable, Geocodify.com or Smappee API?

On our scheduled checks, Smappee API leads on measured uptime — Geocodify.com 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 Geocodify.com and Smappee API need an API key?

Both ask you to authenticate — Geocodify.com uses an API key and Smappee 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 Geocodify.com and Smappee API from the browser?

Only Geocodify.com 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 Geocodify.com and Smappee API free for commercial use?

Geocodify.com 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.