Head to head · Cooking nutrition · October 2026 research run

Nutritionix API vs spoonacular

spoonacular scores 49 (D) on agent readiness against Nutritionix API's 33.6 (F), and leads in 6 of 7 scored categories. Nutritionix API leads on security & auth. Both do cooking nutrition.

Best recipe, nutrition and meal planning APIs for AI agents · All 28 cooking comparisons

Which one, for what

Nutritionix API F

Best for Agents that log meals from free text for a US or UK audience and need branded grocery and restaurant nutrition with UPCs, under a sales contract.

Ahead on

  • Security & auth, 52 against 20

Watch for

No public free tier or published price; a limited trial is granted by sales after a form on www.nutritionix.com

spoonacular D

Best for Agents that need recipe search with diet and nutrient filters, ingredient substitutions and nutrition, and meal plans or shopping lists written to a connected user.

Ahead on

  • Reliability, 58 against 15
  • Schema & documentation, 65 against 45
  • Agent ergonomics, 68 against 51
  • Payments & pricing, 40 against 0
  • Maintenance & community, 22 against 10

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

One all-powerful key per account, documented in the apiKey query parameter and sent that way by the MCP server

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability spoonacular +43

Nutritionix API 15

Read with the hosted lines. The docs name a status page at status.nutritionix.com, but that host's robots.txt disallows our reader, so it is scored as unread (0 of 20) with no incident history (5). No rate limit figure appears anywhere in the docs (0 of 15). No 429, Retry-After or backoff guidance; the error page files 'usage limits exceeded' under 401 (0 of 15). No SLA found (0). The v2 API is generally available (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.

spoonacular 58

Read with the hosted lines. A status page exists at status.spoonacular.com (UptimeRobot), but on 3 November 2026 it rendered 'There was an error while fetching the data' with no components or history, so half credit (10 of 20) and no readable incident record (5). Daily point quotas and requests-per-second limits are published by plan, 60 a minute on Free and 5, 10 and 20 a second on Cook, Culinarian and Chef (15). HTTP 429 and 402 are documented with three quota headers, but there is no Retry-After, backoff guidance or idempotency key for the meal-plan writes (8 of 15). The pricing page states 99 per cent uptime on Cook and Culinarian and 99.9 per cent on Chef, and the FAQ says SLAs are sold above $250 a month (10). The API is generally available (10). 10 + 5 + 15 + 8 + 10 + 10 = 58.

Payments & pricing spoonacular +40

Nutritionix API 0

No x402, MPP or L402 (0 of 40). No price is published on any page read; the pricing page on www.nutritionix.com is closed to our reader and the developer portal routes to sales (0 of 20, unchecked). The developer portal says the public free-access tier has ended and a limited trial is granted by sales (0 of 20). A person files a form and waits for a sales follow-up (0 of 20). Total 0.

spoonacular 40

No x402, MPP or L402 (0 of 40). Plan prices and per-point overage rates ($0.005, $0.004 and $0.002) are public, with the point cost of every endpoint (20). The Free plan gives 50 points a day with no card (20). A person signs up in the console in a browser, and no key API exists (0 of 20). 0 + 20 + 20 + 0 = 40.

Security & auth Nutritionix API +32

Nutritionix API 52

An application id and key pair with no scopes, sent only as headers per the docs, which say not to use the query string; no expiry or rotation documented (18 of 30). The API is read-only, so nothing destructive is reachable, but there is no read-only or per-user credential (12 of 20). Food, brand and menu names come from brands and restaurants through Syndigo, with little free text and no guidance on treating it as untrusted (8 of 15). x-remote-user-id counts active users for billing; no request log or per-call visibility for the operator was found (2 of 15). Syndigo runs a responsible disclosure programme on Bugcrowd without compensation, holds SOC 2 Type II for named products that do not include Nutritionix, and lists the Nutritionix API's sub-processors; no security.txt (12 of 20). 18 + 12 + 8 + 2 + 12 = 52.

spoonacular 20

