FoodData Central vs LAPIS
Same instrument, two spec sheets — measured, not claimed.
FoodData Central vs LAPIS: common questions
Which is more reliable, FoodData Central or LAPIS?
On our scheduled checks, LAPIS leads on measured uptime — FoodData Central at 98.0% versus LAPIS 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, FoodData Central or LAPIS?
LAPIS has the lower median latency in our checks — FoodData Central responds in 1726 ms versus LAPIS at 524 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 FoodData Central and LAPIS need an API key?
LAPIS needs no key, while FoodData Central requires a free API key. If you want to start calling without signup, reach for LAPIS first.
Can I call FoodData Central and LAPIS from the browser?
Yes — both FoodData Central and LAPIS send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.
Are FoodData Central and LAPIS free for commercial use?
FoodData Central has unclear commercial terms, and LAPIS 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.