City Bikes vs NPPES
Same instrument, two spec sheets — measured, not claimed.
City Bikes vs NPPES: common questions
Which is more reliable, City Bikes or NPPES?
Both are neck-and-neck — City Bikes and NPPES 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 NPPES?
City Bikes has the lower median latency in our checks — City Bikes responds in 665 ms versus NPPES at 910 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 NPPES need an API key?
Neither needs a paid key — City Bikes is callable with no signup, and NPPES is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call City Bikes and NPPES from the browser?
Only City Bikes is browser-friendly — it returns CORS headers over HTTPS. NPPES needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are City Bikes and NPPES free for commercial use?
City Bikes has unclear commercial terms, and NPPES allows commercial use on its free tier. 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.