ES·pera API vs Open Food Facts

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

Uptime · 30d
Uptime · 90d0.0%38.8%
Uptime · 30d0.0%39.7%
P50 · ms—1165
P95 · ms—3047
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-09-212026-07-05
operationalpartialdownno data

ES·pera API vs Open Food Facts: common questions

Which is more reliable, ES·pera API or Open Food Facts?

On our scheduled checks, Open Food Facts leads on measured uptime — ES·pera API at 0.0% versus Open Food Facts at 38.8% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do ES·pera API and Open Food Facts need an API key?

Neither needs a paid key — ES·pera API 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 ES·pera API and Open Food Facts from the browser?

Neither sends browser-friendly CORS headers reliably, so call ES·pera API and Open Food Facts from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are ES·pera API and Open Food Facts free for commercial use?

ES·pera API 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.