shipapis
StarSubmit an APISubmit API

Cutt.ly vs Passantenfrequenzen Zürich

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

APICutt.lyNEW—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

Cutt.ly vs Passantenfrequenzen Zürich: common questions

Which is more reliable, Cutt.ly or Passantenfrequenzen Zürich?

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

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

Can I call Cutt.ly and Passantenfrequenzen Zürich from the browser?

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

Are Cutt.ly and Passantenfrequenzen Zürich free for commercial use?

Cutt.ly 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.