# Nutritionix API vs spoonacular (slim)

> spoonacular scores 49 (D) to Nutritionix's 33.6 (F) for cooking nutrition. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/nutritionix-vs-spoonacular.md (~4,300 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/nutritionix-vs-spoonacular.json · canonical https://www.anchorterminal.com/compare/nutritionix-vs-spoonacular
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Nutritionix API: F 33.6, rank #1257 of 1349 · https://www.anchorterminal.com/tools/nutritionix.min.md
- spoonacular: D 49, rank #1010 of 1349 · https://www.anchorterminal.com/tools/spoonacular.min.md
- Nutritionix API, good 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.
- spoonacular, good 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 Runs on your own machine; Free to start without a card.

| Category | Nutritionix API | spoonacular |
| --- | --- | --- |
| Reliability (16%) | 15 | 58 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 45 | 65 |
| Agent ergonomics (13%) | 51 | 68 |
| Security & auth (14%) | 52 | 20 |
| Payments & pricing (10%) | 0 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 22 |
| Transparency & trust (7%) | 57 | 61 |

| Fact (where they differ) | Nutritionix API | spoonacular |
| --- | --- | --- |
| Vendor | Syndigo LLC | skycraft GmbH |
| Transports |  | stdio |
| Pricing | Paid | Freemium |
| Tools exposed | 0 | 6 |
| llms.txt | yes | no |
| Last release | 2024-03-14 | 2026-02-01 |
| Terms last updated | 2019-01-22 | 2026-04-16 |
| Privacy policy last updated | 2026-03-25 | no date given |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 192 stars | 6 stars |

Why the edge:
- 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.)