Foodish vs Fruityvice
Same instrument, two spec sheets — measured, not claimed.
Foodish vs Fruityvice: common questions
Which is more reliable, Foodish or Fruityvice?
On our scheduled checks, Fruityvice leads on measured uptime — Foodish at 27.5% versus Fruityvice at 100% 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, Foodish or Fruityvice?
Foodish has the lower median latency in our checks — Foodish responds in 250 ms versus Fruityvice at 951 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 Foodish and Fruityvice need an API key?
Neither needs a paid key — Foodish is callable with no signup, and Fruityvice is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Foodish and Fruityvice from the browser?
Neither sends browser-friendly CORS headers reliably, so call Foodish and Fruityvice from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are Foodish and Fruityvice free for commercial use?
Foodish has unclear commercial terms, and Fruityvice 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.