Best Nutrition API in 2026

The best nutrition API in 2026 is the one whose price unit matches the feature you will actually call. Five products cover almost every brief we see. Prices below were read from each vendor’s site on 1 October 2026. Use their page, and ours, when you sign.

Food logging and barcodes

This is a search index with a stable id, a barcode endpoint, and macros per 100 grams so your code can scale a portion. Calorie API is that API. The live plans:

• Free, $0, 1,000 calls a month, no card, non-commercial
• Basic, $15, 20,000 calls, non-commercial
• Core, $50, 150,000 calls, non-commercial
• Plus, $150, 1 million calls, commercial production, cache up to 30 days under the commercial license
• Enterprise, quoted, including image-to-calorie

Commercial means the app charges, runs ads, or otherwise makes money. The cheaper paid plans do not cover it. You send X-API-Usage-Type: commercial on Plus and above. Auth is one header, X-API-Key. There is no natural-language meal parser. If that sentence is the product, skip to Nutritionix.

Catalog marketing on our site says 4M+ foods, with UPC/EAN and an Open Food Facts fallback when we miss. Displaying the data requires attribution unless your Plus or Enterprise agreement waives it.

Restaurant meals and sentences

Nutritionix is the tracking API: natural language, instant search, a branded grocery set they describe as over a million barcodes, and about 203,000 restaurant foods. The public free tier is closed. The business trial is 2 monthly active users. Starter is $499 a month for up to 200 MAU, MVP is $999 for up to 1,000, Unicorn starts at $1,850, and the plans are billed annually. Attribution is required until Unicorn.

That is the best API when users describe a meal in words and you do not want to own the parser. It is a bad API when you are a solo developer who needed a key this afternoon. The switch criteria are in the Nutritionix alternative.

A recipe in, a label out

Edamam’s food database starts at $14 a month for 100,000 calls, which is a lot of search for the money, with attribution and a narrow cache. Their nutrition analysis product is the one that feels like magic and bills like a library: $29 a month to start, and each new recipe you analyze stays on the monthly license afterward. Analysis Basic is not a commercial plan. If you read one paragraph before you integrate Edamam, read that license example on the Edamam pricing post.

Buy this when recipe NLP and diet labels are the feature. Do not buy it as a cheaper Calorie API and then paste recipes in a loop.

Recipe content

Spoonacular is not a thin nutrition lookup. It is recipes, images, instructions, and meal planning, metered in points. Free is 50 points a day, then HTTP 402. Cook is $29 for 1,500 points a day, then half a cent a point. A point is usually one request plus a fraction per result, so 50 points is not 50 calls. Cache lasts an hour, and leaving the platform means deleting what you stored.

It is the best API when the screen is a recipe. It is the wrong meter for a barcode logger. The arithmetic is on Spoonacular API pricing.

The free government API

USDA FoodData Central is the right nutrition API when the foods are generic US reference items and you can build autocomplete, barcode UX, and support yourself. The key is free. There is no SLA. It is a poor best-nutrition-API answer for a consumer app full of branded granola bars, and it is the correct answer for a research tool. We wrote the production gaps up separately in the USDA guide linked above, and we will not pretend a paid API replaces the reference standard.

How to pick this week

Write down the request you cannot ship without. One request.

• A barcode or a search box: price Plus against a week of real call volume. Start on the free 1,000 if the app is not commercial yet.
• A sentence or a chain-restaurant menu: get a Nutritionix trial for 2 users, or budget Starter for the year.
• A pasted recipe: ask Edamam whether those recipes accumulate, then decide if you would rather aggregate per-100g ingredients yourself.
• A page of cooking instructions: Spoonacular, and model points from X-API-Quota-Request on day one, not from the marketing number.

The comparison index for the feature matrices is /compare. This page will not stay the best nutrition API article if those prices move. The dated posts linked above are where a single vendor’s number should be updated, so this one can stay a decision and not a second copy of every table.