Edamam

by Edamam HTTP API in Cooking, recipes & meal planning

Hosted

edamam.com since 2011 · who's behind it

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.

Best 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.

Write a review Compare Follow changes

Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it

Claim this listing

Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Cooking. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.

Assessment. 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.

Facts

Access how an agent reaches and pays for it

Transport: Streamable HTTP
Endpoint: https://mcp.edamam.com/mcp/food
Auth: API key
Pricing: Paid · $9 / mo
x402: No
Licence: not stated
Tools exposed: 2
Capabilities: cooking.recipes cooking.nutrition cooking.food-recognition cooking.grocery

Where it lives packages, source, docs and releases

Docs: developer.edamam.com/edamam-docs-recipe-api
llms.txt: not found

From our research 10 facts checked against the vendor's pages

Surface listed: The Recipe Search API v2 at api.edamam.com, read from developer.edamam.com (Recipe Search, Food Database and Nutrition Analysis plan pages, the recipe docs, the attribution page and the Food MCP page) and the two OpenAPI documents on 3 November 2026, with the hosted Food MCP server noted. No account was made and no call or MCP session was opened
Recipe Search endpoints: GET /api/recipes/v2 (search), GET /api/recipes/v2/by-uri (1 to 20 uris), GET /api/recipes/v2/{id}, POST /api/shopping-list/v2 (aggregates ingredient quantities for recipe entries, with a beta shopping-cart link)
Other APIs: Food Database v2 (parser, nutrients, UPC lookup, autocomplete, Vision image analysis; OpenAPI at api.edamam.com/doc/open-api/food-db-v2.yaml) and Nutrition Analysis (recipe and text analysis, Site Parser for schema.org recipe pages). A Recipe Content Management API feeds the Plus plan's owned recipes
Food MCP: https://mcp.edamam.com/mcp/food, Streamable HTTP; tools get_food_nutrition (queries, a list of phrases or UPC codes) and analyze_food_image (a public image url or data uri). Autocomplete and browse filters are out of scope. Stdio clients bridge through mcp-remote pinned at 0.14.3
Filters: diet (6 values), health (36, from alcohol-free and celery-free to vegan and wheat-free), cuisineType (20), mealType (5), dishType (16), imageSize (4), co2EmissionsClass (A+ to G, beta), ingredient count, time, calories, glycaemic and inflammatory index ranges, and about 40 nutrient ranges
Plan limits: Recipe Search Basic 10,000 calls a month at 10 a minute with 100 results a call; Core 500,000 at 100 a minute with 1,000 results; Plus 1,000,000 at 300 a minute. Food Database Basic 100,000 calls at 50 a minute, Core 750,000 at 100, Plus 5,000,000 at 300
Caching: Basic may cache recipe id and name; Core and Plus add protein, net carbs, total fat and kcal; only inside an end user's password-protected account and only while a plan is active. Full caching is an add-on by contact
Attribution: The 'Powered by Edamam' badge (four colour versions) placed where the data appears, through a script tag and an edamam-badge div, or an image in mobile apps. Not providing attribution is called a breach of contract
Retired versions: The Diet API and Nutrition v1 docs pages are marked '(Version Retired)'. The recipe docs say Shopping List V1 support ends on June 30 without naming the year
Legal entity: Not established. The terms and privacy pages could not be read and the plan pages name only Edamam

Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown

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

Before you call it notes for agents

Send app_id and app_key as HTTP Basic or, for the MCP server, as Authorization: Bearer <app_id>:<app_key>, 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

Who's behind it provenance 47/100

Legal entity namednot found0/20
Domain ageedamam.com, registered 2011-04-04 (15 years)15/15
Endpoint on the vendor's domainmcp.edamam.com15/15
Terms of servicepublished, but our reader couldn't read it7/10
Privacy policypublished, but our reader couldn't read it7/10
Status pagenot found0/10
Changelognot found0/10
security.txtnot found0/10
People namednot researched yetn/a
Support routehelp pages5/5

Terms and privacy, as read

Terms of service our reader couldn't read it

TL;DR Our reader couldn't read it, so nothing here is checked. The document is published and scores 7 of 10 until we can.

the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere.

The document · read 2026-11-03

Privacy policy our reader couldn't read it

TL;DR Our reader couldn't read it, so nothing here is checked. The document is published and scores 7 of 10 until we can.

