City Bikes vs WhiskyHunter

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

Uptime · 30d
Uptime · 90d100%97.1%
Uptime · 30d100%96.7%
P50 · ms665885
P95 · ms15801775
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — no API key
Rate limit300 req/window · 296 remaining · resets 837Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City Bikes vs WhiskyHunter: common questions

Which is more reliable, City Bikes or WhiskyHunter?

On our scheduled checks, City Bikes leads on measured uptime — City Bikes at 100% versus WhiskyHunter 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, City Bikes or WhiskyHunter?

City Bikes has the lower median latency in our checks — City Bikes responds in 665 ms versus WhiskyHunter at 885 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 City Bikes and WhiskyHunter need an API key?

Neither needs a paid key — City Bikes is callable with no signup, and WhiskyHunter is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call City Bikes and WhiskyHunter from the browser?

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

Are City Bikes and WhiskyHunter free for commercial use?

City Bikes has unclear commercial terms, and WhiskyHunter 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.