shipapis
StarSubmit an APISubmit API

Parkhaus Basel API vs VerifyEd

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

APIParkhaus Basel APIHEALTHY86VerifyEdHEALTHY76
Uptime · 30d
Uptime · 90d100%97.1%
Uptime · 30d100%95.0%
P50 · ms10601933
P95 · ms29823606
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublished100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

Parkhaus Basel API vs VerifyEd: common questions

Which is more reliable, Parkhaus Basel API or VerifyEd?

On our scheduled checks, Parkhaus Basel API leads on measured uptime — Parkhaus Basel API at 100% versus VerifyEd at 97.1% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Parkhaus Basel API or VerifyEd?

Parkhaus Basel API has the lower median latency in our checks — Parkhaus Basel API responds in 1060 ms versus VerifyEd at 1933 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 Parkhaus Basel API and VerifyEd need an API key?

Parkhaus Basel API needs no key, while VerifyEd 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 VerifyEd from the browser?

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

Are Parkhaus Basel API and VerifyEd free for commercial use?

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