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