shipapis
StarSubmit an APISubmit API

Packagist vs Parkhaus Basel API

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

APIPackagistHEALTHY99Parkhaus Basel APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms611060
P95 · ms9392982
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Packagist vs Parkhaus Basel API: common questions

Which is more reliable, Packagist or Parkhaus Basel API?

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

Packagist has the lower median latency in our checks — Packagist responds in 61 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 Packagist and Parkhaus Basel API need an API key?

Neither needs a paid key — Packagist is callable with no signup, and Parkhaus Basel API is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

Are Packagist and Parkhaus Basel API free for commercial use?

Packagist 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.