Passantenfrequenzen Zürich vs Truth or Dare API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms569546
P95 · ms1228973
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished5 req/window · 4 remaining · resets 5
In directory since2026-07-052026-07-05
operationalpartialdownno data

Passantenfrequenzen Zürich vs Truth or Dare API: common questions

Which is more reliable, Passantenfrequenzen Zürich or Truth or Dare API?

Both are neck-and-neck — Passantenfrequenzen Zürich and Truth or Dare API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Passantenfrequenzen Zürich or Truth or Dare API?

Truth or Dare API has the lower median latency in our checks — Passantenfrequenzen Zürich responds in 569 ms versus Truth or Dare API at 546 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Passantenfrequenzen Zürich and Truth or Dare API need an API key?

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

Can I call Passantenfrequenzen Zürich and Truth or Dare API from the browser?

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

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