{ "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": "spoonacular scores 49 (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 schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "spoonacular", "name": "spoonacular", "vendor": "skycraft GmbH", "vendorUrl": "https://spoonacular.com/food-api", "kind": "http-api", "category": "cooking", "summary": "spoonacular is a recipe and food REST API from skycraft GmbH in Dresden. It searches recipes by ingredients, diet and nutrients, analyses recipes and grocery products, builds meal plans and shopping lists, and has a small open-source MCP server.", "url": "https://www.anchorterminal.com/tools/spoonacular", "markdownUrl": "https://www.anchorterminal.com/tools/spoonacular.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/spoonacular.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/spoonacular.json", "dns": "spoonacular.grade.anchorterminal.com", "repo": "https://github.com/ddsky/spoonacular-mcp", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "spoonacular-mcp" } ], "auth": "api-key", "authNotes": "One API key per account, minted in the console after a browser signup. The docs send it as the `apiKey` query parameter on every request, or as an `x-api-key` header since December 2022. No scopes, expiry or rotation procedure found. Writes to a user's meal plan need a per-user `username` and `hash` pair from the connect-user endpoint.", "pricing": "freemium", "pricingNotes": "Free plan of 50 points a day with no card, then HTTP 402 until the quota resets at midnight UTC. Cook $29 a month for 1,500 points a day (overage $0.005 a point), Culinarian $79 for 4,500 ($0.004), Chef $149 for 10,000 ($0.002), Enterprise from $300. A request costs 1 point plus 0.01 a result, with exceptions listed per endpoint. Academic and hackathon plan $10 a month through RapidAPI.", "priceSummary": "$29 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, pricing page, OpenAPI spec or MCP source (checked 2026-11-03). An exhausted daily quota answers HTTP 402 with no payment requirements; subscriptions are bought in the console through Stripe.", "endpoints": [] }, "toolCount": 6, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://spoonacular.com/food-api/docs", "openapi": "https://raw.githubusercontent.com/ddsky/spoonacular-api-clients/refs/heads/master/spoonacular-openapi-3.json", "capabilities": [ "cooking.recipes", "cooking.nutrition", "cooking.meal-plans", "cooking.pantry", "cooking.grocery", "cooking.food-recognition" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "api-key", "openapi", "mcp", "typescript", "python", "java", "go", "eu", "closed-source" ], "lastRelease": "2026-02-01", "graded": true, "anchor": { "graded": true, "score": 49, "grade": "D", "agentReady": false, "rank": 1048, "ranked": true, "rankOf": 1349, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 22, "payments": 40, "reliability": 58, "schema": 65, "security": 20, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "A broad recipe, ingredient, product and meal-plan API with a public OpenAPI document, 24 generated SDKs and a free 50-point day with no card. One key per account travels in the query string by default, the status page showed no data to our reader, and the terms allow caching for an hour at most.", "bestFor": "Agents that need recipe search with diet and nutrient filters, ingredient substitutions and nutrition, and meal plans or shopping lists written to a connected user.", "strengths": [ "Public OpenAPI 3.0 document with 97 paths, and generated SDKs in 24 languages under MIT", "Free plan of 50 points a day with no card, with public plan prices and per-point overage rates", "Quota and rate limits published with numbers, reported in three response headers on every call", "Meal plans, shopping lists and custom foods can be written back through the API for a connected user", "Open-source six-tool MCP server on npm, each tool with a typed JSON Schema and few required fields" ], "weaknesses": [ "One all-powerful key per account, documented in the `apiKey` query parameter and sent that way by the MCP server", "status.spoonacular.com answered with a data error and no history on 3 November 2026, and no incident record could be read", "No security.txt, disclosure policy or certification found, and the privacy policy's last revision is dated 2023", "The newest dated change is February 2026, and the MCP server has had one release, in August 2025", "Terms allow caching user-requested data for one hour only, with written permission, and forbid storing ingredients, instructions and nutrition" ], "agentNotes": [ "Send the key as the `x-api-key` header rather than `apiKey=` in the URL, and keep `number` small, since every result adds 0.01 points to the call's cost", "Read `X-API-Quota-Left` on each response; a 402 means the day's points are gone until midnight UTC and a 429 means the plan's requests-per-second limit, with no Retry-After to wait on", "Use `/recipes/complexSearch` with `addRecipeInformation=true` for one call instead of a search followed by one information call per recipe", "Do not store ingredients, instructions or nutrition between sessions; the terms allow only recipe ids, titles and image urls to be kept", "Show the original recipe source and a link to it with every recipe, as the terms require" ], "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 } ], "editorialScores": { "ergonomics": 68, "maintenance": 22, "payments": 40, "reliability": 58, "schema": 65, "security": 20, "transparency": 38 }, "provenanceScore": 83, "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": { "install": "npm install -g spoonacular-mcp", "http": "curl -H \"x-api-key: $SPOONACULAR_API_KEY\" \"https://api.spoonacular.com/recipes/complexSearch?query=pasta\u0026number=5\"", "config": { "mcpServers": { "spoonacular": { "command": "spoonacular-mcp", "env": { "SPOONACULAR_API_KEY": "your_api_key_here" } } } } }, "letme": { "capability": "https://letme.dev/cooking.recipes", "tool": "https://letme.dev/spoonacular" }, "area": "everyday", "unitPrices": [ { "item": "Cook plan", "unit": "month", "usd": 29, "note": "1,500 points a day, 5 requests a second" }, { "item": "Culinarian plan", "unit": "month", "usd": 79, "note": "4,500 points a day, 10 requests a second" }, { "item": "Chef plan", "unit": "month", "usd": 149, "note": "10,000 points a day, 20 requests a second" }, { "item": "Overage point on Cook", "unit": "credit", "usd": 0.005, "note": "$0.004 on Culinarian, $0.002 on Chef; a request is usually 1 point plus 0.01 a result" }, { "item": "Academic or hackathon plan", "unit": "month", "usd": 10, "note": "Through RapidAPI, up to 5,000 requests a day, manual approval" } ], "provenance": { "legalEntity": "skycraft GmbH", "domain": "spoonacular.com", "domainRegistered": "2012-12-26", "endpointOnVendorDomain": true, "terms": "https://spoonacular.com/food-api/terms", "privacy": "https://spoonacular.com/food-api/privacy", "statusPage": "https://status.spoonacular.com/", "changelog": "https://spoonacular.com/food-api/updates", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "skycraft GmbH is named only in the imprint at spoonacular.com/contact, with Dr. David Urbansky as CEO. The terms (last updated 16 April 2026) choose the law and courts of Dresden and name no entity. The privacy policy's last revision is written 10/9/2023.", "The terms forbid scraping the API and storing its data beyond recipe ids, titles and image urls. They do not address automated reading of the website. spoonacular.com/robots.txt disallows /l/ for all crawlers and disallows the whole site for a list of named download tools and crawlers (including GoogleBot and a client named WebFetch); ClaudeBot and anthropic-ai are not named. Only pages outside /l/ were read.", "status.spoonacular.com is an UptimeRobot page that answered 'There was an error while fetching the data' on 3 November 2026, with no components, history or uptime figures rendered.", "RDAP gives spoonacular.com a registration date of 26 December 2012.", "/.well-known/security.txt returns 404. No llms.txt (404)." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/spoonacular.json", "live": { "slug": "spoonacular", "vendorStatus": { "page": "https://status.spoonacular.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:36.661395014Z" }, "securityTxt": { "url": "https://spoonacular.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:00.134240883Z" }, "updatedAt": "2026-11-04T15:53:00.134240883Z" } }, "edges": [ { "by": 40, "category": "payments", "leads": "spoonacular", "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). Plan prices and per-point overage rates ($0.005, $0.004 and $0.002) are public, with the point cost of every endpoint (20). The Free plan gives 50 points a day with no card (20). A person signs up in the console in a browser, and no key API exists (0 of 20). 0 + 20 + 20 + 0 = 40." }, "scores": { "a": 0, "b": 40 } }, { "by": 36, "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 newest dated change on the updates page is February 2026 (Nutrition by Photo, recipe extraction from video), more than 180 days before 3 November 2026, and the SDK repository's last push is 2 December 2025 (0 of 30). No dated changes in the last 90 days (0 of 20). Updates page, Discord, contact form and paid support from $99 a month; three open issues on the clients repository could not be read (8 of 15). Generated SDKs in 24 languages, last pushed December 2025, and an npm MCP server, but no vendor entry in the official MCP registry, which lists only third-party spoonacular servers (10 of 15). spoonacular-mcp has one release (1.0.0, 4 August 2025), a test script and no CI (4 of 10). 0 + 0 + 8 + 10 + 4 = 22." }, "scores": { "a": 58, "b": 22 } }, { "by": 35, "category": "reliability", "leads": "spoonacular", "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. A status page exists at status.spoonacular.com (UptimeRobot), but on 3 November 2026 it rendered 'There was an error while fetching the data' with no components or history, so half credit (10 of 20) and no readable incident record (5). Daily point quotas and requests-per-second limits are published by plan, 60 a minute on Free and 5, 10 and 20 a second on Cook, Culinarian and Chef (15). HTTP 429 and 402 are documented with three quota headers, but there is no Retry-After, backoff guidance or idempotency key for the meal-plan writes (8 of 15). The pricing page states 99 per cent uptime on Cook and Culinarian and 99.9 per cent on Chef, and the FAQ says SLAs are sold above $250 a month (10). The API is generally available (10). 10 + 5 + 15 + 8 + 10 + 10 = 58." }, "scores": { "a": 23, "b": 58 } }, { "by": 28, "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 key per account with no scopes, expiry or rotation procedure, documented first as the `apiKey` query parameter and also sent in the query string by the MCP server; the `x-api-key` header is the alternative. One all-powerful key (10) less 10 for the documented query string (0 of 30). The data endpoints are read-only and a user's meal plan is written only with that user's `username` and `hash`, but there is no read-only key mode or confirmation step (10 of 20). Recipe text, instructions and extracted pages come from third-party websites and no guidance on treating them as untrusted was found (5 of 15). The console shows quota use and the headers report it per call, but no request log was found (5 of 15). security.txt returns 404 and no disclosure policy, bug bounty or certification was found (0 of 20). 0 + 10 + 5 + 5 + 0 = 20." }, "scores": { "a": 48, "b": 20 } }, { "by": 10, "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.0 document (info version 2.0.2, 97 paths, 99 operations) in the vendor's spoonacular-api-clients repository, linked from the SDK page, and the MCP server's six tools carry JSON Schema inputs (25). No llms.txt (404) and no Markdown docs (0 of 10). Each endpoint states its purpose and point cost, with little on when not to use it (12 of 20). Parameters are typed with required flags, `number` is bounded, but diet, cuisine, intolerance and meal-type values sit in prose lists rather than enums (9 of 15). Request and response examples on every endpoint, 402 and 429 documented in the quota text, but the OpenAPI document lists only 200, 401, 403 and 404 and no error body shape (9 of 15). No version in the path; a dated updates page by month back to February 2020 records field removals with notice, the last in December 2022 for 30 June 2023 (10 of 15). 25 + 0 + 12 + 9 + 9 + 10 = 65." }, "scores": { "a": 75, "b": 65 } }, { "by": 6, "category": "ergonomics", "leads": "spoonacular", "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": "`number` caps results on every search (1 to 100), `addRecipeInformation`, `fillIngredients` and `includeNutrition` switch sections on, and the MCP server lists six compact tools, but there is no field selection and full recipe objects are large (15 of 25). Offset and number pagination with filters by cuisine, diet, intolerances, nutrient ranges, equipment, time and sort keys (18 of 20). 402 and 429 are documented with quota headers, other errors are not, and no error body is shown (10 of 20). Reads are GET and safe to repeat, writes to meal plans and custom foods have no idempotency key, and the MCP tools carry no annotations (10 of 20). No required parameter on complexSearch and generated SDKs in 24 languages (15 of 15). 15 + 18 + 10 + 10 + 15 = 68." }, "scores": { "a": 62, "b": 68 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Eat This Much, Inc.", "b": "skycraft GmbH", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "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": "6", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-10-15", "b": "2026-02-01", "name": "Last release" }, { "a": "no date given", "b": "2026-04-16", "name": "Terms last updated" }, { "a": "2020-12-03", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "6 stars", "name": "Popularity" } ], "faq": [ { "answer": "spoonacular scores 49 (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 schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, Eat This Much Partner API or spoonacular?" }, { "answer": "Both need an API key.", "question": "Do Eat This Much Partner API and spoonacular need an API key?" }, { "answer": "No hosted endpoint is listed for Eat This Much Partner API. spoonacular runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Eat This Much Partner API and spoonacular without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 75 against 65", "Security \u0026 auth, 48 against 20", "Maintenance \u0026 community, 58 against 22" ], "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, 58 against 23", "Agent ergonomics, 68 against 62", "Payments \u0026 pricing, 40 against 0" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "Agents that need recipe search with diet and nutrient filters, ingredient substitutions and nutrition, and meal plans or shopping lists written to a connected user.", "slug": "spoonacular", "watchFor": "One all-powerful key per account, documented in the `apiKey` query parameter and sent that way by the MCP server" } ], "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-spoonacular.json", "title": "fatsecret Platform API vs spoonacular", "url": "https://www.anchorterminal.com/compare/fatsecret-vs-spoonacular" }, { "json": "https://www.anchorterminal.com/compare/nutritionix-vs-spoonacular.json", "title": "Nutritionix API vs spoonacular", "url": "https://www.anchorterminal.com/compare/nutritionix-vs-spoonacular" }, { "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-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/logmeal-vs-spoonacular.json", "title": "LogMeal vs spoonacular", "url": "https://www.anchorterminal.com/compare/logmeal-vs-spoonacular" } ], "panel": null, "scores": [ { "by": 35, "eat-this-much": 23, "edge": "spoonacular", "key": "reliability", "name": "Reliability", "spoonacular": 58, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "eat-this-much": 75, "edge": "eat-this-much", "key": "schema", "name": "Schema \u0026 documentation", "spoonacular": 65, "weight": 13 }, { "by": 6, "eat-this-much": 62, "edge": "spoonacular", "key": "ergonomics", "name": "Agent ergonomics", "spoonacular": 68, "weight": 13 }, { "by": 28, "eat-this-much": 48, "edge": "eat-this-much", "key": "security", "name": "Security \u0026 auth", "spoonacular": 20, "weight": 14 }, { "by": 40, "eat-this-much": 0, "edge": "spoonacular", "key": "payments", "name": "Payments \u0026 pricing", "spoonacular": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 36, "eat-this-much": 58, "edge": "eat-this-much", "key": "maintenance", "name": "Maintenance \u0026 community", "spoonacular": 22, "weight": 7 }, { "by": 0, "eat-this-much": 61, "edge": "", "key": "transparency", "name": "Transparency \u0026 trust", "spoonacular": 61, "weight": 7 } ], "summary": "spoonacular scores 49 (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 schema \u0026 documentation, security \u0026 auth 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.", "spoonacular": "A broad recipe, ingredient, product and meal-plan API with a public OpenAPI document, 24 generated SDKs and a free 50-point day with no card. One key per account travels in the query string by default, the status page showed no data to our reader, and the terms allow caching for an hour at most." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular", "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.min.md" }, "markdown": "spoonacular scores 49 (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 schema \u0026 documentation, security \u0026 auth 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- spoonacular: grade D, 49/100, rank #1048 of 1349. Markdown https://www.anchorterminal.com/tools/spoonacular.md · JSON https://www.anchorterminal.com/api/v1/tools/spoonacular.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 65\n- Security \u0026 auth, 48 against 20\n- Maintenance \u0026 community, 58 against 22\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### spoonacular (D)\n\nGood for: Agents that need recipe search with diet and nutrient filters, ingredient substitutions and nutrition, and meal plans or shopping lists written to a connected user.\n\nAhead on:\n- Reliability, 58 against 23\n- Agent ergonomics, 68 against 62\n- Payments \u0026 pricing, 40 against 0\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: One all-powerful key per account, documented in the `apiKey` query parameter and sent that way by the MCP server\n\n\n## Why the edge\n\n### Payments \u0026 pricing: spoonacular +40\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- spoonacular (40): No x402, MPP or L402 (0 of 40). Plan prices and per-point overage rates ($0.005, $0.004 and $0.002) are public, with the point cost of every endpoint (20). The Free plan gives 50 points a day with no card (20). A person signs up in the console in a browser, and no key API exists (0 of 20). 0 + 20 + 20 + 0 = 40.\n\n### Maintenance \u0026 community: Eat This Much Partner API +36\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- spoonacular (22): Read as a closed service. The newest dated change on the updates page is February 2026 (Nutrition by Photo, recipe extraction from video), more than 180 days before 3 November 2026, and the SDK repository's last push is 2 December 2025 (0 of 30). No dated changes in the last 90 days (0 of 20). Updates page, Discord, contact form and paid support from $99 a month; three open issues on the clients repository could not be read (8 of 15). Generated SDKs in 24 languages, last pushed December 2025, and an npm MCP server, but no vendor entry in the official MCP registry, which lists only third-party spoonacular servers (10 of 15). spoonacular-mcp has one release (1.0.0, 4 August 2025), a test script and no CI (4 of 10). 0 + 0 + 8 + 10 + 4 = 22.\n\n### Reliability: spoonacular +35\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- spoonacular (58): Read with the hosted lines. A status page exists at status.spoonacular.com (UptimeRobot), but on 3 November 2026 it rendered 'There was an error while fetching the data' with no components or history, so half credit (10 of 20) and no readable incident record (5). Daily point quotas and requests-per-second limits are published by plan, 60 a minute on Free and 5, 10 and 20 a second on Cook, Culinarian and Chef (15). HTTP 429 and 402 are documented with three quota headers, but there is no Retry-After, backoff guidance or idempotency key for the meal-plan writes (8 of 15). The pricing page states 99 per cent uptime on Cook and Culinarian and 99.9 per cent on Chef, and the FAQ says SLAs are sold above $250 a month (10). The API is generally available (10). 10 + 5 + 15 + 8 + 10 + 10 = 58.\n\n### Security \u0026 auth: Eat This Much Partner API +28\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- spoonacular (20): One key per account with no scopes, expiry or rotation procedure, documented first as the `apiKey` query parameter and also sent in the query string by the MCP server; the `x-api-key` header is the alternative. One all-powerful key (10) less 10 for the documented query string (0 of 30). The data endpoints are read-only and a user's meal plan is written only with that user's `username` and `hash`, but there is no read-only key mode or confirmation step (10 of 20). Recipe text, instructions and extracted pages come from third-party websites and no guidance on treating them as untrusted was found (5 of 15). The console shows quota use and the headers report it per call, but no request log was found (5 of 15). security.txt returns 404 and no disclosure policy, bug bounty or certification was found (0 of 20). 0 + 10 + 5 + 5 + 0 = 20.\n\n### Schema \u0026 documentation: Eat This Much Partner API +10\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- spoonacular (65): Public OpenAPI 3.0.0 document (info version 2.0.2, 97 paths, 99 operations) in the vendor's spoonacular-api-clients repository, linked from the SDK page, and the MCP server's six tools carry JSON Schema inputs (25). No llms.txt (404) and no Markdown docs (0 of 10). Each endpoint states its purpose and point cost, with little on when not to use it (12 of 20). Parameters are typed with required flags, `number` is bounded, but diet, cuisine, intolerance and meal-type values sit in prose lists rather than enums (9 of 15). Request and response examples on every endpoint, 402 and 429 documented in the quota text, but the OpenAPI document lists only 200, 401, 403 and 404 and no error body shape (9 of 15). No version in the path; a dated updates page by month back to February 2020 records field removals with notice, the last in December 2022 for 30 June 2023 (10 of 15). 25 + 0 + 12 + 9 + 9 + 10 = 65.\n\n### Agent ergonomics: spoonacular +6\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- spoonacular (68): `number` caps results on every search (1 to 100), `addRecipeInformation`, `fillIngredients` and `includeNutrition` switch sections on, and the MCP server lists six compact tools, but there is no field selection and full recipe objects are large (15 of 25). Offset and number pagination with filters by cuisine, diet, intolerances, nutrient ranges, equipment, time and sort keys (18 of 20). 402 and 429 are documented with quota headers, other errors are not, and no error body is shown (10 of 20). Reads are GET and safe to repeat, writes to meal plans and custom foods have no idempotency key, and the MCP tools carry no annotations (10 of 20). No required parameter on complexSearch and generated SDKs in 24 languages (15 of 15). 15 + 18 + 10 + 10 + 15 = 68.\n\n## Score by category\n\n| Category | Weight | Eat This Much Partner API | spoonacular | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 23 | 58 | spoonacular +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 65 | Eat This Much Partner API +10 |\n| Agent ergonomics | 13% (16.2 this run) | 62 | 68 | spoonacular +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 20 | Eat This Much Partner API +28 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 40 | spoonacular +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 58 | 22 | Eat This Much Partner API +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 61 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.7 · E** | **49 · D** | |\n\n## Facts side by side\n\n| Fact | Eat This Much Partner API | spoonacular |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Eat This Much, Inc. | skycraft GmbH |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | stdio |\n| Auth | API key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under a partner contract; the website terms cover the consumer service | none |\n| Tools exposed | 0 | 6 |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-10-15 | 2026-02-01 |\n| Terms last updated | no date given | 2026-04-16 |\n| Privacy policy last updated | 2020-12-03 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | none | 6 stars |\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**spoonacular.** A broad recipe, ingredient, product and meal-plan API with a public OpenAPI document, 24 generated SDKs and a free 50-point day with no card. One key per account travels in the query string by default, the status page showed no data to our reader, and the terms allow caching for an hour at most.\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### spoonacular\n\n1. Send the key as the `x-api-key` header rather than `apiKey=` in the URL, and keep `number` small, since every result adds 0.01 points to the call's cost\n2. Read `X-API-Quota-Left` on each response; a 402 means the day's points are gone until midnight UTC and a 429 means the plan's requests-per-second limit, with no Retry-After to wait on\n3. Use `/recipes/complexSearch` with `addRecipeInformation=true` for one call instead of a search followed by one information call per recipe\n4. Do not store ingredients, instructions or nutrition between sessions; the terms allow only recipe ids, titles and image urls to be kept\n5. Show the original recipe source and a link to it with every recipe, as the terms require\n\n## Questions\n\n### Which is better for AI agents, Eat This Much Partner API or spoonacular?\n\nspoonacular scores 49 (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 schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.\n\n### Do Eat This Much Partner API and spoonacular need an API key?\n\nBoth need an API key.\n\n### Can an agent call Eat This Much Partner API and spoonacular without installing anything?\n\nNo hosted endpoint is listed for Eat This Much Partner API. spoonacular runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.json, and with the fewest tokens: https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"eat-this-much\", \"b\": \"spoonacular\"}`. From a terminal: `anchor compare eat-this-much spoonacular`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/eat-this-much.json and https://www.anchorterminal.com/api/v1/tools/spoonacular.json\n\n## Other comparisons with Eat This Much Partner API or spoonacular\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 spoonacular](https://www.anchorterminal.com/compare/fatsecret-vs-spoonacular.md)\n- [Nutritionix API vs spoonacular](https://www.anchorterminal.com/compare/nutritionix-vs-spoonacular.md)\n- [Eat This Much Partner API vs Edamam](https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.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- [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 spoonacular", "url": "" } ], "description": "spoonacular scores 49 (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", "spoonacular D 49", "scores" ], "h1": "Eat This Much Partner API vs spoonacular", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/eat-this-much-vs-spoonacular", "published": "2026-10-01", "section": "tools", "title": "Eat This Much Partner vs spoonacular for AI agents (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-spoonacular" }, "tokens": { "markdown": 4250, "slim": 2680 }, "version": 1 }