API Ninjas alternatives for recipe and nutrition data
By Chris Artmann ·
Maybe you know the feeling. You built a recipe feature on API Ninjas over a weekend. It works. Then you go to launch and read the pricing page properly. The free plan is "evaluation and demo purposes only". No commercial use. No caching or storing data. Attribution required.
That's not a trick. API Ninjas is clear about it. But it means your side project now needs a paid plan, or a different API. This post is for that moment. We'll look at what you get on API Ninjas, what the alternatives cost, and how to move your code over.
A quick heads-up first: we run one of these alternatives, Tiny Plates. We'll be honest about where API Ninjas is the better pick, and there are a few places where it is. Every price below comes from each provider's own site, checked on November 5, 2026.
Why people go looking
The API Ninjas Recipe API is pretty good. It has over 125,000 recipes. Ingredients come back as a name, a quantity and a unit. Every recipe has nutrition figures, even on the free plan. That's more than most free APIs give you.
The friction is all in the plans. Here's what the free plan gives you:
- 3,000 calls a month, and at most 100 an hour.
- Search by title only, with up to five results per call.
- No commercial use, no storing data, and attribution required.
Searching by ingredient, paging, scaling servings and nutrition filters all need a paid plan. The Developer plan is listed at $59 a month, shown at $39 with the current discount. But read the plan table closely. Developer allows commercial use, but it still says no to caching and storing data. That only opens up on Business, which is listed at $149 and currently shown at $99.
So if your app saves favourites, or keeps recipes around so pages load fast, you're really looking at the Business plan. For a small app, that's a big jump.
API Ninjas also has a separate Nutrition API. It's clever: send it free text like "2 eggs and a slice of toast" and it pulls out each food. Just note that calories and protein are premium-only fields there. If you were hoping for free calorie counts from that endpoint, you'll hit the same wall.
Here's how the main alternatives compare.
| API | Free plan | Commercial use on free | Paid from | Recipes |
|---|---|---|---|---|
| API Ninjas | 3,000 calls/month, 100/hour | No | $59/month ($39 on discount) | 125,000+ |
| Tiny Plates | 50 requests/day, 300/week | Yes | $5/month | 12,000+ |
| Spoonacular | 50 points/day, backlink required | Yes, with the backlink | $29/month | 5,000+, plus products and menus |
| Edamam | None (10-day trial on $9) | No free plan | $9/month | 2 million+ web recipes |
| TheMealDB | Test key for development | Not in an app store without supporter status | $10 once | 793 |
| Tasty (RapidAPI) | Set on the listing | Check the listing | Set on the listing | Tasty's own recipes |
| USDA FoodData Central | Free, 1,000 requests/hour | Yes, public domain | Free | None. Foods and nutrients only |
Now let's go through them one at a time.
Tiny Plates is ours. The free plan gives you 50 requests a day and 300 a week. No credit card, and you can use it in a public app. Personal is $5 a month for 5,000 requests. Business is $20 for 20,000. Extra requests are $1 per 1,000. You're allowed to cache the recipes your users open, so favourites and offline mode just work. Just give the cache a TTL, since recipes get updated at the source. What you can't do is copy the whole index.
We have over 12,000 recipes in English, Spanish and Swedish. That's far fewer than API Ninjas. What we focus on is the recipe as data. Every ingredient has its quantity, unit, name and preparation in separate fields. Each ingredient also gets an id that means the same thing in every language. Every recipe says true or false for each of the EU's 14 regulated allergens, plus the US definitions of wheat and tree nuts. You can leave allergens out of a search with without=milk,peanuts. Search by ingredient, scaling, unit conversion and shopping lists are all on the free plan.
Nutrition is where we're weaker. We return it when the source recipe publishes it, and many do, but not every recipe has it. Best for: apps that need allergens, ingredients as data or a free plan you can ship on. More detail in Tiny Plates vs API Ninjas.
Spoonacular is the big all-rounder. One key covers recipes, grocery products, restaurant menu items, meal plans and shopping lists. The free plan is 50 points a day and needs a backlink to Spoonacular. Paid plans are $29, $79 and $149 a month, and Enterprise starts at $300. Points make a bill harder to predict, because a search costs more the more results you ask for. The terms also limit caching to one hour, with written permission. Best for: apps that need grocery or menu data alongside recipes. We dug into it in Spoonacular alternatives.
Edamam has the biggest index: over 2 million recipes from around the web, with excellent nutrition and diet labels. There's no free plan for Recipe Search. It's $9 a month for 10,000 calls, $99 for 500,000 and $399 for a million. The catch is the cooking steps. On the $9 and $99 plans you get web recipes without instructions, so you link out to the source. Steps only come with Edamam's own recipes on the $399 plan. Attribution is required on every plan. The terms also only allow requests driven by a human end user, so read them carefully if you're building an agent. Best for: search and discovery apps where nutrition matters most.
TheMealDB is the friendly classic. Use the test key 1, no sign-up needed. It has 793 meals. Ingredients are names with measures written as text, and the method is one block of text. The test key is for development and education. To release an app publicly, you become a supporter for a one-off $10. Best for: learning, hackathons and demos.
Tasty on RapidAPI serves BuzzFeed's Tasty recipes. It's a third-party listing by a publisher called Api Dojo, and you subscribe through RapidAPI. We couldn't load the plans when we checked, so look at the listing yourself. Best for: apps that specifically want Tasty's recipes and already use RapidAPI.
USDA FoodData Central isn't a recipe API at all. It's worth knowing about if nutrition is the part you'll miss most. It's free, with 1,000 requests an hour on a data.gov key, and the data is public domain. You get detailed nutrients for generic and branded foods. Pair it with a recipe API that gives you structured ingredients, and you can add up the nutrition yourself. Best for: nutrition you fully control. There's more on where the calorie numbers come from in Nutrition APIs compared.
When to stay on API Ninjas
Let's be fair. API Ninjas is the right call in a few cases. If you need a huge catalogue, 125,000 recipes is hard to beat. If nutrition on every single recipe is the core of your app, they have it. If you already use other API Ninjas endpoints, like weather or exchange rates, one key and one bill is convenient. And if your app is commercial and you're fine with the Business plan, the limits mostly go away.
But if you're a small app that needs a free plan you can actually launch on, or you need allergens, you'll want something else.
So what does moving actually look like? Let's use Tiny Plates as the example, since we know it best. Most API Ninjas calls map to one request. Here's searching by title:
# API Ninjas
curl 'https://api.api-ninjas.com/v3/recipe?title=pasta' \
-H 'X-Api-Key: YOUR_KEY'
# Tiny Plates
curl 'https://api.tinyplates.dev/search?query=pasta' \
-H 'Authorization: Bearer rd_your_api_key'
Two things change. The key moves from an X-Api-Key header to a standard bearer token. And search works on meaning, so query=creamy pasta finds carbonara even if the title doesn't say "creamy".
Searching by ingredient is a paid feature on API Ninjas. On Tiny Plates it's on the free plan:
# API Ninjas (paid plans)
curl 'https://api.api-ninjas.com/v3/recipe?ingredients=chicken,rice' \
-H 'X-Api-Key: YOUR_KEY'
# Tiny Plates
curl 'https://api.tinyplates.dev/pantry?ingredients=chicken,rice,garlic&maxMissing=2' \
-H 'Authorization: Bearer rd_your_api_key'
API Ninjas has a pantry_match field with matched and missing ingredients. Ours has matchedIngredients and missingIngredients, plus assumedIngredients for staples like salt and oil. You can send up to 20 ingredients instead of five. maxMissing=0 means "what can I cook right now".
Scaling works the same way. API Ninjas uses a servings parameter on search. On Tiny Plates you fetch one recipe and pass the servings you want:
curl 'https://api.tinyplates.dev/recipes/RECIPE_ID?servings=4&units=metric' \
-H 'Authorization: Bearer rd_your_api_key'
Every quantity is rewritten for four people and converted to metric. The original field still holds the line the source published.
The response shape is the bigger change. API Ninjas returns a flat array of recipes. We return an object with recipes and pagination. Ingredient objects carry more fields, like ingredientId, preparation and optional. If your code reads ingredient.name, ingredient.quantity and ingredient.unit, the first two still work. The unit lives at ingredient.quantity.unit, next to the value. Budget an hour or two to adjust your types, and you're done.
That's the roundup. If you're still weighing things up, The best recipe APIs in 2026 compares a few more options, and Free food APIs for developers lists every free one we know. And if Tiny Plates sounds like a fit, grab a free key and try the pantry search above. It takes about a minute.