# Eat This Much Partner API vs LogMeal

> 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.

- Canonical: https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal
- Markdown: https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.md (~3,650 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 <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. 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-03

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 & community. Both do cooking meal plans.

- 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
- 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
- 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:
- Agent ergonomics, 62 against 54
- Maintenance & community, 58 against 31

Watch for: No self-serve signup. Partners are onboarded after a contract, the API is in early access and prices are tailored per partner

### LogMeal (D)

Good for: Agents that log meals from photos for a person and keep a nutrition history with goals, plans and manager oversight, within the EU.

Ahead on:
- Reliability, 42 against 23
- Security & auth, 58 against 48
- Payments & pricing, 20 against 0

Also in its favour:
- Free to start without a card

Watch for: No plan price is published; the pricing pages describe credits and limits and leave figures to the account


## Why the edge

### Maintenance & community: Eat This Much Partner API +27

- 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.
- 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.

### Payments & pricing: LogMeal +20

- 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.
- 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.

### Reliability: LogMeal +19

- 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.
- 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.

### Security & auth: LogMeal +10

- 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.
- 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.

### Agent ergonomics: Eat This Much Partner API +8

- 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.
- 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.

## Score by category

| Category | Weight | Eat This Much Partner API | LogMeal | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 23 | 42 | LogMeal +19 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 75 | 71 | Eat This Much Partner API +4 |
| Agent ergonomics | 13% (16.2 this run) | 62 | 54 | Eat This Much Partner API +8 |
| Security & auth | 14% (17.5 this run) | 48 | 58 | LogMeal +10 |
| Payments & pricing | 10% (12.5 this run) | 0 | 20 | LogMeal +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 58 | 31 | Eat This Much Partner API +27 |
| Transparency & trust | 7% (8.8 this run) | 61 | 57 | Eat This Much Partner API +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **45.7 · E** | **49.1 · D** | |

## Facts side by side

| Fact | Eat This Much Partner API | LogMeal |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Eat This Much, Inc. | AIGecko Technologies S.L. |
| 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 | 2026-10-07 |
| 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 | yes |
| 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 |

## 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.

**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.

## 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

### LogMeal

1. 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
2. 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
3. Read GET /v2/info/limitations before a batch, since it reports credits and daily limits without spending any
4. 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
5. Tell the person that uploaded photos are kept and used to develop LogMeal's models unless deletion is requested

## Questions

### Which is better for AI agents, Eat This Much Partner API or LogMeal?

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 & community.

### Do Eat This Much Partner API and LogMeal need an API key?

Both need an API key.

### Can an agent call Eat This Much Partner API and LogMeal without installing anything?

No hosted endpoint is listed for Eat This Much Partner API. No hosted endpoint is listed for LogMeal.


## For agents

- 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
- 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`
- 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

## Other comparisons with Eat This Much Partner API or LogMeal

- [Eat This Much Partner API vs fatsecret Platform API](https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.md)
- [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)
- [LogMeal vs Nutritionix API](https://www.anchorterminal.com/compare/logmeal-vs-nutritionix.md)
- [Eat This Much Partner API vs Edamam](https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.md)
- [Edamam vs LogMeal](https://www.anchorterminal.com/compare/edamam-vs-logmeal.md)
- [Eat This Much Partner API vs spoonacular](https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.md)
- [LogMeal vs spoonacular](https://www.anchorterminal.com/compare/logmeal-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