One key per account with no scopes, expiry or rotation procedure, documented first as the apiKey query parameter and also sent in the query string by the MCP server; the x-api-key header is the alternative. One all-powerful key (10) less 10 for the documented query string (0 of 30). The data endpoints are read-only and a user's meal plan is written only with that user's username and hash, but there is no read-only key mode or confirmation step (10 of 20). Recipe text, instructions and extracted pages come from third-party websites and no guidance on treating them as untrusted was found (5 of 15). The console shows quota use and the headers report it per call, but no request log was found (5 of 15). security.txt returns 404 and no disclosure policy, bug bounty or certification was found (0 of 20). 0 + 10 + 5 + 5 + 0 = 20.

Schema & documentation spoonacular +20

Nutritionix API 45

No OpenAPI or similar document was found (0 of 25). Syndigo's docs portal serves an llms.txt index and a Markdown twin of every Nutritionix page (10). Each endpoint page states its purpose with usage guidance, such as debouncing instant searches and using the right follow-up endpoint for common and branded foods (13 of 20). Parameters are typed with defaults, but the only required column reads 'Required for Authentication', taxonomy_node_id is typed boolean while described as an id, and claims values sit in prose (8 of 15). Request and response examples on each endpoint; six error statuses with one line each and no body format (9 of 15). v2 in the path, no changelog, and the API guide last updated on 14 March 2024 (5 of 15). 0 + 10 + 13 + 8 + 9 + 5 = 45.

spoonacular 65

Public OpenAPI 3.0.0 document (info version 2.0.2, 97 paths, 99 operations) in the vendor's spoonacular-api-clients repository, linked from the SDK page, and the MCP server's six tools carry JSON Schema inputs (25). No llms.txt (404) and no Markdown docs (0 of 10). Each endpoint states its purpose and point cost, with little on when not to use it (12 of 20). Parameters are typed with required flags, number is bounded, but diet, cuisine, intolerance and meal-type values sit in prose lists rather than enums (9 of 15). Request and response examples on every endpoint, 402 and 429 documented in the quota text, but the OpenAPI document lists only 200, 401, 403 and 404 and no error body shape (9 of 15). No version in the path; a dated updates page by month back to February 2020 records field removals with notice, the last in December 2022 for 30 June 2023 (10 of 15). 25 + 0 + 12 + 9 + 9 + 10 = 65.

Agent ergonomics spoonacular +17

Nutritionix API 51

Instant returns at most 20 common and 20 branded items and premium detailed_nutrients picks up to three nutrients, but natural nutrients returns every food with a full nutrient array and there is no general field selection (12 of 25). No pagination; filters by branded, common, brand id, brand type and region (10 of 20). Six statuses with a line each, no codes in the body, and limit errors folded into 401 (7 of 20). Every endpoint is a read and safe to repeat (14 of 20). One required parameter per endpoint and sensible defaults, but no official SDK on the developer page beyond a label widget, and the organisation's Python library was last pushed in 2022 (8 of 15). 12 + 10 + 7 + 14 + 8 = 51.

spoonacular 68

number caps results on every search (1 to 100), addRecipeInformation, fillIngredients and includeNutrition switch sections on, and the MCP server lists six compact tools, but there is no field selection and full recipe objects are large (15 of 25). Offset and number pagination with filters by cuisine, diet, intolerances, nutrient ranges, equipment, time and sort keys (18 of 20). 402 and 429 are documented with quota headers, other errors are not, and no error body is shown (10 of 20). Reads are GET and safe to repeat, writes to meal plans and custom foods have no idempotency key, and the MCP tools carry no annotations (10 of 20). No required parameter on complexSearch and generated SDKs in 24 languages (15 of 15). 15 + 18 + 10 + 10 + 15 = 68.

Maintenance & community spoonacular +12

Nutritionix API 10

Read as a closed service. The newest dated first-hand change to the API's docs is the guide's update of 14 March 2024, more than 180 days before 3 November 2026; Syndigo's sub-processor list of 13 April 2026 and the vue-nutrition-label push of February 2026 are not API changes (0 of 30). No three dated changes in 90 days (0 of 20). Support through Syndigo's form and support@nutritionix.com for caching, no public changelog or community channel (5 of 15). No current official SDK; library-python last pushed December 2022, the label widget June 2024 (3 of 15). The organisation's packages show no CI or recent releases (2 of 10). 0 + 0 + 5 + 3 + 2 = 10.

