shipapis
StarSubmit an APISubmit API

Geocoder REST API vs Passantenfrequenzen Zürich

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

APIGeocoder REST APINEW—Passantenfrequenzen ZürichNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocoder REST API vs Passantenfrequenzen Zürich: common questions

Which is more reliable, Geocoder REST API or Passantenfrequenzen Zürich?

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

Passantenfrequenzen Zürich needs no key, while Geocoder REST API requires a free API key. If you want to start calling without signup, reach for Passantenfrequenzen Zürich first.

Can I call Geocoder REST API and Passantenfrequenzen Zürich from the browser?

Only Passantenfrequenzen Zürich is browser-friendly — it returns CORS headers over HTTPS. Geocoder REST API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Geocoder REST API and Passantenfrequenzen Zürich free for commercial use?

Geocoder REST API has unclear commercial terms, and Passantenfrequenzen Zürich 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.