City Bikes vs LAPIS
Same instrument, two spec sheets — measured, not claimed.
City Bikes vs LAPIS: common questions
Which is more reliable, City Bikes or LAPIS?
Both are neck-and-neck — City Bikes and LAPIS 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, City Bikes or LAPIS?
LAPIS has the lower median latency in our checks — City Bikes responds in 665 ms versus LAPIS at 524 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 LAPIS need an API key?
Neither needs a paid key — City Bikes is callable with no signup, and LAPIS is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call City Bikes and LAPIS from the browser?
Yes — both City Bikes and LAPIS 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 City Bikes and LAPIS free for commercial use?
City Bikes has unclear commercial terms, and LAPIS 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.