DietlyAPI vs Nutritionix
DietlyAPI and Nutritionix both return food and nutrition data over a JSON API, but they are built for different jobs. This is an honest side-by-side to help you pick — including where Nutritionix is the better choice.
At a glance
| DietlyAPI | Nutritionix | |
|---|---|---|
| Monthly price | Free tier; Pro €27/mo; Scale €92/mo | Quote / contact sales (Syndigo) |
| Rate limit | Free ~30 req/min per IP; Pro 500 req/min; Scale 3,000 req/min (per account) | Not publicly specified |
| Included quota | No monthly call cap on paid plans (rate-limited only) | Not publicly specified |
| Underlying data | Open Food Facts + USDA FoodData Central | 600K+ food database (US-focused), branded + restaurant items |
| Best at | High-throughput fuzzy food search, barcode lookup, stable IDs, per-100g nutrients, MCP server | Natural-language food logging, instant search, exercise parsing |
| Trade-offs | No recipe analysis, no natural-language meal parsing, no image recognition | Pricing and limits not published; enterprise/quote sales motion |
How capacity is metered
Nutritionix (owned by Syndigo) publishes neither numeric rate limits nor list pricing, so capacity and cost are established by quote. DietlyAPI publishes its plans, limits and OpenAPI spec openly.
Which should you choose?
Choose Nutritionix
Nutritionix is the stronger pick when natural-language food logging (“two eggs and toast” → nutrients) and a large US restaurant/branded catalog are central to your product.
Choose DietlyAPI
DietlyAPI is the stronger pick when you want transparent, self-serve pricing and high-throughput search/barcode access without contacting sales for a quote.
Neither is a universal winner. If your workload is high-volume food search and barcode lookup with predictable pricing, DietlyAPI fits. If you need Nutritionix’s specialist features above, use Nutritionix.
Get the API