Eat This Much Partner API vs LogMeal

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.

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.

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.

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.

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.