shipapis
StarSubmit an APISubmit API

Hunter vs Parkhaus Basel API

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

APIHunterHEALTHY96Parkhaus Basel APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms3621060
P95 · ms8592982
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hunter vs Parkhaus Basel API: common questions

Which is more reliable, Hunter or Parkhaus Basel API?

Both are neck-and-neck — Hunter and Parkhaus Basel 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, Hunter or Parkhaus Basel API?

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

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

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

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

Are Hunter and Parkhaus Basel API free for commercial use?

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