shipapis
StarSubmit an APISubmit API

City Bikes vs Healthcare.gov

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

APICity BikesHEALTHY91Healthcare.govHEALTHY92
Uptime · 30d
Uptime · 90d100%96.1%
Uptime · 30d100%93.3%
P50 · ms665420
P95 · ms15801696
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedU.S. Government content (CMS)
Free tierFree — no key requiredFree — no key required
Rate limit300 req/window · 296 remaining · resets 837Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City Bikes vs Healthcare.gov: common questions

Which is more reliable, City Bikes or Healthcare.gov?

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

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

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

Can I call City Bikes and Healthcare.gov from the browser?

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

Are City Bikes and Healthcare.gov free for commercial use?

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