Passantenfrequenzen Zürich vs Rendex

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

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

Passantenfrequenzen Zürich vs Rendex: common questions

Which is more reliable, Passantenfrequenzen Zürich or Rendex?

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

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

Can I call Passantenfrequenzen Zürich and Rendex from the browser?

Yes — both Passantenfrequenzen Zürich and Rendex 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 Passantenfrequenzen Zürich and Rendex free for commercial use?

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