Head to head · Cooking nutrition · October 2026 research run
Eat This Much Partner API vs Nutritionix API
Eat This Much Partner API scores 45.7 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories. Both do cooking nutrition.
Best recipe, nutrition and meal planning APIs for AI agents · All 28 cooking comparisons
Which one, for what
Best for Health, fitness, dietitian and healthcare apps that want generated meal plans and grocery lists under contract.
Ahead on
- Reliability, 23 against 15
- Schema & documentation, 75 against 45
- Agent ergonomics, 62 against 51
- Maintenance & community, 58 against 10
Watch for
No self-serve signup. Partners are onboarded after a contract, the API is in early access and prices are tailored per partner
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public free tier or published price; a limited trial is granted by sales after a form on www.nutritionix.com
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.
Maintenance & community Eat This Much Partner API +48
Eat This Much Partner API 58
Read as a closed service. Changelog entry 4.2.0 dated 15 October 2026 (30). Four dated entries in the 90 days to 3 November, 5 August, 6 August, 16 September and 15 October 2026 (20). A support address in the OpenAPI contact block and the changelog, no community channel (8 of 15). No official SDK; the docs point to Postman (0). No package to judge (0). Total 58.
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.
Schema & documentation Eat This Much Partner API +30
Eat This Much Partner API 75
Public OpenAPI 3.0.3, version 4.2.0, at /g/openapi.yaml with 14 operations and named schemas (25). No llms.txt or Markdown docs; the docs page is the OpenAPI document and a Postman guide (0 of 10). Every operation states its purpose, its credit cost and its concurrency limit, and the week endpoint says when to use render separately; little on when not to use a call (14 of 20). Enums on preset_diet, output, format, generator_focus, num_foods and food_output, but the generate request schemas list no required properties, with the required inputs stated in prose (10 of 15). curl samples on six operations, error responses 400, 401, 404, 429 and 500 with an IssueMap of field messages (12 of 15). The version is in info only, paths carry no version, but the changelog dates each change and labels breaking ones (14 of 15). Total 75.
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 Eat This Much Partner API +11
Eat This Much Partner API 62
food_output simple or expanded, include_groceries on or off, and JSON, HTML or PDF output size responses (20 of 25). Food search has filters and pagination and usage history pages at 100; generation takes exclusions and per-meal settings (16 of 20). IssueMap errors name the field, 429 means a concurrency limit, 404 on food and key ids (14 of 20). No idempotency keys; generation is randomised and charged per call, so a retry costs again (4 of 20). Three required inputs with defaults for the rest, no official SDK (8 of 15). Total 62.
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.
Reliability Eat This Much Partner API +8
Eat This Much Partner API 23
Read with the hosted lines. No status page found on eatthismuch.com, the docs or the partner page, and status.eatthismuch.com does not resolve (0). No readable incident history (5). Concurrency limits published with numbers, 3 week, 10 day and 20 meal generations per API user, but no rate per minute or day (12 of 15). 429 documented on three generate operations without Retry-After or backoff guidance, and no idempotency keys on calls that are charged (6 of 15). No SLA (0). The partner page calls the API early access with a limited number of partners, so not general availability (0). Total 23.
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.
Score by category
| Category | Weight this run | Eat This Much Partner API | Nutritionix API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 23 | 15 | Eat This Much Partner API +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 75 | 45 | Eat This Much Partner API +30 |
| Agent ergonomics | 13%16.2 | 62 | 51 | Eat This Much Partner API +11 |
| Security & auth | 14%17.5 | 48 | 52 | Nutritionix API +4 |
| Payments & pricing | 10%12.5 | 0 | 0 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 58 | 10 | Eat This Much Partner API +48 |
| Transparency & trust | 7%8.8 | 61 | 57 | Eat This Much Partner API +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 45.7/100 | F 33.6/100 |
Facts side by side
| Fact | Eat This Much Partner API | Nutritionix API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Eat This Much, Inc. | Syndigo LLC |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | API key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under a partner contract; the website terms cover the consumer service | none |
| Tools exposed | 0 | 0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-15 | 2024-03-14 |
| Terms last updated | no date given | 2019-01-22 |
| Privacy policy last updated | 2020-12-03 | 2026-03-25 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 192 stars |
Verdicts
Eat This Much Partner API
A public OpenAPI 3.0.3 document with credits and concurrency limits per operation, enum diet presets and a dated changelog describes a meal plan generator an agent can read well. Access needs a partner contract with no self-serve signup, no published price and no status page, and the API is in early access.
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.
Before you call either
Eat This Much Partner API
- Access needs a contract with Eat This Much first; ask the person to contact support@eatthismuch.com before planning calls
- Send the key as X-API-Key. Each generate call needs calories, number of meals and preset_diet; keep macro percentages summing to 100 or use gram ranges, not both
- Stay under 3 concurrent week, 10 day and 20 meal generations per API user, and treat 429 as a concurrency limit to wait out, not a quota
- Request food_output=simple unless expanded nutrition is needed, and set include_groceries=false when the list is not wanted; each call costs credits
- Read the changelog before upgrading, since 3.0.0 moved preferred_food_type into meal_settings and 4.0.0 renamed amount to servings
Nutritionix API
- 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
- Send
x-app-idandx-app-keyas headers and setx-remote-user-idper end user (0 in development), since billing counts active users - Treat a 401 as either a bad key or an exhausted usage limit; the docs give no limit figure, so back off before retrying
- Debounce instant searches by 300 ms and send at least 3 characters, then pass
food_nameto natural/nutrients for common foods andnix_item_idto search/item for branded ones - Cache only a person's own logged results; cached data may not be shown to another user
Questions
Which is better for AI agents, Eat This Much Partner API or Nutritionix API?
Eat This Much Partner API scores 45.7 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories.
Do Eat This Much Partner API and Nutritionix API need an API key?
Both need an API key.
Can an agent call Eat This Much Partner API and Nutritionix API without installing anything?
No hosted endpoint is listed for Eat This Much Partner API. No hosted endpoint is listed for Nutritionix API.
Other comparisons with Eat This Much Partner API or Nutritionix API
Machine-readable
- This page as Markdown
/compare/eat-this-much-vs-nutritionix.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/eat-this-much.json·/api/v1/tools/nutritionix.json - From a terminal
anchor compare eat-this-much nutritionix(the CLI) - Over MCP
compare_tools {"a": "eat-this-much", "b": "nutritionix"}at/mcp, no key