shipapis
StarSubmit an APISubmit API

Foodish vs Longevity World Cup

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

APIFoodishDYING53Longevity World CupHEALTHY85
Uptime · 30d
Uptime · 90d27.5%99.02%
Uptime · 30d11.7%98.3%
P50 · ms250767
P95 · ms7603677
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)Unverified
Free tierFree — no keyFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs Longevity World Cup: common questions

Which is more reliable, Foodish or Longevity World Cup?

On our scheduled checks, Longevity World Cup leads on measured uptime — Foodish at 27.5% versus Longevity World Cup at 99.02% 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 Longevity World Cup?

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

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

Can I call Foodish and Longevity World Cup from the browser?

Only Longevity World Cup 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 Foodish and Longevity World Cup free for commercial use?

Foodish has unclear commercial terms, and Longevity World Cup 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.