{ "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-04T20:04:59.632187903Z", "lastOk": true, "lastStatus": 405, "lastMs": 360, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 298, "p95ms24h": 384, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-11-04", "probes": 48, "ok": 48 } ] }, "securityTxt": { "url": "https://edamam.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:51.148952618Z" }, "updatedAt": "2026-11-04T20:04:59.632187903Z" } }, "answer": "Edamam and fatsecret Platform API score within a point of each other on agent readiness, 42.2 (E) and 42 (E). fatsecret Platform API leads on reliability and security \u0026 auth.", "b": { "slug": "fatsecret", "name": "fatsecret Platform API", "vendor": "fatsecret", "vendorUrl": "https://platform.fatsecret.com/platform-api", "kind": "http-api", "category": "cooking", "summary": "The fatsecret Platform API is a REST API over fatsecret's verified food and nutrition database, with food search, barcode lookup, recipes, image recognition and natural-language food logging, plus per-user food, exercise and weight diaries, under OAuth 2.0 and OAuth 1.0.", "url": "https://www.anchorterminal.com/tools/fatsecret", "markdownUrl": "https://www.anchorterminal.com/tools/fatsecret.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fatsecret.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fatsecret.json", "dns": "fatsecret.grade.anchorterminal.com", "transports": [], "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 client credentials at https://oauth.fatsecret.com/connect/token with a Client ID and Client Secret from the developer dashboard after a browser registration; tokens last 86,400 seconds and carry scopes (`basic`, `premier`, `barcode`, `localization`, `nlp`, `image-recognition` and `feedback`), and token requests are allowed only from the IP addresses or CIDR ranges registered on the key. OAuth 1.0 with HMAC-SHA1 signatures is kept for signed and delegated (per-user profile) requests, including a 3-legged flow for fatsecret.com accounts.", "pricing": "freemium", "pricingNotes": "Basic is free on self sign-up with 5,000 calls a day, US data, English and attribution required. Premier Free (start-ups under US$1M revenue and raised, non-profits, students) needs verification and removes the daily cap. Premier is priced on request by market, with 62 regional datasets, 26 languages, white label and a month-by-month SLA; image recognition and NLP are add-ons billed in tiers of 25,000 inputs. No card for Basic or Premier.", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the guides, editions page, authentication guides or terms (checked 2026-11-03). Premier is contracted through sales.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 25, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://platform.fatsecret.com/docs/guides", "capabilities": [ "cooking.nutrition", "cooking.recipes", "cooking.food-recognition", "cooking.grocery" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "oauth", "sales-led", "enterprise", "closed-source", "no-status-page" ], "graded": true, "anchor": { "graded": true, "score": 42, "grade": "E", "agentReady": false, "rank": 1193, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 13, "payments": 25, "reliability": 35, "schema": 52, "security": 51, "transparency": 34 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "OAuth 2.0 client credentials with feature scopes, IP-restricted tokens, a free 5,000-call day with no card, and per-serving nutrients with allergen flags on branded and generic foods. The newest search and image methods need the sales-priced Premier edition, there is no status page, OpenAPI file or official SDK, and the privacy policy and blog could not be read.", "bestFor": "Agents logging foods and reading serving-level nutrients, allergens and barcodes for a person, with diaries written back; strongest outside the US on Premier with 62 regional datasets.", "strengths": [ "OAuth 2.0 client credentials with seven scopes, 24-hour tokens and token requests limited to registered IP addresses", "Basic edition free on self sign-up with 5,000 calls a day and no card", "Serving-level nutrients with allergen and preference flags, barcode lookup and 212 region codes in 26 languages on Premier", "Numeric error codes with messages documented centrally and per method, with JSON or XML responses", "Per-user food, exercise and weight diaries can be written through profiles, so a plan can reach a person's log" ], "weaknesses": [ "Natural language, image recognition, autocomplete, barcode scanning and foods.search v5 are Premier Exclusive, priced on request by market", "No status page, SLA figures outside Premier, OpenAPI document, llms.txt, changelog or official SDK found", "No HTTP 429 or Retry-After documented; limits surface as error codes 11 and 12 in the body", "Content not marked storable must be removed or re-requested within 24 hours, and attribution is required wherever it is shown on Basic and Premier Free", "The privacy policy on foods.fatsecret.com and the blog's release notes could not be read, and the terms name no legal entity or date" ], "agentNotes": [ "Request a token with `grant_type=client_credentials` and only the scopes the task needs; a token request from an IP not registered on the key fails, so run from a fixed address", "Use `foods.search` v1 on Basic, since v5, autocomplete, barcode and image methods answer with a scope error without Premier", "Pass `format=json` and keep `max_results` at or below 50 with a zero-based `page_number`; treat error code 11 or 12 in the body as the rate limit, since no 429 is documented", "Store only food_id and serving_id between sessions and re-request other values within 24 hours, as the terms require", "Use a delegated profile token for diary writes and keep the profile's oauth_token and oauth_secret, since fatsecret does not return them again" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42 } ], "editorialScores": { "ergonomics": 64, "maintenance": 13, "payments": 25, "reliability": 35, "schema": 52, "security": 51, "transparency": 18 }, "provenanceScore": 49, "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 \"$FATSECRET_CLIENT_ID:$FATSECRET_CLIENT_SECRET\" -d \"grant_type=client_credentials\u0026scope=basic\" https://oauth.fatsecret.com/connect/token" }, "letme": { "capability": "https://letme.dev/cooking.nutrition", "tool": "https://letme.dev/fatsecret" }, "area": "everyday", "provenance": { "legalEntity": "", "domain": "fatsecret.com", "domainRegistered": "2006-04-07", "endpointOnVendorDomain": true, "terms": "https://platform.fatsecret.com/terms", "privacy": "https://foods.fatsecret.com/Default.aspx?pa=priv\u0026l=en", "statusPage": "", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "The Platform API terms name the provider only as Fatsecret.com, under the law of the State of Victoria, Australia, with no effective date. They forbid robots, spiders or other automated applications retrieving or indexing API content except as the documentation allows, and say fatsecret may crawl or monitor applications; no clause addresses automated reading of the website.", "platform.fatsecret.com/robots.txt disallows /rest* for all crawlers, which is the API itself, and nothing was fetched under it. foods.fatsecret.com/robots.txt disallows the whole site for ClaudeBot, anthropic-ai and other named crawlers, so the privacy policy there was not read. blog.fatsecret.com/robots.txt answered 403, so the blog's release notes were not read. www.fatsecret.com has no robots.txt (404) and its about-us page answered 403.", "No status page or changelog found. platform.fatsecret.com/.well-known/security.txt answered the site's generic error page with a request id, so security.txt is unknown. No llms.txt (302 to another page).", "RDAP gives fatsecret.com a registration date of 7 April 2006, the year the about page gives for the company's founding." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/fatsecret.json", "live": { "slug": "fatsecret", "securityTxt": { "url": "https://fatsecret.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:54.388597771Z" }, "updatedAt": "2026-11-04T15:52:54.388597771Z" } }, "edges": [ { "by": 21, "category": "security", "leads": "fatsecret", "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": "OAuth 2.0 client credentials with seven scopes gating capabilities (`basic`, `premier`, `barcode`, `localization`, `nlp`, `image-recognition` and `feedback`), tokens of 86,400 seconds, a Client Secret that stays on the server, and token requests limited to IP addresses or CIDR ranges registered on the key; OAuth 1.0 with HMAC-SHA1 remains for delegated calls. The scopes gate capabilities rather than read or write, and no rotation procedure was found (26 of 30). Per-user data is reached only through a delegated profile token, and the shared data methods are reads, but there is no read-only scope and no confirmation step for diary writes (14 of 20). Food and brand names are verified by fatsecret and recipes are its own content, with no guidance on treating them as untrusted (8 of 15). No request log or per-call visibility was found beyond the dashboard (3 of 15). The security.txt path answered the site's generic error page, and no disclosure policy, bug bounty or certification was found (0 of 20). 26 + 14 + 8 + 3 + 0 = 51." }, "scores": { "a": 30, "b": 51 } }, { "by": 20, "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. No dated API change could be read first-hand. The blog that carries the 'What's new' notes sits behind a robots.txt that answered 403, the method pages are undated, and the official Postman repository's last push is 1 July 2025, more than 180 days before 3 November 2026 (0 of 30). No three dated changes in 90 days established (0 of 20). A developer forum on Google Groups, a contact form, and email, phone, Slack and video support on Premier, with no public changelog on the platform site (8 of 15). No official SDK; an official Postman collection (5 of 15). No package to assess (0 of 10). 0 + 0 + 8 + 5 + 0 = 13." }, "scores": { "a": 33, "b": 13 } }, { "by": 14, "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; the official Postman collection is the only machine-readable contract (8 of 25). No llms.txt (a redirect) and no Markdown docs (0 of 10). Each method page states purpose, parameters, response fields and Premier status, with little on when not to use a method (12 of 20). Parameters are typed with defaults and allowed values, `max_results` is capped at 50, but the field tables mistype allergen names as Long and leave food_images out of the food-level fields (11 of 15). Example responses in XML and JSON on each method, a central error code list with the body shape, and per-method error codes (13 of 15). Methods carry versions (v1 to v5) and older versions stay documented, but no changelog is on the platform site and the blog's 'What's new' could not be read (8 of 15). 8 + 0 + 12 + 11 + 13 + 8 = 52." }, "scores": { "a": 66, "b": 52 } }, { "by": 7, "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": "`max_results` up to 50 (default 20), `format=json`, and `include_*` switches add sub-categories, images and attributes only when asked, but there is no field selection and each food carries every serving (15 of 25). Zero-based `page_number`, `food_type` generic or brand, region and language filters (18 of 20). Numeric error codes with messages, for OAuth, parameters and application errors, but limit errors come as codes 11 and 12 with no HTTP status or retry hint (13 of 20). Food and recipe methods are reads and safe to repeat; diary and saved-meal writes have no idempotency key (10 of 20). No parameter is required on foods.search, but there is no official SDK in any language (8 of 15). 15 + 18 + 13 + 10 + 8 = 64." }, "scores": { "a": 71, "b": 64 } }, { "by": 5, "category": "reliability", "leads": "fatsecret", "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. No status page was found on the platform site, the guides, the editions page or the about page (0), so there is no incident history to read (5). The limit is published with a number, 5,000 calls a day on Basic in the terms and on the editions page, and Premier is unlimited (15). Limits surface as error codes 11 and 12 in the body; no HTTP 429, Retry-After or backoff guidance was found, and diary writes have no idempotency key (5 of 15). Premier carries a month-by-month SLA with service credits, named on the editions page without figures, and every edition claims more than 99.9 per cent uptime (5 of 10). The API is generally available, with versioned methods (10). 0 + 5 + 15 + 5 + 5 + 10 = 35." }, "scores": { "a": 30, "b": 35 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Edamam", "b": "fatsecret", "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": "OAuth", "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": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "couldn't be read", "b": "no date given", "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": "not found in the text", "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": "25 stars", "name": "Popularity" } ], "faq": [ { "answer": "Edamam and fatsecret Platform API score within a point of each other on agent readiness, 42.2 (E) and 42 (E). fatsecret Platform API leads on reliability and security \u0026 auth.", "question": "Which is better for AI agents, Edamam or fatsecret Platform API?" }, { "answer": "Edamam needs an API key. fatsecret Platform API uses an OAuth sign-in.", "question": "Do Edamam and fatsecret Platform API need an API key?" }, { "answer": "Edamam has a hosted endpoint at https://mcp.edamam.com/mcp/food. No hosted endpoint is listed for fatsecret Platform API.", "question": "Can an agent call Edamam and fatsecret Platform API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 66 against 52", "Agent ergonomics, 71 against 64", "Maintenance \u0026 community, 33 against 13" ], "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, 35 against 30", "Security \u0026 auth, 51 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "Agents logging foods and reading serving-level nutrients, allergens and barcodes for a person, with diaries written back; strongest outside the US on Premier with 62 regional datasets.", "slug": "fatsecret", "watchFor": "Natural language, image recognition, autocomplete, barcode scanning and foods.search v5 are Premier Exclusive, priced on request by market" } ], "history": null, "job": { "capability": "cooking.recipes", "name": "Cooking recipes" }, "others": [ { "json": "https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.json", "title": "Eat This Much Partner API vs fatsecret Platform API", "url": "https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret" }, { "json": "https://www.anchorterminal.com/compare/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-logmeal.json", "title": "fatsecret Platform API vs LogMeal", "url": "https://www.anchorterminal.com/compare/fatsecret-vs-logmeal" }, { "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/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/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-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": 5, "edamam": 30, "edge": "fatsecret", "fatsecret": 35, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "edamam": 66, "edge": "edamam", "fatsecret": 52, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 7, "edamam": 71, "edge": "edamam", "fatsecret": 64, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 21, "edamam": 30, "edge": "fatsecret", "fatsecret": 51, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "edamam": 25, "edge": "", "fatsecret": 25, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 20, "edamam": 33, "edge": "edamam", "fatsecret": 13, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 3, "edamam": 31, "edge": "fatsecret", "fatsecret": 34, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Edamam and fatsecret Platform API score within a point of each other on agent readiness, 42.2 (E) and 42 (E). fatsecret Platform API leads on reliability and security \u0026 auth. 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.", "fatsecret": "OAuth 2.0 client credentials with feature scopes, IP-restricted tokens, a free 5,000-call day with no card, and per-serving nutrients with allergen flags on branded and generic foods. The newest search and image methods need the sales-priced Premier edition, there is no status page, OpenAPI file or official SDK, and the privacy policy and blog could not be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/edamam-vs-fatsecret", "json": "https://www.anchorterminal.com/compare/edamam-vs-fatsecret.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/edamam-vs-fatsecret.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/edamam-vs-fatsecret.min.md" }, "markdown": "Edamam and fatsecret Platform API score within a point of each other on agent readiness, 42.2 (E) and 42 (E). fatsecret Platform API leads on reliability and security \u0026 auth. 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- fatsecret Platform API: grade E, 42/100, rank #1193 of 1349. Markdown https://www.anchorterminal.com/tools/fatsecret.md · JSON https://www.anchorterminal.com/api/v1/tools/fatsecret.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- Schema \u0026 documentation, 66 against 52\n- Agent ergonomics, 71 against 64\n- Maintenance \u0026 community, 33 against 13\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### fatsecret Platform API (E)\n\nGood for: Agents logging foods and reading serving-level nutrients, allergens and barcodes for a person, with diaries written back; strongest outside the US on Premier with 62 regional datasets.\n\nAhead on:\n- Reliability, 35 against 30\n- Security \u0026 auth, 51 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Natural language, image recognition, autocomplete, barcode scanning and foods.search v5 are Premier Exclusive, priced on request by market\n\n\n## Why the edge\n\n### Security \u0026 auth: fatsecret Platform API +21\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- fatsecret Platform API (51): OAuth 2.0 client credentials with seven scopes gating capabilities (`basic`, `premier`, `barcode`, `localization`, `nlp`, `image-recognition` and `feedback`), tokens of 86,400 seconds, a Client Secret that stays on the server, and token requests limited to IP addresses or CIDR ranges registered on the key; OAuth 1.0 with HMAC-SHA1 remains for delegated calls. The scopes gate capabilities rather than read or write, and no rotation procedure was found (26 of 30). Per-user data is reached only through a delegated profile token, and the shared data methods are reads, but there is no read-only scope and no confirmation step for diary writes (14 of 20). Food and brand names are verified by fatsecret and recipes are its own content, with no guidance on treating them as untrusted (8 of 15). No request log or per-call visibility was found beyond the dashboard (3 of 15). The security.txt path answered the site's generic error page, and no disclosure policy, bug bounty or certification was found (0 of 20). 26 + 14 + 8 + 3 + 0 = 51.\n\n### Maintenance \u0026 community: Edamam +20\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- fatsecret Platform API (13): Read as a closed service. No dated API change could be read first-hand. The blog that carries the 'What's new' notes sits behind a robots.txt that answered 403, the method pages are undated, and the official Postman repository's last push is 1 July 2025, more than 180 days before 3 November 2026 (0 of 30). No three dated changes in 90 days established (0 of 20). A developer forum on Google Groups, a contact form, and email, phone, Slack and video support on Premier, with no public changelog on the platform site (8 of 15). No official SDK; an official Postman collection (5 of 15). No package to assess (0 of 10). 0 + 0 + 8 + 5 + 0 = 13.\n\n### Schema \u0026 documentation: Edamam +14\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- fatsecret Platform API (52): No OpenAPI or similar document was found; the official Postman collection is the only machine-readable contract (8 of 25). No llms.txt (a redirect) and no Markdown docs (0 of 10). Each method page states purpose, parameters, response fields and Premier status, with little on when not to use a method (12 of 20). Parameters are typed with defaults and allowed values, `max_results` is capped at 50, but the field tables mistype allergen names as Long and leave food_images out of the food-level fields (11 of 15). Example responses in XML and JSON on each method, a central error code list with the body shape, and per-method error codes (13 of 15). Methods carry versions (v1 to v5) and older versions stay documented, but no changelog is on the platform site and the blog's 'What's new' could not be read (8 of 15). 8 + 0 + 12 + 11 + 13 + 8 = 52.\n\n### Agent ergonomics: Edamam +7\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- fatsecret Platform API (64): `max_results` up to 50 (default 20), `format=json`, and `include_*` switches add sub-categories, images and attributes only when asked, but there is no field selection and each food carries every serving (15 of 25). Zero-based `page_number`, `food_type` generic or brand, region and language filters (18 of 20). Numeric error codes with messages, for OAuth, parameters and application errors, but limit errors come as codes 11 and 12 with no HTTP status or retry hint (13 of 20). Food and recipe methods are reads and safe to repeat; diary and saved-meal writes have no idempotency key (10 of 20). No parameter is required on foods.search, but there is no official SDK in any language (8 of 15). 15 + 18 + 13 + 10 + 8 = 64.\n\n### Reliability: fatsecret Platform API +5\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- fatsecret Platform API (35): Read with the hosted lines. No status page was found on the platform site, the guides, the editions page or the about page (0), so there is no incident history to read (5). The limit is published with a number, 5,000 calls a day on Basic in the terms and on the editions page, and Premier is unlimited (15). Limits surface as error codes 11 and 12 in the body; no HTTP 429, Retry-After or backoff guidance was found, and diary writes have no idempotency key (5 of 15). Premier carries a month-by-month SLA with service credits, named on the editions page without figures, and every edition claims more than 99.9 per cent uptime (5 of 10). The API is generally available, with versioned methods (10). 0 + 5 + 15 + 5 + 5 + 10 = 35.\n\n## Score by category\n\n| Category | Weight | Edamam | fatsecret Platform API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 30 | 35 | fatsecret Platform API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 52 | Edamam +14 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 64 | Edamam +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 51 | fatsecret Platform API +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 25 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 33 | 13 | Edamam +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 31 | 34 | fatsecret Platform API +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **42.2 · E** | **42 · E** | |\n\n## Facts side by side\n\n| Fact | Edamam | fatsecret Platform API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Edamam | fatsecret |\n| Hosted endpoint | `https://mcp.edamam.com/mcp/food` | no (local only) |\n| Transports | Streamable HTTP | |\n| Auth | API key | OAuth |\n| Pricing | Paid | Freemium |\n| Price for cooking recipes | $9 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 | no |\n| Terms last updated | couldn't be read | no date given |\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 | not found in the text |\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 | 25 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**fatsecret Platform API.** OAuth 2.0 client credentials with feature scopes, IP-restricted tokens, a free 5,000-call day with no card, and per-serving nutrients with allergen flags on branded and generic foods. The newest search and image methods need the sales-priced Premier edition, there is no status page, OpenAPI file or official SDK, and the privacy policy and blog could not be read.\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### fatsecret Platform API\n\n1. Request a token with `grant_type=client_credentials` and only the scopes the task needs; a token request from an IP not registered on the key fails, so run from a fixed address\n2. Use `foods.search` v1 on Basic, since v5, autocomplete, barcode and image methods answer with a scope error without Premier\n3. Pass `format=json` and keep `max_results` at or below 50 with a zero-based `page_number`; treat error code 11 or 12 in the body as the rate limit, since no 429 is documented\n4. Store only food_id and serving_id between sessions and re-request other values within 24 hours, as the terms require\n5. Use a delegated profile token for diary writes and keep the profile's oauth_token and oauth_secret, since fatsecret does not return them again\n\n## Questions\n\n### Which is better for AI agents, Edamam or fatsecret Platform API?\n\nEdamam and fatsecret Platform API score within a point of each other on agent readiness, 42.2 (E) and 42 (E). fatsecret Platform API leads on reliability and security \u0026 auth.\n\n### Do Edamam and fatsecret Platform API need an API key?\n\nEdamam needs an API key. fatsecret Platform API uses an OAuth sign-in.\n\n### Can an agent call Edamam and fatsecret Platform API without installing anything?\n\nEdamam has a hosted endpoint at https://mcp.edamam.com/mcp/food. No hosted endpoint is listed for fatsecret Platform API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/edamam-vs-fatsecret.json, and with the fewest tokens: https://www.anchorterminal.com/compare/edamam-vs-fatsecret.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"edamam\", \"b\": \"fatsecret\"}`. From a terminal: `anchor compare edamam fatsecret`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/edamam.json and https://www.anchorterminal.com/api/v1/tools/fatsecret.json\n\n## Other comparisons with Edamam or fatsecret Platform API\n\n- [Eat This Much Partner API vs fatsecret Platform API](https://www.anchorterminal.com/compare/eat-this-much-vs-fatsecret.md)\n- [Edamam vs Nutritionix API](https://www.anchorterminal.com/compare/edamam-vs-nutritionix.md)\n- [fatsecret Platform API vs LogMeal](https://www.anchorterminal.com/compare/fatsecret-vs-logmeal.md)\n- [fatsecret Platform API vs Nutritionix API](https://www.anchorterminal.com/compare/fatsecret-vs-nutritionix.md)\n- [fatsecret Platform API vs spoonacular](https://www.anchorterminal.com/compare/fatsecret-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 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 fatsecret Platform API", "url": "" } ], "description": "Edamam and fatsecret Platform score within a point of each other for cooking recipes, 42.2 and 42 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Edamam E 42.2", "fatsecret Platform API E 42", "scores" ], "h1": "Edamam vs fatsecret Platform API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/edamam-vs-fatsecret", "published": "2026-10-01", "section": "tools", "title": "Edamam vs fatsecret Platform for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/edamam-vs-fatsecret" }, "tokens": { "markdown": 4200, "slim": 2730 }, "version": 1 }