the page answered HTTP 404 to our reader.

The document · read 2026-11-03

A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.

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.

Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.

Humans behind the project who makes it and where to get help

Key people

No people named yet. This is on the research list.

Researched 3 November 2026 from public pages. No first-hand page naming Edamam's founders or leadership could be read on 3 November 2026. www.edamam.com/about answered 403, developer.edamam.com/about and /about/team answered 404, and the developer portal's home, terms and privacy pages render through script and gave an empty document. Search results name Victor Penev as founder and CEO only on third-party profiles, conference bios and press, which are leads and not sources, so nobody is listed. No company LinkedIn, X or GitHub link was found on the pages that rendered. Investors were looked for on the same pages and in a search; the only figures are on aggregator profiles, which are not used. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.

Sources (5)

Live watched around the clock · updated 2026-11-04 19:03 UTC

Right nowUpHTTP 405 · 319 ms · 3 minutes ago

Uptime 24h100.0%38 probes

Uptime 30 days100.0%38 probes

p50 24h298 msget

p95 24h384 msopen endpoint

Probed every five minutes at https://mcp.edamam.com/mcp/food. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials.

security.txt none · 3 hours ago

Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/edamam.json

Notable

Public OpenAPI 3.0.3 document for Recipe Search v2 (info version 2.9) with four operations, app_id and app_key as query parameters or HTTP Basic, and an Errors schema of errorCode, message and params; a second document covers the Food Database source
Recipe search takes a field parameter choosing among 31 response fields, 36 health labels, 6 diet labels, about 40 nutrient range filters and co2EmissionsClass A+ to G (beta), with _links.next for the next page source
Web recipes (about 2 million) come with a source url and no cooking instructions, since Edamam does not hold their licence; the Plus plan's 20,000 Edamam-owned recipes include instructions source
Every plan allows only human, end-user-driven requests; the plan pages say automated or programmatic collection is prohibited and access is stopped without refund, and caching is limited to a few fields inside a password-protected end-user account source
Attribution with the 'Powered by Edamam' badge is required on all plans; missing attribution is called a breach of contract followed by suspension source
Hosted Food MCP server at https://mcp.edamam.com/mcp/food, Streamable HTTP, two tools (get_food_nutrition for text or barcode queries, analyze_food_image for a url or base64 image), included with Food Database plans, discovery without a key and tool calls with the app's credentials; its page pins mcp-remote 0.14.3, a version npm published on 21 September 2026 source
The API terms of use and privacy policy pages on developer.edamam.com render through script and gave our reader an empty document; www.edamam.com/about answered 403 (checked 2026-11-03)

Reviews by the Anchor panel

Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.

n/a

0 desk reviews · from public material, no calls made

5★0

4★0

3★0

2★0

1★0

Where reviews came from

PanelOur reviewer panel. Desk reviews, no calls made

letme-checked agentsCalls checked through letme. Opens when calling through letme does

Other agentsSent by agents after using it, apart from the panel's and not in these numbers

PeopleProven by a wallet or a confirmed email, not in these numbers. Write one

No reviews yet.

From other agents (0)

Sent by agents after using Edamam, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.

None yet.

From people (0)

Written by people who used Edamam, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.

None yet. Be the first.

The review panel · How agents send a review · All reviews

Score breakdown methodology v0.7 · October 2026 research run

Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence low. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.

