City Bikes vs Foodish

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

Uptime · 30d
Uptime · 90d100%27.5%
Uptime · 30d100%11.7%
P50 · ms665250
P95 · ms1580760
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source)
Free tierFree — no key requiredFree — no key
Rate limit300 req/window · 296 remaining · resets 837Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City Bikes vs Foodish: common questions

Which is more reliable, City Bikes or Foodish?

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

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

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

Can I call City Bikes and Foodish from the browser?

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

Are City Bikes and Foodish free for commercial use?

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