shipapis
StarSubmit an APISubmit API

Dev.to vs Parkhaus Basel API

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

APIDev.toHEALTHY77Parkhaus Basel APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms3281060
P95 · ms10682982
Authnonenone
CORSyesyes
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

Dev.to vs Parkhaus Basel API: common questions

Which is more reliable, Dev.to or Parkhaus Basel API?

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

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

Neither needs a paid key — Dev.to 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 Dev.to and Parkhaus Basel API from the browser?

Yes — both Dev.to and Parkhaus Basel API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Dev.to and Parkhaus Basel API free for commercial use?

Dev.to 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.