ClickSend REST API v3 vs Nominatim (OSM)

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyuserAgent
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseUnverifiedODbL (OpenStreetMap)
Free tierFree tier — API key required1 req/sec, identified UA required
Rate limitUnpublished1/sec hard — per application
In directory since2026-07-052026-05-02
operationalpartialdownno data

ClickSend REST API v3 vs Nominatim (OSM): common questions

Which is more reliable, ClickSend REST API v3 or Nominatim (OSM)?

Only Nominatim (OSM) is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do ClickSend REST API v3 and Nominatim (OSM) need an API key?

Nominatim (OSM) needs no key, while ClickSend REST API v3 requires a free API key. If you want to start calling without signup, reach for Nominatim (OSM) first.

Can I call ClickSend REST API v3 and Nominatim (OSM) from the browser?

Yes — both ClickSend REST API v3 and Nominatim (OSM) send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are ClickSend REST API v3 and Nominatim (OSM) free for commercial use?

ClickSend REST API v3 has unclear commercial terms, and Nominatim (OSM) is personal/non-commercial only. 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.