{ "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": "Eat This Much Partner API scores 45.7 (E) on agent readiness against Edamam's 42.2 (E), and leads in 4 of 7 scored categories. Edamam leads on reliability, agent ergonomics and payments \u0026 pricing.", "b": { "slug": "edamam", "name": "Edamam", "vendor": "Edamam", "vendorUrl": "https://developer.edamam.com/", "kind": "http-api", "category": "cooking", "summary": "Edamam sells nutrition REST APIs. Recipe Search covers about 2 million web recipes with diet and allergen filters, the Food Database adds barcode lookup and a Vision model, and Nutrition Analysis parses recipe text, with a hosted Food MCP server.", "url": "https://www.anchorterminal.com/tools/edamam", "markdownUrl": "https://www.anchorterminal.com/tools/edamam.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/edamam.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/edamam.json", "dns": "edamam.grade.anchorterminal.com", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.edamam.com/mcp/food", "packages": [], "auth": "api-key", "authNotes": "An `app_id` and `app_key` pair per application, created in the developer dashboard after a browser signup and a paid or trial plan. The OpenAPI document sends both as query parameters, or HTTP Basic, with an optional `Edamam-Account-User` header that becomes mandatory when active user tracking is switched on. The Food MCP takes `Authorization: Bearer \u003capp_id\u003e:\u003capp_key\u003e`. No scopes, expiry or rotation found.", "pricing": "paid", "pricingNotes": "Recipe Search Basic $9 a month for 10,000 calls (10 a minute, 10-day trial), Core $99 for 500,000, Plus $399 for 1,000,000 with Edamam-owned recipes that include instructions; Unlimited by contact. Food Database Basic $14 a month (30-day trial, 500 Vision calls), Core $69, Plus $299; Vision $0.015 a call on Core. Nutrition Analysis Basic $29, Core $299. All plans prepaid, month to month, human end-user requests only.", "priceSummary": "$9 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the API pages, the OpenAPI documents or the Food MCP page (checked 2026-11-03). Plans are prepaid subscriptions bought in the developer portal.", "endpoints": [] }, "toolCount": 2, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developer.edamam.com/edamam-docs-recipe-api", "openapi": "https://api.edamam.com/doc/open-api/recipe-search-v2.yaml", "capabilities": [ "cooking.recipes", "cooking.nutrition", "cooking.food-recognition", "cooking.grocery" ], "tags": [ "hosted", "paid", "free-trial", "api-key", "openapi", "mcp", "remote-mcp", "vision", "closed-source", "no-status-page" ], "graded": true, "anchor": { "graded": true, "score": 42.2, "grade": "E", "agentReady": false, "rank": 1187, "ranked": true, "rankOf": 1349, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 33, "payments": 25, "reliability": 30, "schema": 66, "security": 30, "transparency": 31 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "Recipe search with 36 health labels, nutrient range filters and field selection, documented in a public OpenAPI file, with a two-tool hosted MCP server for food nutrition and images. Web recipes carry no instructions, every plan is prepaid with human-only requests and tight caching rules, and the terms, privacy policy and any status page could not be read.", "bestFor": "Agents that need recipe candidates filtered by diet, allergen and nutrient ranges with nutrition on each, or food and barcode nutrition through the MCP tools.", "strengths": [ "Public OpenAPI 3.0.3 documents for Recipe Search v2 and the Food Database, with typed enums for diet, health, cuisine, dish and meal filters", "`field` selection of 31 response fields and `_links.next` paging keep responses sized for a context window", "Hosted Food MCP server with two compact tools, included with Food Database plans, reachable with the same app credentials", "Plan prices, call allowances and per-minute limits published for every API without a login", "Nutrition for 28 nutrients with diet and allergen labels generated by Edamam on every recipe" ], "weaknesses": [ "The API terms of use and privacy policy render by script and could not be read; no status page, security.txt or disclosure policy was found", "Web recipes return a source link and no cooking instructions; instructions need the $399 Plus plan's licensed set", "Credentials travel as `app_id` and `app_key` query parameters in the documented scheme, one pair per application with no scopes", "No free tier, 10-day or 30-day trials by plan, and all plans allow only human, end-user-driven requests, which an agent's calls may not satisfy", "No rate-limit error, 429 or Retry-After documented; the OpenAPI file lists only 400, 403 and 404" ], "agentNotes": [ "Send `app_id` and `app_key` as HTTP Basic or, for the MCP server, as `Authorization: Bearer \u003capp_id\u003e:\u003capp_key\u003e`, rather than in the query string", "Expect no instructions on web recipes; return the `url` of the source to the person, and ask for the Plus plan's Edamam-owned set when steps are needed", "Pass `field` to pick the response fields you need and follow `_links.next.href` for the next page; `type=public` is required on every search", "Keep each call tied to a person's request and cache only the fields the plan allows, since the plan pages forbid automated collection and end access without refund", "Show the 'Powered by Edamam' attribution with every result, as every plan requires" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.2 } ], "editorialScores": { "ergonomics": 71, "maintenance": 33, "payments": 25, "reliability": 30, "schema": 66, "security": 30, "transparency": 14 }, "provenanceScore": 47, "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 -u \"$EDAMAM_APP_ID:$EDAMAM_APP_KEY\" \"https://api.edamam.com/api/recipes/v2?type=public\u0026q=chicken\u0026health=gluten-free\u0026field=label\u0026field=url\"", "claudeCode": "claude mcp add --transport http edamam-food https://mcp.edamam.com/mcp/food --header \"Authorization: Bearer \u003capp_id\u003e:\u003capp_key\u003e\"", "config": { "mcpServers": { "edamam-food": { "headers": { "Authorization": "Bearer \u003capp_id\u003e:\u003capp_key\u003e" }, "url": "https://mcp.edamam.com/mcp/food" } } } }, "letme": { "capability": "https://letme.dev/cooking.recipes", "tool": "https://letme.dev/edamam" }, "area": "everyday", "unitPrices": [ { "item": "Recipe Search Basic", "unit": "month", "usd": 9, "note": "10,000 calls a month, 10 a minute, web recipes, 10-day trial" }, { "item": "Recipe Search Core", "unit": "month", "usd": 99, "note": "500,000 calls a month, 100 a minute, up to 1,000 results a call" }, { "item": "Recipe Search Plus", "unit": "month", "usd": 399, "note": "1,000,000 calls a month, Edamam-owned recipes with instructions, 10-day trial" }, { "item": "Food Database Basic", "unit": "month", "usd": 14, "note": "100,000 calls a month, 500 Vision calls, 30-day trial, Food MCP included" }, { "item": "Food Database Core", "unit": "month", "usd": 69, "note": "750,000 calls a month, Vision pay as you go" }, { "item": "Vision image analysis", "unit": "call", "usd": 0.015, "note": "On the Food Database Core plan; Plus includes 10,000 a month" }, { "item": "Nutrition Analysis Basic", "unit": "month", "usd": 29, "note": "2,500 recipes and 10,000 text lines a month; Core $299" } ], "provenance": { "legalEntity": "", "domain": "edamam.com", "domainRegistered": "2011-04-04", "endpointOnVendorDomain": true, "terms": "https://developer.edamam.com/about/terms", "privacy": "https://developer.edamam.com/about/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "No legal entity is named on any page read. The plan pages, docs and MCP page name only Edamam.", "developer.edamam.com/about/terms returned HTTP 200 with a 174-byte script shell and no text on 3 November 2026, and /about/privacy, /about, /terms and /privacy returned the same shell or 404, so the API terms of use and privacy policy are unread. www.edamam.com/about answered 403. The plan pages state that automated or programmatic requests to the API are prohibited and are stopped without refund; no clause on automated reading of the website was seen.", "www.edamam.com/robots.txt disallows /api/, /php/, /m and a few php paths for all crawlers and the whole site for 18 named bots including GPTBot; ClaudeBot and anthropic-ai are not named. developer.edamam.com/robots.txt has only comments. api.edamam.com has no robots.txt (404) and only the two OpenAPI documents were fetched there.", "No status page, changelog, security.txt (404) or llms.txt (404) found.", "RDAP gives edamam.com a registration date of 4 April 2011." ], "score": 47 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/edamam.json", "live": { "slug": "edamam", "probe": { "target": "https://mcp.edamam.com/mcp/food", "method": "get", "lastAt": "2026-11-04T19:34:34.93735809Z", "lastOk": true, "lastStatus": 405, "lastMs": 462, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 298, "p95ms24h": 384, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-04", "probes": 43, "ok": 43 } ] }, "securityTxt": { "url": "https://edamam.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:51.148952618Z" }, "updatedAt": "2026-11-04T19:34:34.93735809Z" } }, "edges": [ { "by": 30, "category": "transparency", "leads": "eat-this-much", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service whose API terms of use could not be read (the page is a script shell). The plan pages state the restrictions on caching, attribution and automated requests clearly (8 of 30). The privacy policy could not be read either, so no data-handling statement was scored (0 of 30, unchecked). Retired API versions are marked on their docs pages and the recipe docs announce the end of Shopping List V1 on June 30 with no year (6 of 20). No subprocessors or data locations found (0 of 20). 8 + 0 + 6 + 0 = 14." }, "scores": { "a": 61, "b": 31 } }, { "by": 25, "category": "payments", "leads": "edamam", "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). Monthly plan prices and call allowances are public for all three APIs, with per-call prices only for Vision ($0.015) and the Site Parser ($0.06 to $0.01), so plan-priced with some per-unit rates (15 of 20). No free tier; 10-day trials on Recipe Search Basic and Plus, a 30-day trial on Food Database Basic, and the pages do not say whether a card is needed (10 of 20). A person signs up in the developer portal and picks a plan in a browser (0 of 20). 0 + 15 + 10 + 0 = 25." }, "scores": { "a": 0, "b": 25 } }, { "by": 25, "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. No dated change was found on the API pages, which carry no changelog. The Food MCP page pins mcp-remote 0.14.3, a version npm published on 21 September 2026, so that page was written or changed within the last 90 days but not demonstrably within 30 (20 of 30). No three dated changes in 90 days (0 of 20). A support widget and form, email and phone on Core and above, no public changelog or community channel (5 of 15). No official SDK; the hosted MCP server is the vendor's but is absent from the official registry, which lists only third-party edamam servers (8 of 15). No package to assess (0 of 10). 20 + 0 + 5 + 8 + 0 = 33." }, "scores": { "a": 58, "b": 33 } }, { "by": 18, "category": "security", "leads": "eat-this-much", "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": "One `app_id` and `app_key` pair per application, documented as query parameters first and HTTP Basic second, with no scopes, expiry or rotation found; the MCP server takes the pair as a Bearer token. Plain keys (20) less 10 for the documented query string (10 of 30). The APIs are read-only for an outside caller, but there is no read-only key mode and nothing to confirm (12 of 20). Recipe titles, ingredient lines and source urls come from the public web, and no guidance on treating them as untrusted was found; the MCP page only says to present results as estimates (5 of 15). Active user tracking counts users per app for billing, but no request log was found (3 of 15). security.txt returns 404 on developer.edamam.com and no disclosure policy, bug bounty or certification was found (0 of 20). 10 + 12 + 5 + 3 + 0 = 30." }, "scores": { "a": 48, "b": 30 } }, { "by": 9, "category": "schema", "leads": "eat-this-much", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "Public OpenAPI 3.0.3 documents for Recipe Search v2 (four operations) and the Food Database, and the Food MCP's two tools take typed arguments (25). No llms.txt (404) and no Markdown docs (0 of 10). Operation and parameter descriptions state purpose, and the by-uri description warns that missing recipes are not flagged, but there is little on when not to use an operation (12 of 20). Enums for type, diet, health, cuisineType, mealType, dishType, imageSize, co2EmissionsClass and 31 field names, required flags, a 1 to 20 bound on uris, and the MCP arguments are required lists and strings (14 of 15). Examples on the docs page, an `Errors` schema of errorCode, message and params, but no example error body and no code list (9 of 15). v2 in the path and retired versions marked, but no changelog and a Shopping List V1 end date with no year (6 of 15). 25 + 0 + 12 + 14 + 9 + 6 = 66." }, "scores": { "a": 75, "b": 66 } }, { "by": 9, "category": "ergonomics", "leads": "edamam", "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": "`field` selects any of 31 response fields, results a call are capped by plan at 100 or 1,000, and the MCP server lists two compact tools (22 of 25). `_links.next` paging with diet, health, cuisine, dish, meal, time, calorie and about 40 nutrient range filters (20 of 20). An error schema with errorCode, message and params, but the codes are not enumerated (10 of 20). Every recipe operation is a read and safe to repeat; the shopping-list POST aggregates quantities and stores nothing; the MCP tools' annotations were not read (12 of 20). `type` and `q` are the only required search parameters, with no official SDK in any language (7 of 15). 22 + 20 + 10 + 12 + 7 = 71." }, "scores": { "a": 62, "b": 71 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Eat This Much, Inc.", "b": "Edamam", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp.edamam.com/mcp/food", "name": "Hosted endpoint" }, { "a": "", "b": "Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "not published", "b": "$9 per month (plan)", "name": "Price for cooking recipes" }, { "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": "2", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-10-15", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2020-12-03", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Eat This Much Partner API scores 45.7 (E) on agent readiness against Edamam's 42.2 (E), and leads in 4 of 7 scored categories. Edamam leads on reliability, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, Eat This Much Partner API or Edamam?" }, { "answer": "Both need an API key.", "question": "Do Eat This Much Partner API and Edamam need an API key?" }, { "answer": "No hosted endpoint is listed for Eat This Much Partner API. Edamam has a hosted endpoint at https://mcp.edamam.com/mcp/food.", "question": "Can an agent call Eat This Much Partner API and Edamam without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 75 against 66", "Security \u0026 auth, 48 against 30", "Maintenance \u0026 community, 58 against 33", "Transparency \u0026 trust, 61 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, 30 against 23", "Agent ergonomics, 71 against 62", "Payments \u0026 pricing, 25 against 0" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Agents that need recipe candidates filtered by diet, allergen and nutrient ranges with nutrition on each, or food and barcode nutrition through the MCP tools.", "slug": "edamam", "watchFor": "The API terms of use and privacy policy render by script and could not be read; no status page, security.txt or disclosure policy was found" } ], "history": null, "job": { "capability": "cooking.recipes", "name": "Cooking recipes" }, "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/edamam-vs-nutritionix.json", "title": "Edamam vs Nutritionix API", "url": "https://www.anchorterminal.com/compare/edamam-vs-nutritionix" }, { "json": "https://www.anchorterminal.com/compare/edamam-vs-fatsecret.json", "title": "Edamam vs fatsecret Platform API", "url": "https://www.anchorterminal.com/compare/edamam-vs-fatsecret" }, { "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/edamam-vs-spoonacular.json", "title": "Edamam vs spoonacular", "url": "https://www.anchorterminal.com/compare/edamam-vs-spoonacular" }, { "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.json", "title": "Eat This Much Partner API vs LogMeal", "url": "https://www.anchorterminal.com/compare/eat-this-much-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" } ], "panel": null, "scores": [ { "by": 7, "eat-this-much": 23, "edamam": 30, "edge": "edamam", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "eat-this-much": 75, "edamam": 66, "edge": "eat-this-much", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 9, "eat-this-much": 62, "edamam": 71, "edge": "edamam", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 18, "eat-this-much": 48, "edamam": 30, "edge": "eat-this-much", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 25, "eat-this-much": 0, "edamam": 25, "edge": "edamam", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 25, "eat-this-much": 58, "edamam": 33, "edge": "eat-this-much", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 30, "eat-this-much": 61, "edamam": 31, "edge": "eat-this-much", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Eat This Much Partner API scores 45.7 (E) on agent readiness against Edamam's 42.2 (E), and leads in 4 of 7 scored categories. Edamam leads on reliability, agent ergonomics and payments \u0026 pricing. Both do cooking recipes.", "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.", "edamam": "Recipe search with 36 health labels, nutrient range filters and field selection, documented in a public OpenAPI file, with a two-tool hosted MCP server for food nutrition and images. Web recipes carry no instructions, every plan is prepaid with human-only requests and tight caching rules, and the terms, privacy policy and any status page could not be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/eat-this-much-vs-edamam", "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.min.md" }, "markdown": "Eat This Much Partner API scores 45.7 (E) on agent readiness against Edamam's 42.2 (E), and leads in 4 of 7 scored categories. Edamam leads on reliability, agent ergonomics and payments \u0026 pricing. Both do cooking recipes.\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- Edamam: grade E, 42.2/100, rank #1187 of 1349. Markdown https://www.anchorterminal.com/tools/edamam.md · JSON https://www.anchorterminal.com/api/v1/tools/edamam.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- Schema \u0026 documentation, 75 against 66\n- Security \u0026 auth, 48 against 30\n- Maintenance \u0026 community, 58 against 33\n- Transparency \u0026 trust, 61 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### Edamam (E)\n\nGood for: Agents that need recipe candidates filtered by diet, allergen and nutrient ranges with nutrition on each, or food and barcode nutrition through the MCP tools.\n\nAhead on:\n- Reliability, 30 against 23\n- Agent ergonomics, 71 against 62\n- Payments \u0026 pricing, 25 against 0\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: The API terms of use and privacy policy render by script and could not be read; no status page, security.txt or disclosure policy was found\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Eat This Much Partner API +30\n\n- 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.\n- Edamam (31): Closed service whose API terms of use could not be read (the page is a script shell). The plan pages state the restrictions on caching, attribution and automated requests clearly (8 of 30). The privacy policy could not be read either, so no data-handling statement was scored (0 of 30, unchecked). Retired API versions are marked on their docs pages and the recipe docs announce the end of Shopping List V1 on June 30 with no year (6 of 20). No subprocessors or data locations found (0 of 20). 8 + 0 + 6 + 0 = 14.\n\n### Payments \u0026 pricing: Edamam +25\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- Edamam (25): No x402, MPP or L402 (0 of 40). Monthly plan prices and call allowances are public for all three APIs, with per-call prices only for Vision ($0.015) and the Site Parser ($0.06 to $0.01), so plan-priced with some per-unit rates (15 of 20). No free tier; 10-day trials on Recipe Search Basic and Plus, a 30-day trial on Food Database Basic, and the pages do not say whether a card is needed (10 of 20). A person signs up in the developer portal and picks a plan in a browser (0 of 20). 0 + 15 + 10 + 0 = 25.\n\n### Maintenance \u0026 community: Eat This Much Partner API +25\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- Edamam (33): Read as a closed service. No dated change was found on the API pages, which carry no changelog. The Food MCP page pins mcp-remote 0.14.3, a version npm published on 21 September 2026, so that page was written or changed within the last 90 days but not demonstrably within 30 (20 of 30). No three dated changes in 90 days (0 of 20). A support widget and form, email and phone on Core and above, no public changelog or community channel (5 of 15). No official SDK; the hosted MCP server is the vendor's but is absent from the official registry, which lists only third-party edamam servers (8 of 15). No package to assess (0 of 10). 20 + 0 + 5 + 8 + 0 = 33.\n\n### Security \u0026 auth: Eat This Much Partner API +18\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- Edamam (30): One `app_id` and `app_key` pair per application, documented as query parameters first and HTTP Basic second, with no scopes, expiry or rotation found; the MCP server takes the pair as a Bearer token. Plain keys (20) less 10 for the documented query string (10 of 30). The APIs are read-only for an outside caller, but there is no read-only key mode and nothing to confirm (12 of 20). Recipe titles, ingredient lines and source urls come from the public web, and no guidance on treating them as untrusted was found; the MCP page only says to present results as estimates (5 of 15). Active user tracking counts users per app for billing, but no request log was found (3 of 15). security.txt returns 404 on developer.edamam.com and no disclosure policy, bug bounty or certification was found (0 of 20). 10 + 12 + 5 + 3 + 0 = 30.\n\n### Schema \u0026 documentation: Eat This Much Partner API +9\n\n- 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.\n- Edamam (66): Public OpenAPI 3.0.3 documents for Recipe Search v2 (four operations) and the Food Database, and the Food MCP's two tools take typed arguments (25). No llms.txt (404) and no Markdown docs (0 of 10). Operation and parameter descriptions state purpose, and the by-uri description warns that missing recipes are not flagged, but there is little on when not to use an operation (12 of 20). Enums for type, diet, health, cuisineType, mealType, dishType, imageSize, co2EmissionsClass and 31 field names, required flags, a 1 to 20 bound on uris, and the MCP arguments are required lists and strings (14 of 15). Examples on the docs page, an `Errors` schema of errorCode, message and params, but no example error body and no code list (9 of 15). v2 in the path and retired versions marked, but no changelog and a Shopping List V1 end date with no year (6 of 15). 25 + 0 + 12 + 14 + 9 + 6 = 66.\n\n### Agent ergonomics: Edamam +9\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- Edamam (71): `field` selects any of 31 response fields, results a call are capped by plan at 100 or 1,000, and the MCP server lists two compact tools (22 of 25). `_links.next` paging with diet, health, cuisine, dish, meal, time, calorie and about 40 nutrient range filters (20 of 20). An error schema with errorCode, message and params, but the codes are not enumerated (10 of 20). Every recipe operation is a read and safe to repeat; the shopping-list POST aggregates quantities and stores nothing; the MCP tools' annotations were not read (12 of 20). `type` and `q` are the only required search parameters, with no official SDK in any language (7 of 15). 22 + 20 + 10 + 12 + 7 = 71.\n\n## Score by category\n\n| Category | Weight | Eat This Much Partner API | Edamam | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 23 | 30 | Edamam +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 66 | Eat This Much Partner API +9 |\n| Agent ergonomics | 13% (16.2 this run) | 62 | 71 | Edamam +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 30 | Eat This Much Partner API +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 25 | Edamam +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 58 | 33 | Eat This Much Partner API +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 31 | Eat This Much Partner API +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.7 · E** | **42.2 · E** | |\n\n## Facts side by side\n\n| Fact | Eat This Much Partner API | Edamam |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Eat This Much, Inc. | Edamam |\n| Hosted endpoint | no (local only) | `https://mcp.edamam.com/mcp/food` |\n| Transports | | Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| Price for cooking recipes | not published | $9 per month (plan) |\n| x402 | no | no |\n| Licence | Proprietary service under a partner contract; the website terms cover the consumer service | none |\n| Tools exposed | 0 | 2 |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-10-15 | none |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | 2020-12-03 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\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**Edamam.** Recipe search with 36 health labels, nutrient range filters and field selection, documented in a public OpenAPI file, with a two-tool hosted MCP server for food nutrition and images. Web recipes carry no instructions, every plan is prepaid with human-only requests and tight caching rules, and the terms, privacy policy and any status page could not be read.\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### Edamam\n\n1. Send `app_id` and `app_key` as HTTP Basic or, for the MCP server, as `Authorization: Bearer \u003capp_id\u003e:\u003capp_key\u003e`, rather than in the query string\n2. Expect no instructions on web recipes; return the `url` of the source to the person, and ask for the Plus plan's Edamam-owned set when steps are needed\n3. Pass `field` to pick the response fields you need and follow `_links.next.href` for the next page; `type=public` is required on every search\n4. Keep each call tied to a person's request and cache only the fields the plan allows, since the plan pages forbid automated collection and end access without refund\n5. Show the 'Powered by Edamam' attribution with every result, as every plan requires\n\n## Questions\n\n### Which is better for AI agents, Eat This Much Partner API or Edamam?\n\nEat This Much Partner API scores 45.7 (E) on agent readiness against Edamam's 42.2 (E), and leads in 4 of 7 scored categories. Edamam leads on reliability, agent ergonomics and payments \u0026 pricing.\n\n### Do Eat This Much Partner API and Edamam need an API key?\n\nBoth need an API key.\n\n### Can an agent call Eat This Much Partner API and Edamam without installing anything?\n\nNo hosted endpoint is listed for Eat This Much Partner API. Edamam has a hosted endpoint at https://mcp.edamam.com/mcp/food.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-this-much\", \"b\": \"edamam\"}`. From a terminal: `anchor compare eat-this-much edamam`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-this-much.json and https://www.anchorterminal.com/api/v1/tools/edamam.json\n\n## Other comparisons with Eat This Much Partner API or Edamam\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- [Edamam vs Nutritionix API](https://www.anchorterminal.com/compare/edamam-vs-nutritionix.md)\n- [Edamam vs fatsecret Platform API](https://www.anchorterminal.com/compare/edamam-vs-fatsecret.md)\n- [Edamam vs LogMeal](https://www.anchorterminal.com/compare/edamam-vs-logmeal.md)\n- [Edamam vs spoonacular](https://www.anchorterminal.com/compare/edamam-vs-spoonacular.md)\n- [Eat This Much Partner API vs LogMeal](https://www.anchorterminal.com/compare/eat-this-much-vs-logmeal.md)\n- [Eat This Much Partner API vs spoonacular](https://www.anchorterminal.com/compare/eat-this-much-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 Edamam", "url": "" } ], "description": "Eat This Much Partner scores 45.7 (E) to Edamam's 42.2 (E) for cooking recipes. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Eat This Much Partner API E 45.7", "Edamam E 42.2", "scores" ], "h1": "Eat This Much Partner API vs Edamam", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/eat-this-much-vs-edamam", "published": "2026-10-01", "section": "tools", "title": "Eat This Much Partner vs Edamam for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-edamam" }, "tokens": { "markdown": 4200, "slim": 2680 }, "version": 1 }