Coffee vs Foodish

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

Uptime · 30d
Uptime · 90d99.02%27.5%
Uptime · 30d98.3%11.7%
P50 · ms698250
P95 · ms2826760
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source)
Free tierFree — no API keyFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Coffee vs Foodish: common questions

Which is more reliable, Coffee or Foodish?

On our scheduled checks, Coffee leads on measured uptime — Coffee at 99.02% 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, Coffee or Foodish?

Foodish has the lower median latency in our checks — Coffee responds in 698 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 Coffee and Foodish need an API key?

Neither needs a paid key — Coffee 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 Coffee and Foodish from the browser?

Neither sends browser-friendly CORS headers reliably, so call Coffee and Foodish from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Coffee and Foodish free for commercial use?

Coffee 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.