spoonacular 22

Read as a closed service. The newest dated change on the updates page is February 2026 (Nutrition by Photo, recipe extraction from video), more than 180 days before 3 November 2026, and the SDK repository's last push is 2 December 2025 (0 of 30). No dated changes in the last 90 days (0 of 20). Updates page, Discord, contact form and paid support from $99 a month; three open issues on the clients repository could not be read (8 of 15). Generated SDKs in 24 languages, last pushed December 2025, and an npm MCP server, but no vendor entry in the official MCP registry, which lists only third-party spoonacular servers (10 of 15). spoonacular-mcp has one release (1.0.0, 4 August 2025), a test script and no CI (4 of 10). 0 + 0 + 8 + 10 + 4 = 22.

Score by category

CategoryWeight this runNutritionix APIspoonacularEdge
Reliability16%201558spoonacular +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24565spoonacular +20
Agent ergonomics13%16.25168spoonacular +17
Security & auth14%17.55220Nutritionix API +32
Payments & pricing10%12.5040spoonacular +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81022spoonacular +12
Transparency & trust7%8.85761spoonacular +4
Negative events≤1500
TotalF 33.6/100D 49/100

Facts side by side

FactNutritionix APIspoonacular
KindHTTP APIHTTP API
VendorSyndigo LLCskycraft GmbH
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthAPI keyAPI key
PricingPaidFreemium
x402nono
Tools exposed06
Read-only variant documentednono
llms.txtyesno
Last release2024-03-142026-02-01
Terms last updated2019-01-222026-04-16
Privacy policy last updated2026-03-25no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity192 stars6 stars

Verdicts

Nutritionix API

Free-text food logging and a branded-food and restaurant database behind four header-authenticated endpoints, documented in Markdown with an llms.txt index and backed by Syndigo's sub-processor list and disclosure programme. There is no public price or free tier since the open trial ended, no documented rate limit or 429, and the status, terms and pricing pages are closed to our reader.

spoonacular

A broad recipe, ingredient, product and meal-plan API with a public OpenAPI document, 24 generated SDKs and a free 50-point day with no card. One key per account travels in the query string by default, the status page showed no data to our reader, and the terms allow caching for an hour at most.

Before you call either

Nutritionix API

  1. Do not plan on self-serve access; a person must request a trial through Syndigo's sales form, so ask for an existing app id and key before starting
  2. Send x-app-id and x-app-key as headers and set x-remote-user-id per end user (0 in development), since billing counts active users
  3. Treat a 401 as either a bad key or an exhausted usage limit; the docs give no limit figure, so back off before retrying
  4. Debounce instant searches by 300 ms and send at least 3 characters, then pass food_name to natural/nutrients for common foods and nix_item_id to search/item for branded ones
  5. Cache only a person's own logged results; cached data may not be shown to another user

spoonacular

  1. Send the key as the x-api-key header rather than apiKey= in the URL, and keep number small, since every result adds 0.01 points to the call's cost
  2. Read X-API-Quota-Left on each response; a 402 means the day's points are gone until midnight UTC and a 429 means the plan's requests-per-second limit, with no Retry-After to wait on
  3. Use /recipes/complexSearch with addRecipeInformation=true for one call instead of a search followed by one information call per recipe
  4. Do not store ingredients, instructions or nutrition between sessions; the terms allow only recipe ids, titles and image urls to be kept
  5. Show the original recipe source and a link to it with every recipe, as the terms require

Questions

Which is better for AI agents, Nutritionix API or spoonacular?

spoonacular scores 49 (D) on agent readiness against Nutritionix API's 33.6 (F), and leads in 6 of 7 scored categories. Nutritionix API leads on security & auth.

Do Nutritionix API and spoonacular need an API key?

Both need an API key.

Can an agent call Nutritionix API and spoonacular without installing anything?

No hosted endpoint is listed for Nutritionix API. spoonacular runs on your own machine, with no hosted endpoint listed.

Other comparisons with Nutritionix API or spoonacular

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.