
Build your perfectly disciplined all-green history on Github.

spoonacular
spoonacular API
Chomp Food & Nutrition Database
DietlyAPI
Foodi Food AI API
Nutrition data for 3.7M foods and 298K brands across 230 countries, with barcodes and images
Website, pricing, platforms and company facts side by side.
|
|
|
|
|---|---|---|
| Website | f6s.com | noms.sh |
| Pricing | — | |
| Platforms | — | |
| Listed in |
In their own words, as submitted to SaaSHub.


No description of CommitCat yet.
Noms is a REST API for nutrition data. One catalog covers 3.7M foods and 298K brands across 230 countries, from generic foods like an apple to packaged supermarket products, with 3.4M barcodes and 566K food images. Each food carries up to 177 nutrients per 100 g or 100 ml. Names are normalized,...
What each product offers, as listed by its team.


Possible disadvantages
An editorial look at what each product does well and who it suits.


Overall verdict
Why this product is good
Recommended for
No analysis of Noms.sh yet.
How often each product is chosen within a category, 0–100% relative to the other.


As answered by people managing CommitCat and Noms.sh.
Noms.sh's answer:
Python, PostgreSQL, and Google Cloud.
Noms.sh's answer:
One catalog covers 3.7M foods and 298K brands across 230 countries, from generic foods like an apple to packaged supermarket products, with 3.4M barcodes and 566K food images. Names are normalized, units reconciled and duplicates merged before the response reaches you. Each food carries up to 177 nutrients per 100 g or 100 ml.
Noms.sh's answer:
Coverage outside the US, including Latin America, in one API. Clean data without doing the cleanup yourself. A free tier with 250 requests a day and no card, then plans from $29 a month. JSON responses with cursor pagination and RFC 9457 errors, described by an OpenAPI 3.1 document.
Noms.sh's answer:
Developers building food, fitness, nutrition and grocery apps who need reliable nutrition data and barcode lookup without maintaining their own food database.
Noms.sh's answer:
Food data is scattered across sources that disagree on names, units and duplicates, and every app ends up redoing the same cleanup. Noms does that work once and serves the result through one API.
Share your experience with using CommitCat and Noms.sh. For example, how are they different and which one is better?