Longevity World Cup vs Open Food Facts

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

Uptime · 30d
Uptime · 90d99.02%39.2%
Uptime · 30d98.3%33.3%
P50 · ms7671556
P95 · ms36772836
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Longevity World Cup vs Open Food Facts: common questions

Which is more reliable, Longevity World Cup or Open Food Facts?

On our scheduled checks, Longevity World Cup leads on measured uptime — Longevity World Cup at 99.02% versus Open Food Facts at 39.2% 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, Longevity World Cup or Open Food Facts?

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

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

Can I call Longevity World Cup and Open Food Facts from the browser?

Only Longevity World Cup is browser-friendly — it returns CORS headers over HTTPS. Open Food Facts needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Longevity World Cup and Open Food Facts free for commercial use?

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