DietlyAPI vs Spoonacular
For the core job of high-volume food search and barcode lookup, DietlyAPI is the stronger default: its pricing and limits are published, paid plans have no monthly call cap, and the API is built around that workload. Spoonacular remains relevant where its specialist features are the deciding requirement.
At a glance
| DietlyAPI | Spoonacular | |
|---|---|---|
| Monthly price | Free tier; Pro €27/mo; Scale €92/mo | Cook US$29/mo (and other tiers) |
| Rate limit | Free ~30 req/min per IP; Pro 500 req/min; Scale 3,000 req/min (per account) | 5 requests/sec |
| Included quota | No monthly call cap on paid plans (rate-limited only) | 1,500 points/day (point-weighted: some calls cost >1 point) |
| Underlying data | Open Food Facts + USDA FoodData Central | Recipe, ingredient and product database |
| Best at | High-throughput fuzzy food search, barcode lookup, stable IDs, per-100g nutrients, MCP server | Recipe search, meal planning, ingredient substitution, wine pairing |
| Trade-offs | No recipe analysis, no natural-language meal parsing, no image recognition | Point-weighted quota; cached data generally must be deleted after 1 hour |
How capacity is metered
Spoonacular bills in points, and some endpoints or larger result sets cost more than one point, so a nominal daily quota does not map one-to-one to calls. DietlyAPI counts plain requests against a per-minute rate with no point weighting.
Which should you choose?
Specialist case for Spoonacular
Spoonacular is a better fit when recipes are central: recipe discovery, meal planning and ingredient workflows are its core, and DietlyAPI does not offer them.
Why DietlyAPI is the stronger default
DietlyAPI is the stronger pick for a food/nutrition catalog: fuzzy product search and barcode lookup at high volume, with simple per-request behaviour instead of a point budget.
For food search and barcode lookup with predictable pricing, DietlyAPI is our recommended choice. Choose Spoonacular when the specialist features above matter more than throughput, transparent self-serve pricing and a simple request-based limit.
Try DietlyAPI free. Public read endpoints work with no key at a shared per-IP limit — enough to prototype in minutes.
Get the API
Top comments (0)