shipapis
StarSubmit an APISubmit API

Passantenfrequenzen Zürich vs 24 Pull Requests

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

APIPassantenfrequenzen ZürichUNMONITORED—24 Pull RequestsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Passantenfrequenzen Zürich vs 24 Pull Requests: common questions

Which is more reliable, Passantenfrequenzen Zürich or 24 Pull Requests?

Only 24 Pull Requests 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 Passantenfrequenzen Zürich and 24 Pull Requests need an API key?

Neither needs a paid key — Passantenfrequenzen Zürich is callable with no signup, and 24 Pull Requests is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Passantenfrequenzen Zürich and 24 Pull Requests from the browser?

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

Are Passantenfrequenzen Zürich and 24 Pull Requests free for commercial use?

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