# Eat This Much Partner API vs fatsecret Platform API > Eat This Much Partner scores 45.7 (E) to fatsecret Platform's 42 (E) for cooking nutrition. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret - Markdown: https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.md (~3,950 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-04 Eat This Much Partner API scores 45.7 (E) on agent readiness against fatsecret Platform API's 42 (E), and leads in 3 of 7 scored categories. fatsecret Platform API leads on reliability and payments & pricing. Both do cooking nutrition. - Eat This Much Partner API: grade E, 45.7/100, rank #1114 of 1349. Markdown https://www.anchorterminal.com/tools/eat-this-much.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-this-much.json - fatsecret Platform API: grade E, 42/100, rank #1185 of 1349. Markdown https://www.anchorterminal.com/tools/fatsecret.md · JSON https://www.anchorterminal.com/api/v1/tools/fatsecret.json - Best recipe, nutrition and meal planning APIs for AI agents: https://www.anchorterminal.com/best/cooking/index.md - All 28 cooking comparisons: https://www.anchorterminal.com/compare/cooking/index.md ## Which one, for what ### Eat This Much Partner API (E) Good for: Health, fitness, dietitian and healthcare apps that want generated meal plans and grocery lists under contract. Ahead on: - Schema & documentation, 75 against 52 - Maintenance & community, 58 against 13 - Transparency & trust, 61 against 34 Watch for: No self-serve signup. Partners are onboarded after a contract, the API is in early access and prices are tailored per partner ### fatsecret Platform API (E) Good for: Agents logging foods and reading serving-level nutrients, allergens and barcodes for a person, with diaries written back; strongest outside the US on Premier with 62 regional datasets. Ahead on: - Reliability, 35 against 23 - Payments & pricing, 25 against 0 Also in its favour: - Free to start without a card Watch for: Natural language, image recognition, autocomplete, barcode scanning and foods.search v5 are Premier Exclusive, priced on request by market ## Why the edge ### Maintenance & community: Eat This Much Partner API +45 - 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. - fatsecret Platform API (13): Read as a closed service. No dated API change could be read first-hand. The blog that carries the 'What's new' notes sits behind a robots.txt that answered 403, the method pages are undated, and the official Postman repository's last push is 1 July 2025, more than 180 days before 3 November 2026 (0 of 30). No three dated changes in 90 days established (0 of 20). A developer forum on Google Groups, a contact form, and email, phone, Slack and video support on Premier, with no public changelog on the platform site (8 of 15). No official SDK; an official Postman collection (5 of 15). No package to assess (0 of 10). 0 + 0 + 8 + 5 + 0 = 13. ### Transparency & trust: Eat This Much Partner API +27 - Eat This Much Partner API (61): Closed service. The website terms name Eat This Much, Inc. under California law but carry no date and do not cover the API, whose terms are the partner contract; the partner page states the standard retention terms (12 of 30). The privacy policy of 3 December 2020 names its processors and US and Canada databases, the partner page gives retention for partner data and a 7-day cache for nutrition data, and the terms say uploaded recipes cannot be removed (15 of 30). Breaking changes are dated and labelled in the changelog but no notice period or policy is stated (8 of 20). Processors named (Google, Amplitude, Meta, Stripe, Bugsnag, Groove, SendGrid, Cloudflare) and data locations stated (12 of 20). Total 47. - fatsecret Platform API (34): Closed service with terms that are clear on caching, attribution, rate limits and termination, but undated, naming the provider only as Fatsecret.com, and changeable with or without notice (12 of 30). The privacy policy on foods.fatsecret.com could not be read, because that host's robots.txt disallows our reader, so no data-handling statement was scored; the terms require content to be removed within 24 hours (0 of 30, unchecked). Older method versions stay documented alongside v5 and foods.search v4 is still served, but the terms allow any aspect of the API to be changed or discontinued at any time with no notice period (6 of 20). No subprocessors or data locations found (0 of 20). 12 + 0 + 6 + 0 = 18. ### Payments & pricing: fatsecret Platform API +25 - Eat This Much Partner API (0): Read with the hosted rule. No x402, MPP or L402 (0). Pricing is tailored to each partner and not published; the usage schema's price per credit of 0.01 is an example value (0). No free tier or trial for the API; evaluation is by contacting the company (0). Access starts with a contract signed by a person (0). Total 0. - fatsecret Platform API (25): No x402, MPP or L402 (0 of 40). Basic is free and Premier is priced on request by market, with add-ons billed in tiers of 25,000 inputs and no price given, so the paid prices are contact sales (5 of 20). Basic is free on self sign-up with no card, and the platform page says Premier needs no upfront payment or card (20 of 20). A person registers in a browser and Premier goes through sales; no key API was found (0 of 20). 0 + 5 + 20 + 0 = 25. ### Schema & documentation: Eat This Much Partner API +23 - 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. - fatsecret Platform API (52): No OpenAPI or similar document was found; the official Postman collection is the only machine-readable contract (8 of 25). No llms.txt (a redirect) and no Markdown docs (0 of 10). Each method page states purpose, parameters, response fields and Premier status, with little on when not to use a method (12 of 20). Parameters are typed with defaults and allowed values, `max_results` is capped at 50, but the field tables mistype allergen names as Long and leave food_images out of the food-level fields (11 of 15). Example responses in XML and JSON on each method, a central error code list with the body shape, and per-method error codes (13 of 15). Methods carry versions (v1 to v5) and older versions stay documented, but no changelog is on the platform site and the blog's 'What's new' could not be read (8 of 15). 8 + 0 + 12 + 11 + 13 + 8 = 52. ### Reliability: fatsecret Platform API +12 - 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. - fatsecret Platform API (35): Read with the hosted lines. No status page was found on the platform site, the guides, the editions page or the about page (0), so there is no incident history to read (5). The limit is published with a number, 5,000 calls a day on Basic in the terms and on the editions page, and Premier is unlimited (15). Limits surface as error codes 11 and 12 in the body; no HTTP 429, Retry-After or backoff guidance was found, and diary writes have no idempotency key (5 of 15). Premier carries a month-by-month SLA with service credits, named on the editions page without figures, and every edition claims more than 99.9 per cent uptime (5 of 10). The API is generally available, with versioned methods (10). 0 + 5 + 15 + 5 + 5 + 10 = 35. ## Score by category | Category | Weight | Eat This Much Partner API | fatsecret Platform API | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 23 | 35 | fatsecret Platform API +12 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 75 | 52 | Eat This Much Partner API +23 | | Agent ergonomics | 13% (16.2 this run) | 62 | 64 | fatsecret Platform API +2 | | Security & auth | 14% (17.5 this run) | 48 | 51 | fatsecret Platform API +3 | | Payments & pricing | 10% (12.5 this run) | 0 | 25 | fatsecret Platform API +25 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 58 | 13 | Eat This Much Partner API +45 | | Transparency & trust | 7% (8.8 this run) | 61 | 34 | Eat This Much Partner API +27 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **45.7 · E** | **42 · E** | | ## Facts side by side | Fact | Eat This Much Partner API | fatsecret Platform API | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Eat This Much, Inc. | fatsecret | | Hosted endpoint | no (local only) | no (local only) | | Transports | | | | Auth | API key | OAuth | | Pricing | Paid | Freemium | | 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 | no | | Last release | 2026-10-15 | none | | Terms last updated | no date given | no date given | | Privacy policy last updated | 2020-12-03 | no date given | | Customer content may train models | not found in the text | not found in the text | | Terms restrict automated access | yes | yes | | Terms restrict benchmarking | yes | not found in the text | | Terms or service can change without notice | yes | yes | | Arbitration or class-action waiver | yes | not found in the text | | Popularity | none | 25 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. **fatsecret Platform API.** OAuth 2.0 client credentials with feature scopes, IP-restricted tokens, a free 5,000-call day with no card, and per-serving nutrients with allergen flags on branded and generic foods. The newest search and image methods need the sales-priced Premier edition, there is no status page, OpenAPI file or official SDK, and the privacy policy and blog could not be read. ## Before you call either ### Eat This Much Partner API 1. Access needs a contract with Eat This Much first; ask the person to contact support@eatthismuch.com before planning calls 2. 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 3. 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 4. Request food_output=simple unless expanded nutrition is needed, and set include_groceries=false when the list is not wanted; each call costs credits 5. Read the changelog before upgrading, since 3.0.0 moved preferred_food_type into meal_settings and 4.0.0 renamed amount to servings ### fatsecret Platform API 1. Request a token with `grant_type=client_credentials` and only the scopes the task needs; a token request from an IP not registered on the key fails, so run from a fixed address 2. Use `foods.search` v1 on Basic, since v5, autocomplete, barcode and image methods answer with a scope error without Premier 3. Pass `format=json` and keep `max_results` at or below 50 with a zero-based `page_number`; treat error code 11 or 12 in the body as the rate limit, since no 429 is documented 4. Store only food_id and serving_id between sessions and re-request other values within 24 hours, as the terms require 5. Use a delegated profile token for diary writes and keep the profile's oauth_token and oauth_secret, since fatsecret does not return them again ## Questions ### Which is better for AI agents, Eat This Much Partner API or fatsecret Platform API? Eat This Much Partner API scores 45.7 (E) on agent readiness against fatsecret Platform API's 42 (E), and leads in 3 of 7 scored categories. fatsecret Platform API leads on reliability and payments & pricing. ### Do Eat This Much Partner API and fatsecret Platform API need an API key? Eat This Much Partner API needs an API key. fatsecret Platform API uses an OAuth sign-in. ### Can an agent call Eat This Much Partner API and fatsecret Platform API without installing anything? No hosted endpoint is listed for Eat This Much Partner API. No hosted endpoint is listed for fatsecret Platform API. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "eat-this-much", "b": "fatsecret"}`. From a terminal: `anchor compare eat-this-much fatsecret` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-this-much.json and https://www.anchorterminal.com/api/v1/tools/fatsecret.json ## Other comparisons with Eat This Much Partner API or fatsecret Platform API - [Eat This Much Partner API vs Nutritionix API](https://www.anchorterminal.com/compare/eat-this-much-vs-nutritionix.md) - [fatsecret Platform API vs LogMeal](https://www.anchorterminal.com/compare/fatsecret-vs-logmeal.md) - [fatsecret Platform API vs Nutritionix API](https://www.anchorterminal.com/compare/fatsecret-vs-nutritionix.md) - [fatsecret Platform API vs spoonacular](https://www.anchorterminal.com/compare/fatsecret-vs-spoonacular.md) - [Eat This Much Partner API vs Edamam](https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.md) - [Edamam vs fatsecret Platform API](https://www.anchorterminal.com/compare/edamam-vs-fatsecret.md) - [Eat This Much Partner API vs LogMeal](https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.md) - [Eat This Much Partner API vs spoonacular](https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp