{ "data": { "similar": [ { "grade": "D", "json": "https://www.anchorterminal.com/tools/logmeal.json", "name": "LogMeal", "score": 49.1, "shared": [ "cooking.food-recognition", "cooking.nutrition", "cooking.recipes", "cooking.grocery" ], "slug": "logmeal" }, { "grade": "D", "json": "https://www.anchorterminal.com/tools/spoonacular.json", "name": "spoonacular", "score": 49, "shared": [ "cooking.recipes", "cooking.nutrition", "cooking.grocery", "cooking.food-recognition" ], "slug": "spoonacular" }, { "grade": "E", "json": "https://www.anchorterminal.com/tools/fatsecret.json", "name": "fatsecret Platform API", "score": 42, "shared": [ "cooking.nutrition", "cooking.recipes", "cooking.food-recognition", "cooking.grocery" ], "slug": "fatsecret" }, { "grade": "E", "json": "https://www.anchorterminal.com/tools/eat-this-much.json", "name": "Eat This Much Partner API", "score": 45.7, "shared": [ "cooking.grocery", "cooking.nutrition", "cooking.recipes" ], "slug": "eat-this-much" }, { "grade": "F", "json": "https://www.anchorterminal.com/tools/nutritionix.json", "name": "Nutritionix API", "score": 33.6, "shared": [ "cooking.nutrition", "cooking.grocery" ], "slug": "nutritionix" }, { "grade": "D", "json": "https://www.anchorterminal.com/tools/instacart.json", "name": "Instacart Developer Platform API + MCP", "score": 48.5, "shared": [ "cooking.grocery" ], "slug": "instacart" } ], "tool": { "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 30, "points": 6, "reason": "Read with the hosted lines. No status page was found on the developer portal, the docs, the OpenAPI documents or the MCP page, and a search found none (0), so there is no incident history to read (5). Per-minute throttles and monthly call allowances are published for every plan, 10, 100 and 300 a minute on Recipe Search and 50 to 1,200 on the Food Database (15). No 429, Retry-After or backoff guidance was found; the OpenAPI file lists only 400, 403 and 404 (0 of 15). No SLA was found (0). The v2 APIs are generally available, with beta marked on individual fields (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 66, "points": 10.73, "reason": "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.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 71, "points": 11.54, "reason": "`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.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 30, "points": 5.25, "reason": "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.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 25, "points": 3.13, "reason": "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.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 33, "points": 2.89, "reason": "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.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 31, "points": 2.71, "note": "editorial 14, provenance 47", "reason": "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.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "low", "notes": { "ergonomics": "`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.", "maintenance": "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.", "payments": "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.", "reliability": "Read with the hosted lines. No status page was found on the developer portal, the docs, the OpenAPI documents or the MCP page, and a search found none (0), so there is no incident history to read (5). Per-minute throttles and monthly call allowances are published for every plan, 10, 100 and 300 a minute on Recipe Search and 50 to 1,200 on the Food Database (15). No 429, Retry-After or backoff guidance was found; the OpenAPI file lists only 400, 403 and 404 (0 of 15). No SLA was found (0). The v2 APIs are generally available, with beta marked on individual fields (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.", "schema": "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.", "security": "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.", "transparency": "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." }, "sources": [ { "what": "Recipe Search API plans and rules", "url": "https://developer.edamam.com/edamam-recipe-api", "seen": "2026-11-03" }, { "what": "Recipe Search API docs", "url": "https://developer.edamam.com/edamam-docs-recipe-api", "seen": "2026-11-03" }, { "what": "Recipe Search OpenAPI 3.0.3", "url": "https://api.edamam.com/doc/open-api/recipe-search-v2.yaml", "seen": "2026-11-03" }, { "what": "Food Database API plans", "url": "https://developer.edamam.com/food-database-api", "seen": "2026-11-03" }, { "what": "Food Database API docs (OpenAPI link)", "url": "https://developer.edamam.com/food-database-api-docs", "seen": "2026-11-03" }, { "what": "Nutrition Analysis API plans", "url": "https://developer.edamam.com/edamam-nutrition-api", "seen": "2026-11-03" }, { "what": "Food MCP page", "url": "https://developer.edamam.com/mcp-edamam-food", "seen": "2026-11-03" }, { "what": "attribution guidelines", "url": "https://developer.edamam.com/attribution", "seen": "2026-11-03" }, { "what": "API terms of use (script shell, unread)", "url": "https://developer.edamam.com/about/terms", "seen": "2026-11-03" }, { "what": "privacy policy (unread)", "url": "https://developer.edamam.com/about/privacy", "seen": "2026-11-03" }, { "what": "about page (403)", "url": "https://www.edamam.com/about/", "seen": "2026-11-03" }, { "what": "robots.txt www", "url": "https://www.edamam.com/robots.txt", "seen": "2026-11-03" }, { "what": "robots.txt developer", "url": "https://developer.edamam.com/robots.txt", "seen": "2026-11-03" }, { "what": "security.txt (404)", "url": "https://developer.edamam.com/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "npm mcp-remote version dates", "url": "https://registry.npmjs.org/mcp-remote", "seen": "2026-11-03" }, { "what": "MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=edamam", "seen": "2026-11-03" }, { "what": "RDAP for edamam.com", "url": "https://rdap.verisign.com/com/v1/domain/edamam.com", "seen": "2026-11-03" } ], "openQuestions": [ "unchecked: the API terms of use and privacy policy, which render through script and gave our reader an empty document on 3 November 2026; and www.edamam.com/about, which answered 403. Transparency scores them as absent and the legal entity is not established.", "unchecked: whether trials need a card, the error code list, the MCP tools' annotations and the live tools/list, which needs credentials.", "firstReleased is 4 April 2011, the domain's registration date, since no first-hand page about the APIs carries a date. lastRelease is empty; the only dated signal is the MCP page's pin of mcp-remote 0.14.3, published on 21 September 2026.", "Judgement call on the surface. Graded on Recipe Search v2, the API the audit named and the one with a public OpenAPI file, with the Food Database, Nutrition Analysis and the hosted Food MCP noted. The MCP server exposes Food Database tools only.", "The plan pages say all plans allow only human, end-user-driven requests. Whether an agent acting for a person counts was not established; recorded as a term, not a deduction.", "The official MCP registry lists io.github.pipeworx-io/edamam (0.2.1 on 1 November 2026), a third-party server, and nothing from the vendor.", "The recipe docs page spells the health value 'pecatarian'; the OpenAPI enum has 'pescatarian'." ] }, "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 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "E", "kind": "listed", "method": "0.7", "score": 42.2 } ] }, "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" }, "notable": [ "Public OpenAPI 3.0.3 document for Recipe Search v2 (info version 2.9) with four operations, `app_id` and `app_key` as query parameters or HTTP Basic, and an `Errors` schema of errorCode, message and params; a second document covers the Food Database (https://api.edamam.com/doc/open-api/recipe-search-v2.yaml)", "Recipe search takes a `field` parameter choosing among 31 response fields, 36 health labels, 6 diet labels, about 40 nutrient range filters and `co2EmissionsClass` A+ to G (beta), with `_links.next` for the next page (https://api.edamam.com/doc/open-api/recipe-search-v2.yaml)", "Web recipes (about 2 million) come with a source url and no cooking instructions, since Edamam does not hold their licence; the Plus plan's 20,000 Edamam-owned recipes include instructions (https://developer.edamam.com/edamam-recipe-api)", "Every plan allows only human, end-user-driven requests; the plan pages say automated or programmatic collection is prohibited and access is stopped without refund, and caching is limited to a few fields inside a password-protected end-user account (https://developer.edamam.com/edamam-recipe-api)", "Attribution with the 'Powered by Edamam' badge is required on all plans; missing attribution is called a breach of contract followed by suspension (https://developer.edamam.com/attribution)", "Hosted Food MCP server at https://mcp.edamam.com/mcp/food, Streamable HTTP, two tools (get_food_nutrition for text or barcode queries, analyze_food_image for a url or base64 image), included with Food Database plans, discovery without a key and tool calls with the app's credentials; its page pins mcp-remote 0.14.3, a version npm published on 21 September 2026 (https://developer.edamam.com/mcp-edamam-food)", "The API terms of use and privacy policy pages on developer.edamam.com render through script and gave our reader an empty document; www.edamam.com/about answered 403 (checked 2026-11-03)" ], "area": "everyday", "details": [ { "label": "Surface listed", "value": "The Recipe Search API v2 at api.edamam.com, read from developer.edamam.com (Recipe Search, Food Database and Nutrition Analysis plan pages, the recipe docs, the attribution page and the Food MCP page) and the two OpenAPI documents on 3 November 2026, with the hosted Food MCP server noted. No account was made and no call or MCP session was opened" }, { "label": "Recipe Search endpoints", "value": "GET /api/recipes/v2 (search), GET /api/recipes/v2/by-uri (1 to 20 uris), GET /api/recipes/v2/{id}, POST /api/shopping-list/v2 (aggregates ingredient quantities for recipe entries, with a beta shopping-cart link)" }, { "label": "Other APIs", "value": "Food Database v2 (parser, nutrients, UPC lookup, autocomplete, Vision image analysis; OpenAPI at api.edamam.com/doc/open-api/food-db-v2.yaml) and Nutrition Analysis (recipe and text analysis, Site Parser for schema.org recipe pages). A Recipe Content Management API feeds the Plus plan's owned recipes" }, { "label": "Food MCP", "value": "https://mcp.edamam.com/mcp/food, Streamable HTTP; tools get_food_nutrition (queries, a list of phrases or UPC codes) and analyze_food_image (a public image url or data uri). Autocomplete and browse filters are out of scope. Stdio clients bridge through mcp-remote pinned at 0.14.3" }, { "label": "Filters", "value": "diet (6 values), health (36, from alcohol-free and celery-free to vegan and wheat-free), cuisineType (20), mealType (5), dishType (16), imageSize (4), co2EmissionsClass (A+ to G, beta), ingredient count, time, calories, glycaemic and inflammatory index ranges, and about 40 nutrient ranges" }, { "label": "Plan limits", "value": "Recipe Search Basic 10,000 calls a month at 10 a minute with 100 results a call; Core 500,000 at 100 a minute with 1,000 results; Plus 1,000,000 at 300 a minute. Food Database Basic 100,000 calls at 50 a minute, Core 750,000 at 100, Plus 5,000,000 at 300" }, { "label": "Caching", "value": "Basic may cache recipe id and name; Core and Plus add protein, net carbs, total fat and kcal; only inside an end user's password-protected account and only while a plan is active. Full caching is an add-on by contact" }, { "label": "Attribution", "value": "The 'Powered by Edamam' badge (four colour versions) placed where the data appears, through a script tag and an edamam-badge div, or an image in mobile apps. Not providing attribution is called a breach of contract" }, { "label": "Retired versions", "value": "The Diet API and Nutrition v1 docs pages are marked '(Version Retired)'. The recipe docs say Shopping List V1 support ends on June 30 without naming the year" }, { "label": "Legal entity", "value": "Not established. The terms and privacy pages could not be read and the plan pages name only Edamam" } ], "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, "checks": [ { "check": "Legal entity named", "value": "not found", "points": 0, "max": 20, "state": "no" }, { "check": "Domain age", "value": "edamam.com, registered 2011-04-04 (15 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "mcp.edamam.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "not researched yet", "points": 0, "max": 0, "state": "na" }, { "check": "Support route", "value": "help pages", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://developer.edamam.com/about/terms", "state": "unreadable", "reason": "the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere", "readAt": "2026-11-03", "points": 7, "max": 10 }, { "kind": "privacy", "url": "https://developer.edamam.com/about/privacy", "state": "unreadable", "reason": "the page answered HTTP 404 to our reader", "readAt": "2026-11-03", "points": 7, "max": 10 } ] }, "humans": { "slug": "edamam", "checked": "2026-11-03", "company": "Edamam", "peopleNote": "No first-hand page naming Edamam's founders or leadership could be read on 3 November 2026. www.edamam.com/about answered 403, developer.edamam.com/about and /about/team answered 404, and the developer portal's home, terms and privacy pages render through script and gave an empty document. Search results name Victor Penev as founder and CEO only on third-party profiles, conference bios and press, which are leads and not sources, so nobody is listed. No company LinkedIn, X or GitHub link was found on the pages that rendered. Investors were looked for on the same pages and in a search; the only figures are on aggregator profiles, which are not used.", "companySocial": {}, "support": { "urls": [ "https://developer.edamam.com/edamam-recipe-api", "https://developer.edamam.com/mcp-edamam-food" ] }, "sources": [ "https://developer.edamam.com/edamam-recipe-api", "https://developer.edamam.com/mcp-edamam-food", "https://developer.edamam.com/attribution", "https://www.edamam.com/about/", "https://developer.edamam.com/about/terms" ], "ownership": { "status": "unknown", "checked": "2026-11-03", "sources": [ "https://www.edamam.com/about/", "https://developer.edamam.com/about/terms" ] } }, "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" } }, "verify": { "accepts": "a page on edamam.com or one of its subdomains", "badgeUrl": "https://www.anchorterminal.com/badges/edamam.svg", "body": { "slug": "edamam", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/edamam", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/edamam\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/edamam.svg\" alt=\"Edamam on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Edamam on Anchor Terminal](https://www.anchorterminal.com/badges/edamam.svg)](https://www.anchorterminal.com/tools/edamam)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/edamam\"\u003eEdamam on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/edamam", "json": "https://www.anchorterminal.com/tools/edamam.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/edamam.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/edamam#pricing", "reviews": "https://www.anchorterminal.com/tools/edamam#reviews", "slim": "https://www.anchorterminal.com/tools/edamam.min.md" }, "markdown": "## Overview\n\n**Grade E · 42.2/100 · rank #1187 of 1349 · #5 in Cooking, recipes \u0026 meal planning · not agent-ready · confidence low**\n\n\n## Assessment\n\nRecipe 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Edamam (https://developer.edamam.com/) |\n| Kind | HTTP API |\n| Category | Cooking, recipes \u0026 meal planning (https://www.anchorterminal.com/categories/cooking) |\n| Transport | Streamable HTTP |\n| Endpoint | `https://mcp.edamam.com/mcp/food` |\n| Auth | API key · 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. |\n| Pricing | Paid ($9 / mo) · 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. |\n| x402 | No · 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. |\n| Licence | unknown |\n| Tools exposed | 2 |\n| Docs | https://developer.edamam.com/edamam-docs-recipe-api |\n| llms.txt | not found |\n| Surface listed | The Recipe Search API v2 at api.edamam.com, read from developer.edamam.com (Recipe Search, Food Database and Nutrition Analysis plan pages, the recipe docs, the attribution page and the Food MCP page) and the two OpenAPI documents on 3 November 2026, with the hosted Food MCP server noted. No account was made and no call or MCP session was opened |\n| Recipe Search endpoints | GET /api/recipes/v2 (search), GET /api/recipes/v2/by-uri (1 to 20 uris), GET /api/recipes/v2/{id}, POST /api/shopping-list/v2 (aggregates ingredient quantities for recipe entries, with a beta shopping-cart link) |\n| Other APIs | Food Database v2 (parser, nutrients, UPC lookup, autocomplete, Vision image analysis; OpenAPI at api.edamam.com/doc/open-api/food-db-v2.yaml) and Nutrition Analysis (recipe and text analysis, Site Parser for schema.org recipe pages). A Recipe Content Management API feeds the Plus plan's owned recipes |\n| Food MCP | https://mcp.edamam.com/mcp/food, Streamable HTTP; tools get_food_nutrition (queries, a list of phrases or UPC codes) and analyze_food_image (a public image url or data uri). Autocomplete and browse filters are out of scope. Stdio clients bridge through mcp-remote pinned at 0.14.3 |\n| Filters | diet (6 values), health (36, from alcohol-free and celery-free to vegan and wheat-free), cuisineType (20), mealType (5), dishType (16), imageSize (4), co2EmissionsClass (A+ to G, beta), ingredient count, time, calories, glycaemic and inflammatory index ranges, and about 40 nutrient ranges |\n| Plan limits | Recipe Search Basic 10,000 calls a month at 10 a minute with 100 results a call; Core 500,000 at 100 a minute with 1,000 results; Plus 1,000,000 at 300 a minute. Food Database Basic 100,000 calls at 50 a minute, Core 750,000 at 100, Plus 5,000,000 at 300 |\n| Caching | Basic may cache recipe id and name; Core and Plus add protein, net carbs, total fat and kcal; only inside an end user's password-protected account and only while a plan is active. Full caching is an add-on by contact |\n| Attribution | The 'Powered by Edamam' badge (four colour versions) placed where the data appears, through a script tag and an edamam-badge div, or an image in mobile apps. Not providing attribution is called a breach of contract |\n| Retired versions | The Diet API and Nutrition v1 docs pages are marked '(Version Retired)'. The recipe docs say Shopping List V1 support ends on June 30 without naming the year |\n| Legal entity | Not established. The terms and privacy pages could not be read and the plan pages name only Edamam |\n| Capabilities | cooking.recipes, cooking.nutrition, cooking.food-recognition, cooking.grocery |\n| Tags | hosted, paid, free-trial, api-key, openapi, mcp, remote-mcp, vision, closed-source, no-status-page |\n| JSON | https://www.anchorterminal.com/api/v1/tools/edamam.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 30 | 6.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 66 | 10.7 |\n| Agent ergonomics | 13% | 16.2 | 71 | 11.5 |\n| Security \u0026 auth | 14% | 17.5 | 30 | 5.2 |\n| Payments \u0026 pricing | 10% | 12.5 | 25 | 3.1 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 33 | 2.9 |\n| Transparency \u0026 trust (editorial 14, provenance 47) | 7% | 8.8 | 31 | 2.7 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **42.2 → E** |\n\n### Why each score\n\n- Reliability 30 (checked 2026-11-03): Read with the hosted lines. No status page was found on the developer portal, the docs, the OpenAPI documents or the MCP page, and a search found none (0), so there is no incident history to read (5). Per-minute throttles and monthly call allowances are published for every plan, 10, 100 and 300 a minute on Recipe Search and 50 to 1,200 on the Food Database (15). No 429, Retry-After or backoff guidance was found; the OpenAPI file lists only 400, 403 and 404 (0 of 15). No SLA was found (0). The v2 APIs are generally available, with beta marked on individual fields (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 66 (checked 2026-11-03): 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- Agent ergonomics 71 (checked 2026-11-03): `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- Security \u0026 auth 30 (checked 2026-11-03): 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- Payments \u0026 pricing 25 (checked 2026-11-03): 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 33 (checked 2026-11-03): 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- Transparency \u0026 trust 31 (checked 2026-11-03): 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\nFix list, everything this grade says the listing lacks, the biggest gain first (20 items). What it covers is at https://www.anchorterminal.com/fixes/edamam.md (JSON https://www.anchorterminal.com/fixes/edamam.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"edamam\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- unchecked: the API terms of use and privacy policy, which render through script and gave our reader an empty document on 3 November 2026; and www.edamam.com/about, which answered 403. Transparency scores them as absent and the legal entity is not established.\n- unchecked: whether trials need a card, the error code list, the MCP tools' annotations and the live tools/list, which needs credentials.\n- firstReleased is 4 April 2011, the domain's registration date, since no first-hand page about the APIs carries a date. lastRelease is empty; the only dated signal is the MCP page's pin of mcp-remote 0.14.3, published on 21 September 2026.\n- Judgement call on the surface. Graded on Recipe Search v2, the API the audit named and the one with a public OpenAPI file, with the Food Database, Nutrition Analysis and the hosted Food MCP noted. The MCP server exposes Food Database tools only.\n- The plan pages say all plans allow only human, end-user-driven requests. Whether an agent acting for a person counts was not established; recorded as a term, not a deduction.\n- The official MCP registry lists io.github.pipeworx-io/edamam (0.2.1 on 1 November 2026), a third-party server, and nothing from the vendor.\n- The recipe docs page spells the health value 'pecatarian'; the OpenAPI enum has 'pescatarian'.\n\n### Sources\n\n- Recipe Search API plans and rules: \u003chttps://developer.edamam.com/edamam-recipe-api\u003e (seen 2026-11-03)\n- Recipe Search API docs: \u003chttps://developer.edamam.com/edamam-docs-recipe-api\u003e (seen 2026-11-03)\n- Recipe Search OpenAPI 3.0.3: \u003chttps://api.edamam.com/doc/open-api/recipe-search-v2.yaml\u003e (seen 2026-11-03)\n- Food Database API plans: \u003chttps://developer.edamam.com/food-database-api\u003e (seen 2026-11-03)\n- Food Database API docs (OpenAPI link): \u003chttps://developer.edamam.com/food-database-api-docs\u003e (seen 2026-11-03)\n- Nutrition Analysis API plans: \u003chttps://developer.edamam.com/edamam-nutrition-api\u003e (seen 2026-11-03)\n- Food MCP page: \u003chttps://developer.edamam.com/mcp-edamam-food\u003e (seen 2026-11-03)\n- attribution guidelines: \u003chttps://developer.edamam.com/attribution\u003e (seen 2026-11-03)\n- API terms of use (script shell, unread): \u003chttps://developer.edamam.com/about/terms\u003e (seen 2026-11-03)\n- privacy policy (unread): \u003chttps://developer.edamam.com/about/privacy\u003e (seen 2026-11-03)\n- about page (403): \u003chttps://www.edamam.com/about/\u003e (seen 2026-11-03)\n- robots.txt www: \u003chttps://www.edamam.com/robots.txt\u003e (seen 2026-11-03)\n- robots.txt developer: \u003chttps://developer.edamam.com/robots.txt\u003e (seen 2026-11-03)\n- security.txt (404): \u003chttps://developer.edamam.com/.well-known/security.txt\u003e (seen 2026-11-03)\n- npm mcp-remote version dates: \u003chttps://registry.npmjs.org/mcp-remote\u003e (seen 2026-11-03)\n- MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=edamam\u003e (seen 2026-11-03)\n- RDAP for edamam.com: \u003chttps://rdap.verisign.com/com/v1/domain/edamam.com\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/edamam/history.json\n\n- 2026-11-03: graded 42.2 E (methodology 0.7)\n\n## Who's behind it (provenance 47/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | not found | 0/20 |\n| Domain age | edamam.com, registered 2011-04-04 (15 years) | 15/15 |\n| Endpoint on the vendor's domain | mcp.edamam.com | 15/15 |\n| Terms of service | published, but our reader couldn't read it | 7/10 |\n| Privacy policy | published, but our reader couldn't read it | 7/10 |\n| Status page | not found | 0/10 |\n| Changelog | not found | 0/10 |\n| security.txt | not found | 0/10 |\n| People named | not researched yet | n/a |\n| Support route | help pages | 5/5 |\n\nNo legal entity is named on any page read. The plan pages, docs and MCP page name only Edamam.\n\ndeveloper.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.\n\nwww.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.\n\nNo status page, changelog, security.txt (404) or llms.txt (404) found.\n\nRDAP gives edamam.com a registration date of 4 April 2011.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://developer.edamam.com/about/terms), read 2026-11-03. Our reader couldn't read it (the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere).\n\n\n**Privacy policy** (https://developer.edamam.com/about/privacy), read 2026-11-03. Our reader couldn't read it (the page answered HTTP 404 to our reader).\n\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- No people named yet.\n- Note: No first-hand page naming Edamam's founders or leadership could be read on 3 November 2026. www.edamam.com/about answered 403, developer.edamam.com/about and /about/team answered 404, and the developer portal's home, terms and privacy pages render through script and gave an empty document. Search results name Victor Penev as founder and CEO only on third-party profiles, conference bios and press, which are leads and not sources, so nobody is listed. No company LinkedIn, X or GitHub link was found on the pages that rendered. Investors were looked for on the same pages and in a search; the only figures are on aggregator profiles, which are not used.\n\n### Getting support\n\n- Help: https://developer.edamam.com/edamam-recipe-api\n- Help: https://developer.edamam.com/mcp-edamam-food\n- Sources: https://developer.edamam.com/edamam-recipe-api, https://developer.edamam.com/mcp-edamam-food, https://developer.edamam.com/attribution, https://www.edamam.com/about/, https://developer.edamam.com/about/terms\n\n## Live (updated 2026-11-04 19:34 UTC)\n\n- Right now: up, HTTP 405, 462 ms, checked 2026-11-04 19:34 UTC (get on `https://mcp.edamam.com/mcp/food`)\n- Uptime 24h 100.0% (43 probes) · 30 days 100.0% (43 probes) · p50 298 ms · p95 384 ms\n- security.txt: none\n- Always current: https://www.anchorterminal.com/api/v1/live/edamam.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Recipe Search Basic | $9 | per month (plan) | 10,000 calls a month, 10 a minute, web recipes, 10-day trial |\n| Recipe Search Core | $99 | per month (plan) | 500,000 calls a month, 100 a minute, up to 1,000 results a call |\n| Recipe Search Plus | $399 | per month (plan) | 1,000,000 calls a month, Edamam-owned recipes with instructions, 10-day trial |\n| Food Database Basic | $14 | per month (plan) | 100,000 calls a month, 500 Vision calls, 30-day trial, Food MCP included |\n| Food Database Core | $69 | per month (plan) | 750,000 calls a month, Vision pay as you go |\n| Vision image analysis | $0.015 | per call | On the Food Database Core plan; Plus includes 10,000 a month |\n| Nutrition Analysis Basic | $29 | per month (plan) | 2,500 recipes and 10,000 text lines a month; Core $299 |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- 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\n- `field` selection of 31 response fields and `_links.next` paging keep responses sized for a context window\n- Hosted Food MCP server with two compact tools, included with Food Database plans, reachable with the same app credentials\n- Plan prices, call allowances and per-minute limits published for every API without a login\n- Nutrition for 28 nutrients with diet and allergen labels generated by Edamam on every recipe\n\n## Weaknesses\n\n- 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- Web recipes return a source link and no cooking instructions; instructions need the $399 Plus plan's licensed set\n- Credentials travel as `app_id` and `app_key` query parameters in the documented scheme, one pair per application with no scopes\n- 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\n- No rate-limit error, 429 or Retry-After documented; the OpenAPI file lists only 400, 403 and 404\n\n\n\n## Before you call it (notes for agents)\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## Connect\n\nFirst request:\n\n```bash\ncurl -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\"\n```\n\nClaude Code:\n\n```bash\nclaude mcp add --transport http edamam-food https://mcp.edamam.com/mcp/food --header \"Authorization: Bearer \u003capp_id\u003e:\u003capp_key\u003e\"\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"edamam-food\": {\n \"headers\": {\n \"Authorization\": \"Bearer \\u003capp_id\\u003e:\\u003capp_key\\u003e\"\n },\n \"url\": \"https://mcp.edamam.com/mcp/food\"\n }\n }\n}\n```\n\nThrough letme: https://letme.dev/edamam. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| LogMeal | D | 49.1 | 1045 | cooking.food-recognition, cooking.nutrition, cooking.recipes, cooking.grocery | no | https://www.anchorterminal.com/tools/logmeal.md |\n| spoonacular | D | 49 | 1048 | cooking.recipes, cooking.nutrition, cooking.grocery, cooking.food-recognition | no | https://www.anchorterminal.com/tools/spoonacular.md |\n| fatsecret Platform API | E | 42 | 1193 | cooking.nutrition, cooking.recipes, cooking.food-recognition, cooking.grocery | no | https://www.anchorterminal.com/tools/fatsecret.md |\n| Eat This Much Partner API | E | 45.7 | 1129 | cooking.grocery, cooking.nutrition, cooking.recipes | no | https://www.anchorterminal.com/tools/eat-this-much.md |\n| Nutritionix API | F | 33.6 | 1259 | cooking.nutrition, cooking.grocery | no | https://www.anchorterminal.com/tools/nutritionix.md |\n| Instacart Developer Platform API + MCP | D | 48.5 | 1067 | cooking.grocery | no | https://www.anchorterminal.com/tools/instacart.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- Public OpenAPI 3.0.3 document for Recipe Search v2 (info version 2.9) with four operations, `app_id` and `app_key` as query parameters or HTTP Basic, and an `Errors` schema of errorCode, message and params; a second document covers the Food Database (source: \u003chttps://api.edamam.com/doc/open-api/recipe-search-v2.yaml\u003e)\n- Recipe search takes a `field` parameter choosing among 31 response fields, 36 health labels, 6 diet labels, about 40 nutrient range filters and `co2EmissionsClass` A+ to G (beta), with `_links.next` for the next page (source: \u003chttps://api.edamam.com/doc/open-api/recipe-search-v2.yaml\u003e)\n- Web recipes (about 2 million) come with a source url and no cooking instructions, since Edamam does not hold their licence; the Plus plan's 20,000 Edamam-owned recipes include instructions (source: \u003chttps://developer.edamam.com/edamam-recipe-api\u003e)\n- Every plan allows only human, end-user-driven requests; the plan pages say automated or programmatic collection is prohibited and access is stopped without refund, and caching is limited to a few fields inside a password-protected end-user account (source: \u003chttps://developer.edamam.com/edamam-recipe-api\u003e)\n- Attribution with the 'Powered by Edamam' badge is required on all plans; missing attribution is called a breach of contract followed by suspension (source: \u003chttps://developer.edamam.com/attribution\u003e)\n- Hosted Food MCP server at https://mcp.edamam.com/mcp/food, Streamable HTTP, two tools (get_food_nutrition for text or barcode queries, analyze_food_image for a url or base64 image), included with Food Database plans, discovery without a key and tool calls with the app's credentials; its page pins mcp-remote 0.14.3, a version npm published on 21 September 2026 (source: \u003chttps://developer.edamam.com/mcp-edamam-food\u003e)\n- The API terms of use and privacy policy pages on developer.edamam.com render through script and gave our reader an empty document; www.edamam.com/about answered 403 (checked 2026-11-03)\n\n- #5 of 8 in 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## Compare\n\n- [Edamam vs Nutritionix API](https://www.anchorterminal.com/compare/edamam-vs-nutritionix.md): E 42.2 vs F 33.6\n- [Eat This Much Partner API vs Edamam](https://www.anchorterminal.com/compare/eat-this-much-vs-edamam.md): E 45.7 vs E 42.2\n- [Edamam vs fatsecret Platform API](https://www.anchorterminal.com/compare/edamam-vs-fatsecret.md): E 42.2 vs E 42\n- [Edamam vs LogMeal](https://www.anchorterminal.com/compare/edamam-vs-logmeal.md): E 42.2 vs D 49.1\n- [Edamam vs spoonacular](https://www.anchorterminal.com/compare/edamam-vs-spoonacular.md): E 42.2 vs D 49\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on edamam.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"edamam\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/edamam\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/edamam.svg\" alt=\"Edamam on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Edamam on Anchor Terminal](https://www.anchorterminal.com/badges/edamam.svg)](https://www.anchorterminal.com/tools/edamam)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/edamam\"\u003eEdamam on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Edamam is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/edamam-dark.png\n- Light: https://www.anchorterminal.com/assets/share/edamam-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Cooking, recipes \u0026 meal planning", "url": "https://www.anchorterminal.com/categories/cooking" }, { "name": "Edamam", "url": "" } ], "description": "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.", "facts": [ "rank #1187 of 1349", "API key auth", "0 desk reviews" ], "h1": "Edamam", "image": "https://www.anchorterminal.com/assets/og/tools-edamam.png", "path": "/tools/edamam", "published": "2026-10-01", "section": "tools", "title": "Edamam review (2026): pricing, alternatives and grade E", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/edamam" }, "tokens": { "markdown": 7300, "slim": 1980 }, "version": 1 }