Parkhaus Basel API vs Scrapfly

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

Uptime · 30d
Uptime · 90d99.44%98.3%
Uptime · 30d100%98.3%
P50 · ms681884
P95 · ms48854809
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 Scrapfly: common questions

Which is more reliable, Parkhaus Basel API or Scrapfly?

On our scheduled checks, Parkhaus Basel API leads on measured uptime — Parkhaus Basel API at 99.44% versus Scrapfly at 98.3% 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 Scrapfly?

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

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

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

Are Parkhaus Basel API and Scrapfly free for commercial use?

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