Eat This Much Partner API vs fatsecret Platform API

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.

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.

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.

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.

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.