shipapis
StarSubmit an APISubmit API

Nationalize.io vs Passantenfrequenzen Zürich

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

APINationalize.ioNEW—Passantenfrequenzen ZürichNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free keyFree — limits not published
Rate limitKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headersUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nationalize.io vs Passantenfrequenzen Zürich: common questions

Which is more reliable, Nationalize.io or Passantenfrequenzen Zürich?

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

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

Can I call Nationalize.io and Passantenfrequenzen Zürich from the browser?

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

Nationalize.io 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.