Open source and the food API
TempoLife's open packages and its read-only food & nutrition API — honest docs, copy-paste examples, and a clear note on what is live versus planned.
Honest status labels below: “beta” means usable but changeable, “planned” means not shipped yet. Nothing here is a promised, stable production endpoint.
What is here
Food & nutrition API
A read-only HTTP API for searching foods and reading their nutrition per 100 g.
Open nutrition dataset
A downloadable CSV/JSON snapshot of common foods and their per-100 g nutrition.
unit-convert (JS)
The tiny, dependency-free converter behind units.tempolife.app, as an open package.
Status at a glance
| Package | Status | Details |
|---|---|---|
| Food & nutrition API | Beta | Docs |
| Open nutrition dataset | Planned | Docs |
| unit-convert (JS) | Planned | Docs |
A quick taste
The read-only food API answers one job well: given a food name, hand back its nutrition per 100 g as JSON. No keys to sign up for during the beta, no personal data, just a GET request.
Search the food database
curl -s 'https://open.tempolife.app/v1/foods?q=banana'Source: TempoLife open-source packages and the read-only food API. Status labels are current as of the check date. · checked 2026-09-04
Frequently asked questions
Is the food API free?
Yes, within a fair-use limit, and it is read-only with no personal data. It is in beta, so treat exact fields as subject to change and get in touch before any heavy or commercial use.
What licence is the code under?
The released packages are open source under a permissive licence with attribution. Each package page states its status; anything marked planned is not published yet.
Can I use this in production?
The beta API and any planned package are fine for prototypes and side projects. Do not build something mission-critical on a beta endpoint until a versioned, stable release is announced.
Prefer the app to the API?
TempoLife puts the whole food database, calculators and trackers in your pocket, free.