# Edamam vs Nutritionix API (slim)

> Edamam scores 42.2 (E) 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/edamam-vs-nutritionix.md (~4,300 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/edamam-vs-nutritionix.json · canonical https://www.anchorterminal.com/compare/edamam-vs-nutritionix
- 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)

Edamam scores 42.2 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories. Nutritionix API leads on security & auth and transparency & trust. Both do cooking nutrition.

- Edamam: E 42.2, rank #1178 of 1349 · https://www.anchorterminal.com/tools/edamam.min.md
- Nutritionix API: F 33.6, rank #1257 of 1349 · https://www.anchorterminal.com/tools/nutritionix.min.md
- Edamam, good for Agents that need recipe candidates filtered by diet, allergen and nutrient ranges with nutrition on each, or food and barcode nutrition through the MCP tools. Ahead on Reliability, 30 against 15; Schema & documentation, 66 against 45; Agent ergonomics, 71 against 51; Payments & pricing, 25 against 0; Maintenance & community, 33 against 10. Also A hosted endpoint, with nothing to install.
- 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 30; Transparency & trust, 57 against 31.

| Category | Edamam | Nutritionix API |
| --- | --- | --- |
| Reliability (16%) | 30 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 66 | 45 |
| Agent ergonomics (13%) | 71 | 51 |
| Security & auth (14%) | 30 | 52 |
| Payments & pricing (10%) | 25 | 0 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 33 | 10 |
| Transparency & trust (7%) | 31 | 57 |

| Fact (where they differ) | Edamam | Nutritionix API |
| --- | --- | --- |
| Vendor | Edamam | Syndigo LLC |
| Hosted endpoint | `https://mcp.edamam.com/mcp/food` | no (local only) |
| Transports | Streamable HTTP |  |
| Price for cooking nutrition | $29 per month (plan) | not published |
| Tools exposed | 2 | 0 |
| llms.txt | no | yes |
| Last release | none | 2024-03-14 |
| Terms last updated | couldn't be read | 2019-01-22 |
| Privacy policy last updated | couldn't be read | 2026-03-25 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 192 stars |

Why the edge:
- Transparency & trust, Nutritionix API +26: Edamam 31 (Closed service whose API terms of use could not be read (the page is a script shell). The plan pages state the restrictions on caching, attribution and automated requests clearly (8 of 30). The privacy policy could not be read either, so no data-handling statement was scored (0 of 30, unchecked). Retired API versions are marked on their docs pages and the recipe docs announce the end of Shopping List V1 on June 30 with no year (6 of 20). No subprocessors or data locations found (0 of 20). 8 + 0 + 6 + 0 = 14.); Nutritionix API 57 (Closed service whose API terms are shown at signup and on www.nutritionix.com, which could not be read; Syndigo's website terms of 2019 do not cover the API (5 of 30, unchecked). Syndigo's privacy notice, effective 25 March 2026, states deletion within 30 days once purposes end, names EU and UK representatives and a DPO, and relies on standard contractual clauses and the Data Privacy Framework, but does not name Nutritionix and gives no category-level retention periods (15 of 30). No deprecation policy or notices found (0 of 20). Sub-processors for the Nutritionix API are named with locations (Amazon Web Services, Red Hat 3scale, Cloudflare, all in the United States) in a list effective 13 April 2026 (16 of 20). 5 + 15 + 0 + 16 = 36.)
- Payments & pricing, Edamam +25: Edamam 25 (No x402, MPP or L402 (0 of 40). Monthly plan prices and call allowances are public for all three APIs, with per-call prices only for Vision ($0.015) and the Site Parser ($0.06 to $0.01), so plan-priced with some per-unit rates (15 of 20). No free tier; 10-day trials on Recipe Search Basic and Plus, a 30-day trial on Food Database Basic, and the pages do not say whether a card is needed (10 of 20). A person signs up in the developer portal and picks a plan in a browser (0 of 20). 0 + 15 + 10 + 0 = 25.); 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.)
- Maintenance & community, Edamam +23: Edamam 33 (Read as a closed service. No dated change was found on the API pages, which carry no changelog. The Food MCP page pins mcp-remote 0.14.3, a version npm published on 21 September 2026, so that page was written or changed within the last 90 days but not demonstrably within 30 (20 of 30). No three dated changes in 90 days (0 of 20). A support widget and form, email and phone on Core and above, no public changelog or community channel (5 of 15). No official SDK; the hosted MCP server is the vendor's but is absent from the official registry, which lists only third-party edamam servers (8 of 15). No package to assess (0 of 10). 20 + 0 + 5 + 8 + 0 = 33.); 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.)
- Security & auth, Nutritionix API +22: Edamam 30 (One `app_id` and `app_key` pair per application, documented as query parameters first and HTTP Basic second, with no scopes, expiry or rotation found; the MCP server takes the pair as a Bearer token. Plain keys (20) less 10 for the documented query string (10 of 30). The APIs are read-only for an outside caller, but there is no read-only key mode and nothing to confirm (12 of 20). Recipe titles, ingredient lines and source urls come from the public web, and no guidance on treating them as untrusted was found; the MCP page only says to present results as estimates (5 of 15). Active user tracking counts users per app for billing, but no request log was found (3 of 15). security.txt returns 404 on developer.edamam.com and no disclosure policy, bug bounty or certification was found (0 of 20). 10 + 12 + 5 + 3 + 0 = 30.); 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.)
- Schema & documentation, Edamam +21: Edamam 66 (Public OpenAPI 3.0.3 documents for Recipe Search v2 (four operations) and the Food Database, and the Food MCP's two tools take typed arguments (25). No llms.txt (404) and no Markdown docs (0 of 10). Operation and parameter descriptions state purpose, and the by-uri description warns that missing recipes are not flagged, but there is little on when not to use an operation (12 of 20). Enums for type, diet, health, cuisineType, mealType, dishType, imageSize, co2EmissionsClass and 31 field names, required flags, a 1 to 20 bound on uris, and the MCP arguments are required lists and strings (14 of 15). Examples on the docs page, an `Errors` schema of errorCode, message and params, but no example error body and no code list (9 of 15). v2 in the path and retired versions marked, but no changelog and a Shopping List V1 end date with no year (6 of 15). 25 + 0 + 12 + 14 + 9 + 6 = 66.); 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.)
- Agent ergonomics, Edamam +20: Edamam 71 (`field` selects any of 31 response fields, results a call are capped by plan at 100 or 1,000, and the MCP server lists two compact tools (22 of 25). `_links.next` paging with diet, health, cuisine, dish, meal, time, calorie and about 40 nutrient range filters (20 of 20). An error schema with errorCode, message and params, but the codes are not enumerated (10 of 20). Every recipe operation is a read and safe to repeat; the shopping-list POST aggregates quantities and stores nothing; the MCP tools' annotations were not read (12 of 20). `type` and `q` are the only required search parameters, with no official SDK in any language (7 of 15). 22 + 20 + 10 + 12 + 7 = 71.); 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.)