{
  "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": 1178,
        "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-04T21:27:47.378873062Z",
          "lastOk": true,
          "lastStatus": 405,
          "lastMs": 259,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 298,
          "p95ms24h": 401,
          "samples24h": 62,
          "samples30d": 62,
          "days": [
            {
              "date": "2026-11-04",
              "probes": 62,
              "ok": 62
            }
          ]
        },
        "securityTxt": {
          "url": "https://edamam.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-04T15:52:51.148952618Z"
        },
        "updatedAt": "2026-11-04T21:27:47.378873062Z"
      }
    },
    "answer": "Edamam scores 42.2 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories. Nutritionix API leads on security \u0026 auth and transparency \u0026 trust.",
    "b": {
      "slug": "nutritionix",
      "name": "Nutritionix API",
      "vendor": "Syndigo LLC",
      "vendorUrl": "https://developer.nutritionix.com/",
      "kind": "http-api",
      "category": "cooking",
      "summary": "The Nutritionix API, run by Syndigo, turns free-text food and exercise descriptions into nutrition data and searches a database of grocery products, restaurant menu items and generic foods by name or UPC. Access is arranged through Syndigo's sales team.",
      "url": "https://www.anchorterminal.com/tools/nutritionix",
      "markdownUrl": "https://www.anchorterminal.com/tools/nutritionix.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nutritionix.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nutritionix.json",
      "dns": "nutritionix.grade.anchorterminal.com",
      "transports": [],
      "packages": [],
      "auth": "api-key",
      "authNotes": "An application id and key pair sent as the `x-app-id` and `x-app-key` headers on every request, with an optional `x-remote-user-id` header that counts an app's active users for billing (0 in development). Keys come from a developer.nutritionix.com account; since the free tier ended, a limited trial is granted through the sales form on www.nutritionix.com. No scopes, expiry or rotation documented.",
      "pricing": "paid",
      "pricingNotes": "No public price. developer.nutritionix.com says the open, no-cost trial that ran for over a decade has ended because of misuse, and that businesses request a limited trial through the contact form at www.nutritionix.com/business/api, after which sales follows up. The pricing page on www.nutritionix.com is closed to our reader by robots.txt. Premium parameters (claims, taxonomy, UK branded data, detailed nutrients) are sold separately through an account executive.",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the developer portal or the Syndigo docs (checked 2026-11-03). Access is contracted through sales.",
        "endpoints": []
      },
      "toolCount": 0,
      "popularity": {
        "githubStars": 192,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://docx.syndigo.com/developers/docs/nutritionix-api-guide",
      "llmsTxt": "https://docx.syndigo.com/llms.txt",
      "capabilities": [
        "cooking.nutrition",
        "cooking.grocery"
      ],
      "tags": [
        "hosted",
        "paid",
        "sales-led",
        "api-key",
        "llms-txt",
        "enterprise",
        "closed-source"
      ],
      "lastRelease": "2024-03-14",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 33.6,
        "grade": "F",
        "agentReady": false,
        "rank": 1257,
        "ranked": true,
        "rankOf": 1349,
        "categoryRank": 8,
        "methodology": "0.7",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 51,
          "maintenance": 10,
          "payments": 0,
          "reliability": 15,
          "schema": 45,
          "security": 52,
          "transparency": 57
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "low",
          "date": "2026-11-03"
        },
        "negative": 0,
        "verdict": "Free-text food logging and a branded-food and restaurant database behind four header-authenticated endpoints, documented in Markdown with an llms.txt index and backed by Syndigo's sub-processor list and disclosure programme. There is no public price or free tier since the open trial ended, no documented rate limit or 429, and the status, terms and pricing pages are closed to our reader.",
        "bestFor": "Agents that log meals from free text for a US or UK audience and need branded grocery and restaurant nutrition with UPCs, under a sales contract.",
        "strengths": [
          "POST /v2/natural/nutrients parses phrases such as '1 cup rice' into serving weights, 11 summary nutrients and a full nutrient array in one call",
          "Branded foods, restaurant menu items and UPC lookup, with brand, region and claim filters on the instant endpoint",
          "Keys travel only in headers, with a per-user header that keeps billing off the key itself",
          "Markdown docs with an llms.txt index on Syndigo's portal, with examples per endpoint",
          "Syndigo names the Nutritionix API's sub-processors with locations and runs a responsible disclosure programme on Bugcrowd"
        ],
        "weaknesses": [
          "No public free tier or published price; a limited trial is granted by sales after a form on www.nutritionix.com",
          "No rate limit figure, 429 or Retry-After documented; exceeded usage is reported as 401",
          "The status page, API terms and pricing page sit on hosts whose robots.txt disallows our reader, so none was read",
          "The API guide's last update is 14 March 2024, with no changelog and no official SDK in current maintenance",
          "Caching is limited to a user's own food log; other caching needs a paid add-on"
        ],
        "agentNotes": [
          "Do not plan on self-serve access; a person must request a trial through Syndigo's sales form, so ask for an existing app id and key before starting",
          "Send `x-app-id` and `x-app-key` as headers and set `x-remote-user-id` per end user (0 in development), since billing counts active users",
          "Treat a 401 as either a bad key or an exhausted usage limit; the docs give no limit figure, so back off before retrying",
          "Debounce instant searches by 300 ms and send at least 3 characters, then pass `food_name` to natural/nutrients for common foods and `nix_item_id` to search/item for branded ones",
          "Cache only a person's own logged results; cached data may not be shown to another user"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "F",
            "methodology": "0.7",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 33.6
          }
        ],
        "editorialScores": {
          "ergonomics": 51,
          "maintenance": 10,
          "payments": 0,
          "reliability": 15,
          "schema": 45,
          "security": 52,
          "transparency": 36
        },
        "provenanceScore": 78,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-03",
            "maintenance": "2026-11-03",
            "payments": "2026-11-03",
            "reliability": "2026-11-03",
            "schema": "2026-11-03",
            "security": "2026-11-03",
            "transparency": "2026-11-03"
          },
          "last": "2026-11-03",
          "oldest": "2026-11-03",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST https://trackapi.nutritionix.com/v2/natural/nutrients -H \"Content-Type: application/json\" -H \"x-app-id: $NUTRITIONIX_APP_ID\" -H \"x-app-key: $NUTRITIONIX_APP_KEY\" -d '{\"query\":\"1 cup rice and 2 eggs\"}'"
      },
      "letme": {
        "capability": "https://letme.dev/cooking.nutrition",
        "tool": "https://letme.dev/nutritionix"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "Syndigo LLC",
        "domain": "nutritionix.com",
        "domainRegistered": "2010-01-25",
        "endpointOnVendorDomain": true,
        "terms": "https://syndigo.com/legal/terms-of-use/",
        "privacy": "https://syndigo.com/legal/privacy-notice/",
        "statusPage": "https://status.nutritionix.com/",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-03",
        "notes": [
          "Syndigo LLC is the entity on syndigo.com's legal pages and the sub-processor list, which has a Nutritionix API section. The API's own terms are shown during signup on developer.nutritionix.com and on www.nutritionix.com, which was not read; the Syndigo terms of use linked here (last updated 22 January 2019) govern Syndigo's website and do not mention the API.",
          "www.nutritionix.com/robots.txt, trackapi.nutritionix.com/robots.txt and status.nutritionix.com/robots.txt all disallow the whole site for ClaudeBot, anthropic-ai and Claude-Web among about 30 named crawlers, and carry a Content-Signal line of search=yes,ai-train=no,use=reference for everyone else. Nothing on those hosts was read, so the pricing page, the API terms and the status page are unchecked. developer.nutritionix.com/robots.txt has only comments and docx.syndigo.com allows all; syndigo.com disallows demo and private paths only.",
          "Syndigo's privacy notice is effective 25 March 2026 and does not name Nutritionix. Syndigo's responsible disclosure notice takes reports through Bugcrowd without compensation. No security.txt on developer.nutritionix.com (404).",
          "RDAP gives nutritionix.com a registration date of 25 January 2010."
        ],
        "score": 78
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/nutritionix.json",
      "live": {
        "slug": "nutritionix",
        "vendorStatus": {
          "page": "https://status.nutritionix.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-04T21:26:18.076993209Z"
        },
        "securityTxt": {
          "url": "https://nutritionix.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-04T15:53:57.34546431Z"
        },
        "updatedAt": "2026-11-04T21:26:18.076993209Z"
      }
    },
    "edges": [
      {
        "by": 26,
        "category": "transparency",
        "leads": "nutritionix",
        "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 service whose API terms are shown at signup and on www.nutritionix.com, which could not be read; Syndigo's website terms of 2019 do not cover the API (5 of 30, unchecked). Syndigo's privacy notice, effective 25 March 2026, states deletion within 30 days once purposes end, names EU and UK representatives and a DPO, and relies on standard contractual clauses and the Data Privacy Framework, but does not name Nutritionix and gives no category-level retention periods (15 of 30). No deprecation policy or notices found (0 of 20). Sub-processors for the Nutritionix API are named with locations (Amazon Web Services, Red Hat 3scale, Cloudflare, all in the United States) in a list effective 13 April 2026 (16 of 20). 5 + 15 + 0 + 16 = 36."
        },
        "scores": {
          "a": 31,
          "b": 57
        }
      },
      {
        "by": 25,
        "category": "payments",
        "leads": "edamam",
        "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). No price is published on any page read; the pricing page on www.nutritionix.com is closed to our reader and the developer portal routes to sales (0 of 20, unchecked). The developer portal says the public free-access tier has ended and a limited trial is granted by sales (0 of 20). A person files a form and waits for a sales follow-up (0 of 20). Total 0."
        },
        "scores": {
          "a": 25,
          "b": 0
        }
      },
      {
        "by": 23,
        "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 first-hand change to the API's docs is the guide's update of 14 March 2024, more than 180 days before 3 November 2026; Syndigo's sub-processor list of 13 April 2026 and the vue-nutrition-label push of February 2026 are not API changes (0 of 30). No three dated changes in 90 days (0 of 20). Support through Syndigo's form and support@nutritionix.com for caching, no public changelog or community channel (5 of 15). No current official SDK; library-python last pushed December 2022, the label widget June 2024 (3 of 15). The organisation's packages show no CI or recent releases (2 of 10). 0 + 0 + 5 + 3 + 2 = 10."
        },
        "scores": {
          "a": 33,
          "b": 10
        }
      },
      {
        "by": 22,
        "category": "security",
        "leads": "nutritionix",
        "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": "An application id and key pair with no scopes, sent only as headers per the docs, which say not to use the query string; no expiry or rotation documented (18 of 30). The API is read-only, so nothing destructive is reachable, but there is no read-only or per-user credential (12 of 20). Food, brand and menu names come from brands and restaurants through Syndigo, with little free text and no guidance on treating it as untrusted (8 of 15). `x-remote-user-id` counts active users for billing; no request log or per-call visibility for the operator was found (2 of 15). Syndigo runs a responsible disclosure programme on Bugcrowd without compensation, holds SOC 2 Type II for named products that do not include Nutritionix, and lists the Nutritionix API's sub-processors; no security.txt (12 of 20). 18 + 12 + 8 + 2 + 12 = 52."
        },
        "scores": {
          "a": 30,
          "b": 52
        }
      },
      {
        "by": 21,
        "category": "schema",
        "leads": "edamam",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "No OpenAPI or similar document was found (0 of 25). Syndigo's docs portal serves an llms.txt index and a Markdown twin of every Nutritionix page (10). Each endpoint page states its purpose with usage guidance, such as debouncing instant searches and using the right follow-up endpoint for common and branded foods (13 of 20). Parameters are typed with defaults, but the only required column reads 'Required for Authentication', taxonomy_node_id is typed boolean while described as an id, and claims values sit in prose (8 of 15). Request and response examples on each endpoint; six error statuses with one line each and no body format (9 of 15). v2 in the path, no changelog, and the API guide last updated on 14 March 2024 (5 of 15). 0 + 10 + 13 + 8 + 9 + 5 = 45."
        },
        "scores": {
          "a": 66,
          "b": 45
        }
      },
      {
        "by": 20,
        "category": "ergonomics",
        "leads": "edamam",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "`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.",
          "b": "Instant returns at most 20 common and 20 branded items and premium `detailed_nutrients` picks up to three nutrients, but natural nutrients returns every food with a full nutrient array and there is no general field selection (12 of 25). No pagination; filters by branded, common, brand id, brand type and region (10 of 20). Six statuses with a line each, no codes in the body, and limit errors folded into 401 (7 of 20). Every endpoint is a read and safe to repeat (14 of 20). One required parameter per endpoint and sensible defaults, but no official SDK on the developer page beyond a label widget, and the organisation's Python library was last pushed in 2022 (8 of 15). 12 + 10 + 7 + 14 + 8 = 51."
        },
        "scores": {
          "a": 71,
          "b": 51
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Edamam",
        "b": "Syndigo LLC",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.edamam.com/mcp/food",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "$29 per month (plan)",
        "b": "not published",
        "name": "Price for cooking nutrition"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "2",
        "b": "0",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "none",
        "b": "2024-03-14",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "2019-01-22",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2026-03-25",
        "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": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "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": "192 stars",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Edamam scores 42.2 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories. Nutritionix API leads on security \u0026 auth and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Edamam or Nutritionix API?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do Edamam and Nutritionix API need an API key?"
      },
      {
        "answer": "Edamam has a hosted endpoint at https://mcp.edamam.com/mcp/food. No hosted endpoint is listed for Nutritionix API.",
        "question": "Can an agent call Edamam and Nutritionix API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 30 against 15",
          "Schema \u0026 documentation, 66 against 45",
          "Agent ergonomics, 71 against 51",
          "Payments \u0026 pricing, 25 against 0",
          "Maintenance \u0026 community, 33 against 10"
        ],
        "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": [
          "Security \u0026 auth, 52 against 30",
          "Transparency \u0026 trust, 57 against 31"
        ],
        "also": null,
        "goodFor": "Agents that log meals from free text for a US or UK audience and need branded grocery and restaurant nutrition with UPCs, under a sales contract.",
        "slug": "nutritionix",
        "watchFor": "No public free tier or published price; a limited trial is granted by sales after a form on www.nutritionix.com"
      }
    ],
    "history": null,
    "job": {
      "capability": "cooking.nutrition",
      "name": "Cooking nutrition"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-nutritionix.json",
        "title": "Eat This Much Partner API vs Nutritionix API",
        "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-nutritionix"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fatsecret-vs-nutritionix.json",
        "title": "fatsecret Platform API vs Nutritionix API",
        "url": "https://www.anchorterminal.com/compare/fatsecret-vs-nutritionix"
      },
      {
        "json": "https://www.anchorterminal.com/compare/logmeal-vs-nutritionix.json",
        "title": "LogMeal vs Nutritionix API",
        "url": "https://www.anchorterminal.com/compare/logmeal-vs-nutritionix"
      },
      {
        "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/edamam-vs-spoonacular.json",
        "title": "Edamam vs spoonacular",
        "url": "https://www.anchorterminal.com/compare/edamam-vs-spoonacular"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 15,
        "edamam": 30,
        "edge": "edamam",
        "key": "reliability",
        "name": "Reliability",
        "nutritionix": 15,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 21,
        "edamam": 66,
        "edge": "edamam",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "nutritionix": 45,
        "weight": 13
      },
      {
        "by": 20,
        "edamam": 71,
        "edge": "edamam",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "nutritionix": 51,
        "weight": 13
      },
      {
        "by": 22,
        "edamam": 30,
        "edge": "nutritionix",
        "key": "security",
        "name": "Security \u0026 auth",
        "nutritionix": 52,
        "weight": 14
      },
      {
        "by": 25,
        "edamam": 25,
        "edge": "edamam",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "nutritionix": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 23,
        "edamam": 33,
        "edge": "edamam",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "nutritionix": 10,
        "weight": 7
      },
      {
        "by": 26,
        "edamam": 31,
        "edge": "nutritionix",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "nutritionix": 57,
        "weight": 7
      }
    ],
    "summary": "Edamam scores 42.2 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories. Nutritionix API leads on security \u0026 auth and transparency \u0026 trust. Both do cooking nutrition.",
    "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.",
      "nutritionix": "Free-text food logging and a branded-food and restaurant database behind four header-authenticated endpoints, documented in Markdown with an llms.txt index and backed by Syndigo's sub-processor list and disclosure programme. There is no public price or free tier since the open trial ended, no documented rate limit or 429, and the status, terms and pricing pages are closed to our reader."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/edamam-vs-nutritionix",
    "json": "https://www.anchorterminal.com/compare/edamam-vs-nutritionix.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/edamam-vs-nutritionix.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/edamam-vs-nutritionix.min.md"
  },
  "markdown": "Edamam scores 42.2 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories. Nutritionix API leads on security \u0026 auth and transparency \u0026 trust. Both do cooking nutrition.\n\n- Edamam: grade E, 42.2/100, rank #1178 of 1349. Markdown https://www.anchorterminal.com/tools/edamam.md · JSON https://www.anchorterminal.com/api/v1/tools/edamam.json\n- Nutritionix API: grade F, 33.6/100, rank #1257 of 1349. Markdown https://www.anchorterminal.com/tools/nutritionix.md · JSON https://www.anchorterminal.com/api/v1/tools/nutritionix.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- Reliability, 30 against 15\n- Schema \u0026 documentation, 66 against 45\n- Agent ergonomics, 71 against 51\n- Payments \u0026 pricing, 25 against 0\n- Maintenance \u0026 community, 33 against 10\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### Nutritionix API (F)\n\nGood for: Agents that log meals from free text for a US or UK audience and need branded grocery and restaurant nutrition with UPCs, under a sales contract.\n\nAhead on:\n- Security \u0026 auth, 52 against 30\n- Transparency \u0026 trust, 57 against 31\n\nWatch for: No public free tier or published price; a limited trial is granted by sales after a form on www.nutritionix.com\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Nutritionix API +26\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- Nutritionix API (57): Closed service whose API terms are shown at signup and on www.nutritionix.com, which could not be read; Syndigo's website terms of 2019 do not cover the API (5 of 30, unchecked). Syndigo's privacy notice, effective 25 March 2026, states deletion within 30 days once purposes end, names EU and UK representatives and a DPO, and relies on standard contractual clauses and the Data Privacy Framework, but does not name Nutritionix and gives no category-level retention periods (15 of 30). No deprecation policy or notices found (0 of 20). Sub-processors for the Nutritionix API are named with locations (Amazon Web Services, Red Hat 3scale, Cloudflare, all in the United States) in a list effective 13 April 2026 (16 of 20). 5 + 15 + 0 + 16 = 36.\n\n### Payments \u0026 pricing: Edamam +25\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- Nutritionix API (0): No x402, MPP or L402 (0 of 40). No price is published on any page read; the pricing page on www.nutritionix.com is closed to our reader and the developer portal routes to sales (0 of 20, unchecked). The developer portal says the public free-access tier has ended and a limited trial is granted by sales (0 of 20). A person files a form and waits for a sales follow-up (0 of 20). Total 0.\n\n### Maintenance \u0026 community: Edamam +23\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- Nutritionix API (10): Read as a closed service. The newest dated first-hand change to the API's docs is the guide's update of 14 March 2024, more than 180 days before 3 November 2026; Syndigo's sub-processor list of 13 April 2026 and the vue-nutrition-label push of February 2026 are not API changes (0 of 30). No three dated changes in 90 days (0 of 20). Support through Syndigo's form and support@nutritionix.com for caching, no public changelog or community channel (5 of 15). No current official SDK; library-python last pushed December 2022, the label widget June 2024 (3 of 15). The organisation's packages show no CI or recent releases (2 of 10). 0 + 0 + 5 + 3 + 2 = 10.\n\n### Security \u0026 auth: Nutritionix API +22\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- Nutritionix API (52): An application id and key pair with no scopes, sent only as headers per the docs, which say not to use the query string; no expiry or rotation documented (18 of 30). The API is read-only, so nothing destructive is reachable, but there is no read-only or per-user credential (12 of 20). Food, brand and menu names come from brands and restaurants through Syndigo, with little free text and no guidance on treating it as untrusted (8 of 15). `x-remote-user-id` counts active users for billing; no request log or per-call visibility for the operator was found (2 of 15). Syndigo runs a responsible disclosure programme on Bugcrowd without compensation, holds SOC 2 Type II for named products that do not include Nutritionix, and lists the Nutritionix API's sub-processors; no security.txt (12 of 20). 18 + 12 + 8 + 2 + 12 = 52.\n\n### Schema \u0026 documentation: Edamam +21\n\n- Edamam (66): Public OpenAPI 3.0.3 documents for Recipe Search v2 (four operations) and the Food Database, and the Food MCP's two tools take typed arguments (25). No llms.txt (404) and no Markdown docs (0 of 10). Operation and parameter descriptions state purpose, and the by-uri description warns that missing recipes are not flagged, but there is little on when not to use an operation (12 of 20). Enums for type, diet, health, cuisineType, mealType, dishType, imageSize, co2EmissionsClass and 31 field names, required flags, a 1 to 20 bound on uris, and the MCP arguments are required lists and strings (14 of 15). Examples on the docs page, an `Errors` schema of errorCode, message and params, but no example error body and no code list (9 of 15). v2 in the path and retired versions marked, but no changelog and a Shopping List V1 end date with no year (6 of 15). 25 + 0 + 12 + 14 + 9 + 6 = 66.\n- Nutritionix API (45): No OpenAPI or similar document was found (0 of 25). Syndigo's docs portal serves an llms.txt index and a Markdown twin of every Nutritionix page (10). Each endpoint page states its purpose with usage guidance, such as debouncing instant searches and using the right follow-up endpoint for common and branded foods (13 of 20). Parameters are typed with defaults, but the only required column reads 'Required for Authentication', taxonomy_node_id is typed boolean while described as an id, and claims values sit in prose (8 of 15). Request and response examples on each endpoint; six error statuses with one line each and no body format (9 of 15). v2 in the path, no changelog, and the API guide last updated on 14 March 2024 (5 of 15). 0 + 10 + 13 + 8 + 9 + 5 = 45.\n\n### Agent ergonomics: Edamam +20\n\n- Edamam (71): `field` selects any of 31 response fields, results a call are capped by plan at 100 or 1,000, and the MCP server lists two compact tools (22 of 25). `_links.next` paging with diet, health, cuisine, dish, meal, time, calorie and about 40 nutrient range filters (20 of 20). An error schema with errorCode, message and params, but the codes are not enumerated (10 of 20). Every recipe operation is a read and safe to repeat; the shopping-list POST aggregates quantities and stores nothing; the MCP tools' annotations were not read (12 of 20). `type` and `q` are the only required search parameters, with no official SDK in any language (7 of 15). 22 + 20 + 10 + 12 + 7 = 71.\n- Nutritionix API (51): Instant returns at most 20 common and 20 branded items and premium `detailed_nutrients` picks up to three nutrients, but natural nutrients returns every food with a full nutrient array and there is no general field selection (12 of 25). No pagination; filters by branded, common, brand id, brand type and region (10 of 20). Six statuses with a line each, no codes in the body, and limit errors folded into 401 (7 of 20). Every endpoint is a read and safe to repeat (14 of 20). One required parameter per endpoint and sensible defaults, but no official SDK on the developer page beyond a label widget, and the organisation's Python library was last pushed in 2022 (8 of 15). 12 + 10 + 7 + 14 + 8 = 51.\n\n## Score by category\n\n| Category | Weight | Edamam | Nutritionix API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 30 | 15 | Edamam +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 45 | Edamam +21 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 51 | Edamam +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 52 | Nutritionix API +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 0 | Edamam +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 33 | 10 | Edamam +23 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 31 | 57 | Nutritionix API +26 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **42.2 · E** | **33.6 · F** | |\n\n## Facts side by side\n\n| Fact | Edamam | Nutritionix API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Edamam | Syndigo LLC |\n| Hosted endpoint | `https://mcp.edamam.com/mcp/food` | no (local only) |\n| Transports | Streamable HTTP |  |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| Price for cooking nutrition | $29 per month (plan) | not published |\n| x402 | no | no |\n| Tools exposed | 2 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2024-03-14 |\n| Terms last updated | couldn't be read | 2019-01-22 |\n| Privacy policy last updated | couldn't be read | 2026-03-25 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | none | 192 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**Nutritionix API.** Free-text food logging and a branded-food and restaurant database behind four header-authenticated endpoints, documented in Markdown with an llms.txt index and backed by Syndigo's sub-processor list and disclosure programme. There is no public price or free tier since the open trial ended, no documented rate limit or 429, and the status, terms and pricing pages are closed to our reader.\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### Nutritionix API\n\n1. Do not plan on self-serve access; a person must request a trial through Syndigo's sales form, so ask for an existing app id and key before starting\n2. Send `x-app-id` and `x-app-key` as headers and set `x-remote-user-id` per end user (0 in development), since billing counts active users\n3. Treat a 401 as either a bad key or an exhausted usage limit; the docs give no limit figure, so back off before retrying\n4. Debounce instant searches by 300 ms and send at least 3 characters, then pass `food_name` to natural/nutrients for common foods and `nix_item_id` to search/item for branded ones\n5. Cache only a person's own logged results; cached data may not be shown to another user\n\n## Questions\n\n### Which is better for AI agents, Edamam or Nutritionix API?\n\nEdamam scores 42.2 (E) on agent readiness against Nutritionix API's 33.6 (F), and leads in 5 of 7 scored categories. Nutritionix API leads on security \u0026 auth and transparency \u0026 trust.\n\n### Do Edamam and Nutritionix API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Edamam and Nutritionix API without installing anything?\n\nEdamam has a hosted endpoint at https://mcp.edamam.com/mcp/food. No hosted endpoint is listed for Nutritionix API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/edamam-vs-nutritionix.json, and with the fewest tokens: https://www.anchorterminal.com/compare/edamam-vs-nutritionix.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"edamam\", \"b\": \"nutritionix\"}`. From a terminal: `anchor compare edamam nutritionix`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/edamam.json and https://www.anchorterminal.com/api/v1/tools/nutritionix.json\n\n## Other comparisons with Edamam or Nutritionix API\n\n- [Eat This Much Partner API vs Nutritionix API](https://www.anchorterminal.com/compare/eat-this-much-vs-nutritionix.md)\n- [fatsecret Platform API vs Nutritionix API](https://www.anchorterminal.com/compare/fatsecret-vs-nutritionix.md)\n- [LogMeal vs Nutritionix API](https://www.anchorterminal.com/compare/logmeal-vs-nutritionix.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- [Edamam vs spoonacular](https://www.anchorterminal.com/compare/edamam-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 Nutritionix API",
        "url": ""
      }
    ],
    "description": "Edamam scores 42.2 (E) to Nutritionix's 33.6 (F) for cooking nutrition. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Edamam E 42.2",
      "Nutritionix API F 33.6",
      "scores"
    ],
    "h1": "Edamam vs Nutritionix API",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/edamam-vs-nutritionix",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Edamam vs Nutritionix for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-04",
    "url": "https://www.anchorterminal.com/compare/edamam-vs-nutritionix"
  },
  "tokens": {
    "markdown": 4300,
    "slim": 2880
  },
  "version": 1
}
