Parkhaus Basel API vs UrlBae

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

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

Parkhaus Basel API vs UrlBae: common questions

Which is more reliable, Parkhaus Basel API or UrlBae?

On our scheduled checks, UrlBae leads on measured uptime — Parkhaus Basel API at —% versus UrlBae 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 Parkhaus Basel API and UrlBae need an API key?

Parkhaus Basel API needs no key, while UrlBae requires a free API key. If you want to start calling without signup, reach for Parkhaus Basel API first.

Can I call Parkhaus Basel API and UrlBae from the browser?

Only Parkhaus Basel API is browser-friendly — it returns CORS headers over HTTPS. UrlBae needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Parkhaus Basel API and UrlBae free for commercial use?

Parkhaus Basel API has unclear commercial terms, and UrlBae 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.