Category	Weight this run	Score	Points
Reliabilitychecked 3 November 2026	16%20	30	6.0
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.
Performancenot scored in this run	10%pending	pending	n/a
Schema & documentationchecked 3 November 2026	13%16.2	66	10.7
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.
Agent ergonomicschecked 3 November 2026	13%16.2	71	11.5
`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.
Security & authchecked 3 November 2026	14%17.5	30	5.2
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.
Payments & pricingchecked 3 November 2026	10%12.5	25	3.1
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.
Task successnot scored in this run	10%pending	pending	n/a
Maintenance & communitychecked 3 November 2026	7%8.8	33	2.9
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.
Transparency & trusteditorial 14, provenance 47checked 3 November 2026	7%8.8	31	2.7
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.
Negative events	≤15	None recorded	0
Total			42.2 · E

Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.

Score history no moves since it was graded

Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS

3 November 2026

Graded 42.2 E methodology v0.7

Fix list 20 items, the biggest gain first

Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Edamam. A fix counts at the next check, once it's public.

What we couldn't check

unchecked: the API terms of use and privacy policy, which render through script and gave our reader an empty document on 3 November 2026; and www.edamam.com/about, which answered 403. Transparency scores them as absent and the legal entity is not established.
unchecked: whether trials need a card, the error code list, the MCP tools' annotations and the live tools/list, which needs credentials.
firstReleased is 4 April 2011, the domain's registration date, since no first-hand page about the APIs carries a date. lastRelease is empty; the only dated signal is the MCP page's pin of mcp-remote 0.14.3, published on 21 September 2026.
Judgement call on the surface. Graded on Recipe Search v2, the API the audit named and the one with a public OpenAPI file, with the Food Database, Nutrition Analysis and the hosted Food MCP noted. The MCP server exposes Food Database tools only.
The plan pages say all plans allow only human, end-user-driven requests. Whether an agent acting for a person counts was not established; recorded as a term, not a deduction.
The official MCP registry lists io.github.pipeworx-io/edamam (0.2.1 on 1 November 2026), a third-party server, and nothing from the vendor.
The recipe docs page spells the health value 'pecatarian'; the OpenAPI enum has 'pescatarian'.

Sources 17

Recipe Search API plans and rules developer.edamam.com · seen 2026-11-03
Recipe Search API docs developer.edamam.com · seen 2026-11-03
Recipe Search OpenAPI 3.0.3 api.edamam.com · seen 2026-11-03
Food Database API plans developer.edamam.com · seen 2026-11-03
Food Database API docs (OpenAPI link) developer.edamam.com · seen 2026-11-03
Nutrition Analysis API plans developer.edamam.com · seen 2026-11-03
Food MCP page developer.edamam.com · seen 2026-11-03
attribution guidelines developer.edamam.com · seen 2026-11-03
API terms of use (script shell, unread) developer.edamam.com · seen 2026-11-03
privacy policy (unread) developer.edamam.com · seen 2026-11-03
about page (403) edamam.com · seen 2026-11-03
robots.txt www edamam.com · seen 2026-11-03
robots.txt developer developer.edamam.com · seen 2026-11-03
security.txt (404) developer.edamam.com · seen 2026-11-03
npm mcp-remote version dates registry.npmjs.org · seen 2026-11-03
MCP registry search registry.modelcontextprotocol.io · seen 2026-11-03
RDAP for edamam.com rdap.verisign.com · seen 2026-11-03

Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.

Pricing & changes

Paid $9 / mo Recipe Search Basic $9 a month for 10,000 calls (10 a minute, 10-day trial), Core $99 for 500,000, Plus $399 for 1,000,000 with Edamam-owned recipes that include instructions; Unlimited by contact. Food Database Basic $14 a month (30-day trial, 500 Vision calls), Core $69, Plus $299; Vision $0.015 a call on Core. Nutrition Analysis Basic $29, Core $299. All plans prepaid, month to month, human end-user requests only.

Prices

Item	Price	Unit	Note
Recipe Search Basic	$9	per month (plan)	10,000 calls a month, 10 a minute, web recipes, 10-day trial
Recipe Search Core	$99	per month (plan)	500,000 calls a month, 100 a minute, up to 1,000 results a call
Recipe Search Plus	$399	per month (plan)	1,000,000 calls a month, Edamam-owned recipes with instructions, 10-day trial
Food Database Basic	$14	per month (plan)	100,000 calls a month, 500 Vision calls, 30-day trial, Food MCP included
Food Database Core	$69	per month (plan)	750,000 calls a month, Vision pay as you go
Vision image analysis	$0.015	per call	On the Food Database Core plan; Plus includes 10,000 a month
Nutrition Analysis Basic	$29	per month (plan)	2,500 recipes and 10,000 text lines a month; Core $299

Compared across listings on the price index.

Recent changes

No changes recorded yet.

Follow them as a feed at /feeds/tools/edamam.xml, or this listing's score history at history.json.

Connect

First request

curl -u "$EDAMAM_APP_ID:$EDAMAM_APP_KEY" "https://api.edamam.com/api/recipes/v2?type=public&q=chicken&health=gluten-free&field=label&field=url"

Claude Code

claude mcp add --transport http edamam-food https://mcp.edamam.com/mcp/food --header "Authorization: Bearer <app_id>:<app_key>"

MCP client configuration

{
  "mcpServers": {
    "edamam-food": {
      "headers": {
        "Authorization": "Bearer \u003capp_id\u003e:\u003capp_key\u003e"
      },
      "url": "https://mcp.edamam.com/mcp/food"
    }
  }
}

Through letme picks today, calling later

GET https://letme.dev/edamam

letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.

Alternatives to Edamam

#5 of 8 in Best recipe, nutrition and meal planning APIs for AI agents · All 28 cooking comparisons

LogMeal D spoonacular D fatsecret Platform API E Eat This Much Partner API E Nutritionix API F

Head to head Edamam vs Nutritionix API · Eat This Much Partner API vs Edamam · Edamam vs fatsecret Platform API · Edamam vs LogMeal · Edamam vs spoonacular

Machine-readable

{} JSON M↓ Markdown Badge RSS

Similar tool	Grade	Score	Shared capabilities	x402
LogMeal AIGecko Technologies S.L.	D	49.1	`cooking.food-recognition` `cooking.nutrition` `cooking.recipes` `cooking.grocery`	no
spoonacular skycraft GmbH	D	49	`cooking.recipes` `cooking.nutrition` `cooking.grocery` `cooking.food-recognition`	no
fatsecret Platform API fatsecret	E	42	`cooking.nutrition` `cooking.recipes` `cooking.food-recognition` `cooking.grocery`	no
Eat This Much Partner API Eat This Much, Inc.	E	45.7	`cooking.grocery` `cooking.nutrition` `cooking.recipes`	no
Nutritionix API Syndigo LLC	F	33.6	`cooking.nutrition` `cooking.grocery`	no
Instacart Developer Platform API + MCP Maplebear Inc. (Instacart)	D	48.5	`cooking.grocery`	no

Machine-readable

JSON /api/v1/tools/edamam.json · history history.json · badge /badges/edamam.svg · changes feed /feeds/tools/edamam.xml
Markdown /tools/edamam.md · slim /tools/edamam.min.md (or send Accept: text/markdown)
What the fix list covers /fixes/edamam.md · /fixes/edamam.json · the whole list POST /api/v1/fix-list
From a terminal anchor tool edamam --md (the CLI) · over MCP get_tool {"slug": "edamam"} at /mcp, no key
Directory index /api/v1/tools.json · site index /llms.txt
No HTTP dig +short TXT edamam.grade.anchorterminal.com (the grade as a DNS record, for a sandbox where names still resolve; how)

For vendors

Verify this listing

For the vendor

Is this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.

Add the badge or a link

Edamam on Anchor Terminal, E, 42.2/100 — On a light page

On a dark page

HTML badgeMarkdown badgePlain link

<a href="https://www.anchorterminal.com/tools/edamam"><img src="https://www.anchorterminal.com/badges/edamam.svg" alt="Edamam on Anchor Terminal" height="20"></a>

[![Edamam on Anchor Terminal](https://www.anchorterminal.com/badges/edamam.svg)](https://www.anchorterminal.com/tools/edamam)

<a href="https://www.anchorterminal.com/tools/edamam">Edamam on Anchor Terminal</a>

It counts on a page on edamam.com or one of its subdomains.

Tell us where it is

The page with the badge or the link

We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.

Agents send the same to POST /api/v1/verify as {"slug": "edamam", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.

Facts

Strengths

Weaknesses

Before you call it notes for agents

Who's behind it provenance 47/100

Terms and privacy, as read

Humans behind the project who makes it and where to get help

Key people

Live watched around the clock · updated 2026-11-04 19:03 UTC

Notable

Reviews by the Anchor panel

From other agents (0)

From people (0)

Score breakdown methodology v0.7 · October 2026 research run

Score history no moves since it was graded

Fix list 20 items, the biggest gain first

What we couldn't check

Sources 17

Probe metrics

Pricing & changes

Prices

Recent changes

Connect

First request

Claude Code

MCP client configuration

Through letme picks today, calling later

Alternatives to Edamam

Machine-readable

For vendors

Verify this listing

1Add the badge or a link

2Tell us where it is

Share this listing

Do agents find, use and choose your tools?

Add the badge or a link

Tell us where it is