Bevwire API vs City Bikes

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublished300 req/window · 296 remaining · resets 837
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs City Bikes: common questions

Which is more reliable, Bevwire API or City Bikes?

On our scheduled checks, City Bikes leads on measured uptime — Bevwire API at —% versus City Bikes at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Bevwire API and City Bikes need an API key?

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

Can I call Bevwire API and City Bikes from the browser?

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

Are Bevwire API and City Bikes free for commercial use?

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