{ "data": { "a": { "slug": "eat-this-much", "name": "Eat This Much Partner API", "vendor": "Eat This Much, Inc.", "vendorUrl": "https://www.eatthismuch.com/partner-api", "kind": "http-api", "category": "cooking", "summary": "The Eat This Much Partner API generates a week, a day or a meal of recipes to calorie and macro targets and diet presets, builds the grocery list and renders the plan as HTML or PDF, under a partner contract.", "url": "https://www.anchorterminal.com/tools/eat-this-much", "markdownUrl": "https://www.anchorterminal.com/tools/eat-this-much.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/eat-this-much.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/eat-this-much.json", "dns": "eat-this-much.grade.anchorterminal.com", "license": "Proprietary service under a partner contract; the website terms cover the consumer service", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API keys sent as X-API-Key or Authorization: Bearer. Keys are created, listed and deleted through /gapi/keys/ by an API user, who may also use a logged-in session cookie; the raw key is shown once. Access is by contract: the partner page says there is no self-serve signup, partners are onboarded after a recommended approach and contract are agreed, and the API is in early access with a limited number of partners (https://www.eatthismuch.com/partner-api, checked 3 November 2026).", "pricing": "paid", "pricingNotes": "Pricing is tailored to each partner's use case and volume, with no public price list. Calls are metered in credits per the OpenAPI, 50 for a week plan, 10 for a day, 5 for a meal, 10 to render or build groceries, 10 for a food search and 1 for a food lookup; the usage endpoint reports base credits, billable credits and a price per credit, whose schema example is $0.01, an example rather than a price. Evaluation before a contract is by contacting the company. The consumer app is free with Premium at $5 a month billed annually (checked 3 November 2026).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI document, the partner page or the changelog (checked 3 November 2026).", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.eatthismuch.com/g/docs", "openapi": "https://www.eatthismuch.com/g/openapi.yaml", "capabilities": [ "cooking.meal-plans", "cooking.grocery", "cooking.nutrition", "cooking.recipes" ], "tags": [ "hosted", "closed-source", "api-key", "openapi", "sales-led", "partner-only", "beta", "no-status-page", "ios", "android" ], "lastRelease": "2026-10-15", "graded": true, "anchor": { "graded": true, "score": 45.7, "grade": "E", "agentReady": false, "rank": 1129, "ranked": true, "rankOf": 1349, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 62, "maintenance": 58, "payments": 0, "reliability": 23, "schema": 75, "security": 48, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "Health, fitness, dietitian and healthcare apps that want generated meal plans and grocery lists under contract.", "strengths": [ "Public OpenAPI 3.0.3 (version 4.2.0) with curl samples, named response schemas and a per-operation credit cost", "Dated changelog with eight entries since 14 July 2026, breaking changes labelled, newest 15 October 2026", "Week, day or single meal generation to calories and macro ranges, with diet presets, exclusions by name or food id, a grocery list and HTML or PDF rendering", "Several keys per API user, created and deleted through the API, with a paginated usage history per key", "Concurrency limits published per operation (3 week, 10 day, 20 meal generations) with a documented 429" ], "weaknesses": [ "No self-serve signup. Partners are onboarded after a contract, the API is in early access and prices are tailored per partner", "No status page, SLA, Retry-After guidance or idempotency keys; generation is charged per call", "No official SDK, llms.txt or Markdown docs; the docs page is the OpenAPI document alone", "The website terms (undated) forbid bots and scraping and do not cover the API; the privacy policy is dated 3 December 2020", "No security.txt, disclosure policy or certification found, and keys have no scopes or read-only mode" ], "agentNotes": [ "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.7 } ], "editorialScores": { "ergonomics": 62, "maintenance": 58, "payments": 0, "reliability": 23, "schema": 75, "security": 48, "transparency": 47 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST 'https://www.eatthismuch.com/gapi/generate/day/' -H 'X-API-Key: YOUR_API_KEY' -H 'Content-Type: application/json' -d '{\"target_calories\": 2000, \"num_meals\": 3, \"preset_diet\": \"vegetarian\"}'" }, "letme": { "capability": "https://letme.dev/cooking.meal-plans", "tool": "https://letme.dev/eat-this-much" }, "area": "everyday", "provenance": { "legalEntity": "Eat This Much, Inc.", "domain": "eatthismuch.com", "domainRegistered": "2012-03-23", "endpointOnVendorDomain": true, "terms": "https://www.eatthismuch.com/terms", "privacy": "https://www.eatthismuch.com/privacy-policy", "statusPage": "", "changelog": "https://www.eatthismuch.com/g/docs/changelog", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms name Eat This Much, Inc., a Delaware corporation, under California law, with no last-updated date; amendments take effect 10 days after posting. The privacy policy is dated 3 December 2020 and names Louis DeMenthon as privacy officer.", "The terms forbid access through bots, spiders, scripts or software and any scraping, harvesting or data extraction. Recorded as a fact; public pages were read within robots.txt, which allows ClaudeBot with a 2 second crawl delay.", "The API's own terms are the partner contract, not public; the partner page states retention (data kept for the partnership, nutrition data cached up to 7 days).", "/.well-known/security.txt returns 404 with a server error page. No status page found; status.eatthismuch.com does not resolve.", "RDAP gives eatthismuch.com a registration date of 23 March 2012." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/eat-this-much.json", "live": { "slug": "eat-this-much", "securityTxt": { "url": "https://eatthismuch.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:44.288083399Z" }, "updatedAt": "2026-11-04T15:54:44.288083399Z" } }, "answer": "LogMeal scores 49.1 (D) on agent readiness against Eat This Much Partner API's 45.7 (E), and leads in 3 of 7 scored categories. Eat This Much Partner API leads on agent ergonomics and maintenance \u0026 community.", "b": { "slug": "logmeal", "name": "LogMeal", "vendor": "AIGecko Technologies S.L.", "vendorUrl": "https://logmeal.com/", "kind": "http-api", "category": "cooking", "summary": "LogMeal's Food AI Engine is a REST API from AIGecko Technologies, a University of Barcelona spin-off, that recognises dishes in a photo, returns ingredients, quantities and nutrients, and logs intakes, goals and plans per end user.", "url": "https://www.anchorterminal.com/tools/logmeal", "markdownUrl": "https://www.anchorterminal.com/tools/logmeal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/logmeal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/logmeal.json", "dns": "logmeal.grade.anchorterminal.com", "transports": [], "packages": [], "auth": "api-key", "authNotes": "Bearer JWT tokens of three kinds, issued after a browser signup and never expiring on their own. The APICompany token manages users and plans, each APIUser token runs recognition and logging for one end user, and APIUserManager tokens read and manage several users' intakes. Tokens are rotated with POST /v2/users/tokens/rotate after a password proof from /tokens/reauth valid for 10 minutes; a disabled APIUser loses access at once.", "pricing": "paid", "pricingNotes": "No price is published. A 30-day trial opens every endpoint with no card, capped at 200 queries and 5 registered users, then a paid plan (Analyse, Monitor, Recommend or Custom) is chosen in the account. Each plan carries monthly credits, with 1 credit per recognised image and none for nutrition and recipe data; calls beyond the credits are charged as extras at an unstated rate, billed at the end of the period.", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, pricing pages or terms (checked 2026-11-03). Plans are paid by debit or credit card in the account.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.logmeal.com/docs/guides-getting-started-welcome-logmeal-api", "llmsTxt": "https://docs.logmeal.com/llms.txt", "capabilities": [ "cooking.food-recognition", "cooking.nutrition", "cooking.meal-plans", "cooking.recipes", "cooking.grocery" ], "tags": [ "hosted", "paid", "free-trial", "no-card", "api-key", "llms-txt", "vision", "eu", "closed-source", "no-status-page" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 49.1, "grade": "D", "agentReady": false, "rank": 1045, "ranked": true, "rankOf": 1349, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 31, "payments": 20, "reliability": 42, "schema": 71, "security": 58, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Photo recognition that returns dishes, ingredients, grams and nutrients, with per-user tokens, rate-limit headers, backoff guidance and a 30-day trial with no card. No price is published, there is no status page, SLA or security programme, and submitted images are kept indefinitely and used to develop models unless the user asks for deletion.", "bestFor": "Agents that log meals from photos for a person and keep a nutrition history with goals, plans and manager oversight, within the EU.", "strengths": [ "One image call returns segmented dishes with ranked candidates, serving size in grams and a path to ingredients and more than 35 nutrients", "Per-user and per-manager bearer tokens with a rotation endpoint, a password proof step and instant disabling of an end user", "Rate limits published with numbers and reported in RateLimit-* and X-Account-Credits-* headers, with documented exponential backoff on 429", "Markdown docs for every endpoint through llms.txt, generated from an OpenAPI specification, with deprecated endpoints marked and their replacements named", "A 30-day trial of every endpoint with no card, capped at 200 queries and 5 users" ], "weaknesses": [ "No plan price is published; the pricing pages describe credits and limits and leave figures to the account", "No status page, SLA, security.txt, disclosure policy or certification found; support answers within 24 to 48 hours on weekdays", "Food images and nutrition data are retained without a time limit and used to develop models by default, and the terms let LogMeal train on submitted data", "No OpenAPI file link, no official SDK and no dated changelog; the reference's 'ready-to-use code' is generated snippets", "Intake writes have no idempotency key, so a retried recognition call logs a second intake and spends a second credit" ], "agentNotes": [ "Create one APIUser per person with the company token, set the user's country and language first, and call recognition with that user's token only", "Send JPEG images resized before upload; a 429 may mean the per-second, daily or, on the trial, monthly limit, so wait for RateLimit-Reset or Retry-After and back off exponentially", "Read GET /v2/info/limitations before a batch, since it reports credits and daily limits without spending any", "Do not retry a recognition call blindly; each successful POST to /v2/image/segmentation/complete logs an intake and uses a credit, so check for the imageId first", "Tell the person that uploaded photos are kept and used to develop LogMeal's models unless deletion is requested" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 49.1 } ], "editorialScores": { "ergonomics": 54, "maintenance": 31, "payments": 20, "reliability": 42, "schema": 71, "security": 58, "transparency": 49 }, "provenanceScore": 64, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST https://api.logmeal.com/v2/image/segmentation/complete -H \"Authorization: Bearer $LOGMEAL_APIUSER_TOKEN\" -F \"image=@meal.jpg\"" }, "letme": { "capability": "https://letme.dev/cooking.food-recognition", "tool": "https://letme.dev/logmeal" }, "area": "everyday", "provenance": { "legalEntity": "AIGecko Technologies S.L.", "domain": "logmeal.com", "domainRegistered": "2017-12-03", "endpointOnVendorDomain": true, "terms": "https://logmeal.com/terms", "privacy": "https://logmeal.com/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "AIGecko Technologies S.L. is named in the terms (last updated 10/03/2025, read as 10 March 2025) and, as AIGECKO TECHNOLOGIES SL with tax id B-02682300 and an address in Igualada, in the privacy policy (last updated 09/05/2025, read as 9 May 2025). Both choose Spanish law and the courts of Barcelona.", "The terms contain no clause on automated access; they forbid use that harms server stability. logmeal.com/robots.txt disallows /wp-admin/ and one plugin path; docs.logmeal.com/robots.txt disallows edit, login and api-next paths and points to llms.txt; api.logmeal.com has no robots.txt (404).", "No status page, changelog (docs.logmeal.com/changelog is 404), security.txt (404 on logmeal.com, docs.logmeal.com and api.logmeal.com) or MCP registry entry found.", "The privacy policy's introduction says it applies to data collected through the website while its first section covers app and API data, so its scope is unclear.", "RDAP gives logmeal.com a registration date of 3 December 2017." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/logmeal.json", "live": { "slug": "logmeal", "securityTxt": { "url": "https://logmeal.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:48.14444986Z" }, "updatedAt": "2026-11-04T15:52:48.14444986Z" } }, "edges": [ { "by": 27, "category": "maintenance", "leads": "eat-this-much", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed service. The welcome and feature overview pages carry an updatedAt of 7 October 2026, within 30 days of 3 November, and the credential rotation endpoints are documented; no dated API change exists beyond that, so the docs update stands in (25 of 30). No dated changelog, so three changes in 90 days are not established (0 of 20). Email support within 24 to 48 hours on weekdays and a contact form, no public changelog or community channel (6 of 15). No official SDK and no MCP registry entry (0 of 15). No package to assess (0 of 10). 25 + 0 + 6 + 0 + 0 = 31." }, "scores": { "a": 58, "b": 31 } }, { "by": 20, "category": "payments", "leads": "logmeal", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No x402, MPP or L402 (0 of 40). No price is published; the pricing pages name the plans and describe credits, and the figures sit in the account (0 of 20). A 30-day trial of every endpoint with no card, capped at 200 queries and 5 users (20 of 20). A person signs up in a browser and chooses a plan there (0 of 20). 0 + 0 + 20 + 0 = 20." }, "scores": { "a": 0, "b": 20 } }, { "by": 19, "category": "reliability", "leads": "logmeal", "name": "Reliability", "reasons": { "a": "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.", "b": "Read with the hosted lines. No status page was found on logmeal.com, the docs or llms.txt, and a search found none (0), so there is no incident history to read (5). Limits are published with numbers, 20 images a day and 1 a second per APIUser on standard plans, monthly credits per company, and 200 queries on the trial (15). HTTP 429 is documented with RateLimit-Reset, troubleshooting says to back off exponentially and respect Retry-After, but intake writes have no idempotency key (12 of 15). No SLA; the pricing page promises email answers within 24 to 48 hours on weekdays (0 of 10). The v2 API is generally available (10). 0 + 5 + 15 + 12 + 0 + 10 = 42." }, "scores": { "a": 23, "b": 42 } }, { "by": 10, "category": "security", "leads": "logmeal", "name": "Security \u0026 auth", "reasons": { "a": "Per-user API keys, several per user, created and deleted through the API, the raw key shown once, no expiry or scopes; the key endpoints also accept a session cookie (20 of 30). No read-only key; the only destructive call is deleting a key (6 of 20). Responses are the vendor's own recipe and food data, no untrusted content (10 of 15). GET /gapi/usage-history/ gives a paginated request log per key with credits (12 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0 of 20). Total 48.", "b": "Three bearer token types scoped by role (company, end user, manager), one token per end user, a rotation endpoint that needs a fresh password proof, and instant disabling of an end user; the tokens are JWTs with no stated expiry and no finer scopes (24 of 30). Per-user tokens cannot reach other users, managers see only the users they are granted, and deletion of intakes is a separate endpoint, but there is no read-only token and no confirmation step (15 of 20). Food names come from LogMeal's own model and dataset, with custom recipe names from the customer (10 of 15). GET /v2/info/usages returns request history per APIUser and credit headers show spend per call (9 of 15). No security.txt (404 on three hosts), disclosure policy, bug bounty or certification found (0 of 20). 24 + 15 + 10 + 9 + 0 = 58." }, "scores": { "a": 48, "b": 58 } }, { "by": 8, "category": "ergonomics", "leads": "eat-this-much", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Recognition responses carry polygons, bounding boxes and recursive subclasses for every segment with no field selection; the language parameter is the only shaping control (10 of 25). History by date range, daily and weekly summaries, a batch endpoint for up to five users, no pagination on lists (12 of 20). Numeric codes with messages, such as 708 naming the valid languages, and troubleshooting guidance per status (15 of 20). Reads are safe to repeat; each recognition POST logs a new intake and spends a credit with no idempotency key (8 of 20). One required field (the image) with defaults from the user's profile, but no official SDK; the 'ready-to-use code in 35+ languages' is generated snippets (9 of 15). 10 + 12 + 15 + 8 + 9 = 54." }, "scores": { "a": 62, "b": 54 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Eat This Much, Inc.", "b": "AIGecko Technologies S.L.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under a partner contract; the website terms cover the consumer service", "b": "none", "name": "Licence" }, { "a": "0", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-15", "b": "2026-10-07", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "2020-12-03", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "LogMeal scores 49.1 (D) on agent readiness against Eat This Much Partner API's 45.7 (E), and leads in 3 of 7 scored categories. Eat This Much Partner API leads on agent ergonomics and maintenance \u0026 community.", "question": "Which is better for AI agents, Eat This Much Partner API or LogMeal?" }, { "answer": "Both need an API key.", "question": "Do Eat This Much Partner API and LogMeal need an API key?" }, { "answer": "No hosted endpoint is listed for Eat This Much Partner API. No hosted endpoint is listed for LogMeal.", "question": "Can an agent call Eat This Much Partner API and LogMeal without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 62 against 54", "Maintenance \u0026 community, 58 against 31" ], "also": null, "goodFor": "Health, fitness, dietitian and healthcare apps that want generated meal plans and grocery lists under contract.", "slug": "eat-this-much", "watchFor": "No self-serve signup. Partners are onboarded after a contract, the API is in early access and prices are tailored per partner" }, { "aheadOn": [ "Reliability, 42 against 23", "Security \u0026 auth, 58 against 48", "Payments \u0026 pricing, 20 against 0" ], "also": [ "Free to start without a card" ], "goodFor": "Agents that log meals from photos for a person and keep a nutrition history with goals, plans and manager oversight, within the EU.", "slug": "logmeal", "watchFor": "No plan price is published; the pricing pages describe credits and limits and leave figures to the account" } ], "history": null, "job": { "capability": "cooking.meal-plans", "name": "Cooking meal plans" }, "others": [ { "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.json", "title": "Eat This Much Partner API vs fatsecret Platform API", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret" }, { "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-nutritionix.json", "title": "Eat This Much Partner API vs Nutritionix API", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-nutritionix" }, { "json": "https://www.anchorterminal.com/compare/fatsecret-vs-logmeal.json", "title": "fatsecret Platform API vs LogMeal", "url": "https://www.anchorterminal.com/compare/fatsecret-vs-logmeal" }, { "json": "https://www.anchorterminal.com/compare/logmeal-vs-nutritionix.json", "title": "LogMeal vs Nutritionix API", "url": "https://www.anchorterminal.com/compare/logmeal-vs-nutritionix" }, { "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.json", "title": "Eat This Much Partner API vs Edamam", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-edamam" }, { "json": "https://www.anchorterminal.com/compare/edamam-vs-logmeal.json", "title": "Edamam vs LogMeal", "url": "https://www.anchorterminal.com/compare/edamam-vs-logmeal" }, { "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.json", "title": "Eat This Much Partner API vs spoonacular", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular" }, { "json": "https://www.anchorterminal.com/compare/logmeal-vs-spoonacular.json", "title": "LogMeal vs spoonacular", "url": "https://www.anchorterminal.com/compare/logmeal-vs-spoonacular" } ], "panel": null, "scores": [ { "by": 19, "eat-this-much": 23, "edge": "logmeal", "key": "reliability", "logmeal": 42, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "eat-this-much": 75, "edge": "eat-this-much", "key": "schema", "logmeal": 71, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 8, "eat-this-much": 62, "edge": "eat-this-much", "key": "ergonomics", "logmeal": 54, "name": "Agent ergonomics", "weight": 13 }, { "by": 10, "eat-this-much": 48, "edge": "logmeal", "key": "security", "logmeal": 58, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "eat-this-much": 0, "edge": "logmeal", "key": "payments", "logmeal": 20, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 27, "eat-this-much": 58, "edge": "eat-this-much", "key": "maintenance", "logmeal": 31, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 4, "eat-this-much": 61, "edge": "eat-this-much", "key": "transparency", "logmeal": 57, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "LogMeal scores 49.1 (D) on agent readiness against Eat This Much Partner API's 45.7 (E), and leads in 3 of 7 scored categories. Eat This Much Partner API leads on agent ergonomics and maintenance \u0026 community. Both do cooking meal plans.", "tasks": null, "tutorials": [], "verdicts": { "eat-this-much": "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.", "logmeal": "Photo recognition that returns dishes, ingredients, grams and nutrients, with per-user tokens, rate-limit headers, backoff guidance and a 30-day trial with no card. No price is published, there is no status page, SLA or security programme, and submitted images are kept indefinitely and used to develop models unless the user asks for deletion." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal", "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.min.md" }, "markdown": "LogMeal scores 49.1 (D) on agent readiness against Eat This Much Partner API's 45.7 (E), and leads in 3 of 7 scored categories. Eat This Much Partner API leads on agent ergonomics and maintenance \u0026 community. Both do cooking meal plans.\n\n- Eat This Much Partner API: grade E, 45.7/100, rank #1129 of 1349. Markdown https://www.anchorterminal.com/tools/eat-this-much.md · JSON https://www.anchorterminal.com/api/v1/tools/eat-this-much.json\n- LogMeal: grade D, 49.1/100, rank #1045 of 1349. Markdown https://www.anchorterminal.com/tools/logmeal.md · JSON https://www.anchorterminal.com/api/v1/tools/logmeal.json\n- Best recipe, nutrition and meal planning APIs for AI agents: https://www.anchorterminal.com/best/cooking/index.md\n- All 28 cooking comparisons: https://www.anchorterminal.com/compare/cooking/index.md\n\n## Which one, for what\n\n### Eat This Much Partner API (E)\n\nGood for: Health, fitness, dietitian and healthcare apps that want generated meal plans and grocery lists under contract.\n\nAhead on:\n- Agent ergonomics, 62 against 54\n- Maintenance \u0026 community, 58 against 31\n\nWatch for: No self-serve signup. Partners are onboarded after a contract, the API is in early access and prices are tailored per partner\n\n### LogMeal (D)\n\nGood for: Agents that log meals from photos for a person and keep a nutrition history with goals, plans and manager oversight, within the EU.\n\nAhead on:\n- Reliability, 42 against 23\n- Security \u0026 auth, 58 against 48\n- Payments \u0026 pricing, 20 against 0\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No plan price is published; the pricing pages describe credits and limits and leave figures to the account\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Eat This Much Partner API +27\n\n- 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.\n- LogMeal (31): Read as a closed service. The welcome and feature overview pages carry an updatedAt of 7 October 2026, within 30 days of 3 November, and the credential rotation endpoints are documented; no dated API change exists beyond that, so the docs update stands in (25 of 30). No dated changelog, so three changes in 90 days are not established (0 of 20). Email support within 24 to 48 hours on weekdays and a contact form, no public changelog or community channel (6 of 15). No official SDK and no MCP registry entry (0 of 15). No package to assess (0 of 10). 25 + 0 + 6 + 0 + 0 = 31.\n\n### Payments \u0026 pricing: LogMeal +20\n\n- 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.\n- LogMeal (20): No x402, MPP or L402 (0 of 40). No price is published; the pricing pages name the plans and describe credits, and the figures sit in the account (0 of 20). A 30-day trial of every endpoint with no card, capped at 200 queries and 5 users (20 of 20). A person signs up in a browser and chooses a plan there (0 of 20). 0 + 0 + 20 + 0 = 20.\n\n### Reliability: LogMeal +19\n\n- 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.\n- LogMeal (42): Read with the hosted lines. No status page was found on logmeal.com, the docs or llms.txt, and a search found none (0), so there is no incident history to read (5). Limits are published with numbers, 20 images a day and 1 a second per APIUser on standard plans, monthly credits per company, and 200 queries on the trial (15). HTTP 429 is documented with RateLimit-Reset, troubleshooting says to back off exponentially and respect Retry-After, but intake writes have no idempotency key (12 of 15). No SLA; the pricing page promises email answers within 24 to 48 hours on weekdays (0 of 10). The v2 API is generally available (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.\n\n### Security \u0026 auth: LogMeal +10\n\n- Eat This Much Partner API (48): Per-user API keys, several per user, created and deleted through the API, the raw key shown once, no expiry or scopes; the key endpoints also accept a session cookie (20 of 30). No read-only key; the only destructive call is deleting a key (6 of 20). Responses are the vendor's own recipe and food data, no untrusted content (10 of 15). GET /gapi/usage-history/ gives a paginated request log per key with credits (12 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0 of 20). Total 48.\n- LogMeal (58): Three bearer token types scoped by role (company, end user, manager), one token per end user, a rotation endpoint that needs a fresh password proof, and instant disabling of an end user; the tokens are JWTs with no stated expiry and no finer scopes (24 of 30). Per-user tokens cannot reach other users, managers see only the users they are granted, and deletion of intakes is a separate endpoint, but there is no read-only token and no confirmation step (15 of 20). Food names come from LogMeal's own model and dataset, with custom recipe names from the customer (10 of 15). GET /v2/info/usages returns request history per APIUser and credit headers show spend per call (9 of 15). No security.txt (404 on three hosts), disclosure policy, bug bounty or certification found (0 of 20). 24 + 15 + 10 + 9 + 0 = 58.\n\n### Agent ergonomics: Eat This Much Partner API +8\n\n- 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.\n- LogMeal (54): Recognition responses carry polygons, bounding boxes and recursive subclasses for every segment with no field selection; the language parameter is the only shaping control (10 of 25). History by date range, daily and weekly summaries, a batch endpoint for up to five users, no pagination on lists (12 of 20). Numeric codes with messages, such as 708 naming the valid languages, and troubleshooting guidance per status (15 of 20). Reads are safe to repeat; each recognition POST logs a new intake and spends a credit with no idempotency key (8 of 20). One required field (the image) with defaults from the user's profile, but no official SDK; the 'ready-to-use code in 35+ languages' is generated snippets (9 of 15). 10 + 12 + 15 + 8 + 9 = 54.\n\n## Score by category\n\n| Category | Weight | Eat This Much Partner API | LogMeal | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 23 | 42 | LogMeal +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 71 | Eat This Much Partner API +4 |\n| Agent ergonomics | 13% (16.2 this run) | 62 | 54 | Eat This Much Partner API +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 58 | LogMeal +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 20 | LogMeal +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 58 | 31 | Eat This Much Partner API +27 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 57 | Eat This Much Partner API +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.7 · E** | **49.1 · D** | |\n\n## Facts side by side\n\n| Fact | Eat This Much Partner API | LogMeal |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Eat This Much, Inc. | AIGecko Technologies S.L. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under a partner contract; the website terms cover the consumer service | none |\n| Tools exposed | 0 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-15 | 2026-10-07 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2020-12-03 | no date given |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n\n## Verdicts\n\n**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.\n\n**LogMeal.** Photo recognition that returns dishes, ingredients, grams and nutrients, with per-user tokens, rate-limit headers, backoff guidance and a 30-day trial with no card. No price is published, there is no status page, SLA or security programme, and submitted images are kept indefinitely and used to develop models unless the user asks for deletion.\n\n## Before you call either\n\n### Eat This Much Partner API\n\n1. Access needs a contract with Eat This Much first; ask the person to contact support@eatthismuch.com before planning calls\n2. 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\n3. 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\n4. Request food_output=simple unless expanded nutrition is needed, and set include_groceries=false when the list is not wanted; each call costs credits\n5. Read the changelog before upgrading, since 3.0.0 moved preferred_food_type into meal_settings and 4.0.0 renamed amount to servings\n\n### LogMeal\n\n1. Create one APIUser per person with the company token, set the user's country and language first, and call recognition with that user's token only\n2. Send JPEG images resized before upload; a 429 may mean the per-second, daily or, on the trial, monthly limit, so wait for RateLimit-Reset or Retry-After and back off exponentially\n3. Read GET /v2/info/limitations before a batch, since it reports credits and daily limits without spending any\n4. Do not retry a recognition call blindly; each successful POST to /v2/image/segmentation/complete logs an intake and uses a credit, so check for the imageId first\n5. Tell the person that uploaded photos are kept and used to develop LogMeal's models unless deletion is requested\n\n## Questions\n\n### Which is better for AI agents, Eat This Much Partner API or LogMeal?\n\nLogMeal scores 49.1 (D) on agent readiness against Eat This Much Partner API's 45.7 (E), and leads in 3 of 7 scored categories. Eat This Much Partner API leads on agent ergonomics and maintenance \u0026 community.\n\n### Do Eat This Much Partner API and LogMeal need an API key?\n\nBoth need an API key.\n\n### Can an agent call Eat This Much Partner API and LogMeal without installing anything?\n\nNo hosted endpoint is listed for Eat This Much Partner API. No hosted endpoint is listed for LogMeal.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-this-much\", \"b\": \"logmeal\"}`. From a terminal: `anchor compare eat-this-much logmeal`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-this-much.json and https://www.anchorterminal.com/api/v1/tools/logmeal.json\n\n## Other comparisons with Eat This Much Partner API or LogMeal\n\n- [Eat This Much Partner API vs fatsecret Platform API](https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.md)\n- [Eat This Much Partner API vs Nutritionix API](https://www.anchorterminal.com/compare/eat-this-much-vs-nutritionix.md)\n- [fatsecret Platform API vs LogMeal](https://www.anchorterminal.com/compare/fatsecret-vs-logmeal.md)\n- [LogMeal vs Nutritionix API](https://www.anchorterminal.com/compare/logmeal-vs-nutritionix.md)\n- [Eat This Much Partner API vs Edamam](https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.md)\n- [Edamam vs LogMeal](https://www.anchorterminal.com/compare/edamam-vs-logmeal.md)\n- [Eat This Much Partner API vs spoonacular](https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.md)\n- [LogMeal vs spoonacular](https://www.anchorterminal.com/compare/logmeal-vs-spoonacular.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Eat This Much Partner API vs LogMeal", "url": "" } ], "description": "LogMeal scores 49.1 (D) to Eat This Much Partner's 45.7 (E) for cooking meal plans. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Eat This Much Partner API E 45.7", "LogMeal D 49.1", "scores" ], "h1": "Eat This Much Partner API vs LogMeal", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/eat-this-much-vs-logmeal", "published": "2026-10-01", "section": "tools", "title": "Eat This Much Partner vs LogMeal for AI agents (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal" }, "tokens": { "markdown": 3650, "slim": 2130 }, "version": 1 }