Edamam
Edamam is a food and nutrition data platform powering recipe search, NLP-based nutrition analysis, food database lookup (keyword / brand / UPC / AI Vision), and personalized meal planning. The flagship Recipe Search API v2 covers a 2M+ recipe index with 30+ filters across diet, health, cuisine, meal, dish, nutrients, time, glycemic index, and CO2 emissions class.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Edamam the way a machine reads it — 67 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Edamam scores 52.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Edamam
Each block below is one kind of artifact we hold for Edamam. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Edamam Food Nutrition Request - AI Vision (Beta) API
The Food Nutrition Request - AI Vision (Beta) API from Edamam — 1 operation(s) for food nutrition request - ai vision (beta).
Edamam Food Request Step 1 - Parser API
The Food Request Step 1 - Parser API from Edamam — 1 operation(s) for food request step 1 - parser.
Edamam Food Request Step 2 - Nutrients API
The Food Request Step 2 - Nutrients API from Edamam — 1 operation(s) for food request step 2 - nutrients.
Edamam Food Search Autocomplete API
The Food Search Autocomplete API from Edamam — 1 operation(s) for food search autocomplete.
Edamam Nutrition Data API
The Nutrition Data API from Edamam — 1 operation(s) for nutrition data.
Edamam Nutrition Details API
The Nutrition Details API from Edamam — 1 operation(s) for nutrition details.
Edamam planner API
Meal planning
Edamam Recipe Search API
Search or access individual recipes.
Edamam Shopping List API
The *Shopping List API* provides aggregation of shopping item quantities over one or more ingredient lists, and optional referral to external shopping services. A `shopping-list...
Edamam values API
Daily values
Scroll within the panel for all 10 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Food Database API
OPEN COLLECTIONMeal Planning API
OPEN COLLECTIONNutrition Analysis API
OPEN COLLECTIONRecipe Search and Shopping List API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Edamam Recipes Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Edamam Recipes Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
2M+ Recipe Index
Search across 2 million recipes from third-party sources plus 20,000+ Edamam-owned recipes with cooking instructions.
30+ Filters
Filter by diet, health/allergen labels, cuisine, meal type, dish type, calorie range, total time, nutrients, glycemic index, and excluded ingredients.
28+ Nutrients
Per-recipe and per-food breakdowns including macros, vitamins (A, B-12, C, D, E, K), minerals (Ca, Fe, K, Mg, P, Zn), fiber, sodium, sugars.
Carbon Footprint (CO2e)
Recipes carry a CO2 emissions class (A+ through G) when beta=true is set.
AI Vision Food Recognition
Submit a public image URL or base64 data URI to the Food Database API and receive detected food + nutrition estimates.
NLP Recipe Analysis
Submit raw recipe text (title + ingredient lines) to the Nutrition Analysis API and receive structured nutrient and label output.
Active User Tracking
Use the Edamam-Account-User header to bind per-user budgets and caching rights (required on Enterprise and Meal Planner plans).
Shopping List Aggregation
Aggregate ingredient quantities across one or more recipes into a consolidated shopping list, with optional Instacart integration on Enterprise tiers.
HTTP Compression
gzip supported via Accept-Encoding header.
HATEOAS Pagination
_links.next on paged responses; _links.self on individual hits.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Edamam Recipes Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Edamam API Rules
SPECTRALEdamam API Rules
SPECTRALJSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Edamam Food
JSON SCHEMAEdamam Meal Plan
JSON SCHEMAEdamam Nutrient Info
JSON SCHEMAEdamam Recipe
JSON SCHEMAEdamam Recipe Search Response
JSON SCHEMAJSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Edamam Food Structure
JSON STRUCTUREEdamam Meal Plan Structure
JSON STRUCTUREEdamam Recipe Structure
JSON STRUCTUREExamples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 7 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Recipe Discovery Apps
Build consumer recipe search and discovery apps with rich filtering.
Nutrition Tracking
Power food logging and nutrition tracking with NLP-based ingredient analysis.
Personalized Meal Planning
Generate diet- and health-aware meal plans for fitness, wellness, and clinical nutrition apps.
Grocery and Shopping
Aggregate ingredients into shopping lists with optional Instacart fulfillment.
Chatbots and Voice
Edamam Platform Assistant chatbot and MCP server expose food/recipe tools to conversational agents.
Sustainability Apps
Surface CO2e emissions class to promote lower-impact food choices.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Instacart
Meal Planner Enterprise tiers integrate with Instacart for grocery fulfillment.
Edamam Platform Assistant
Built-in chatbot UI for recipe / nutrition Q&A.
Edamam Content Management
Recipe Management API integrates with the Recipe Search surface.
Model Context Protocol (MCP)
Official Edamam Food MCP server at https://mcp.edamam.com/mcp/food exposes get_food_nutrition and analyze_food_image tools to LLM agents (Claude Code, etc.).
Solutions 9
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Recipe Search Enterprise Basic
$9/mo, 10,000 calls/mo, 10 calls/min, third-party web recipes, 10-day trial.
Recipe Search Enterprise Core
$99/mo, 500,000 calls/mo, 100 calls/min.
Recipe Search Enterprise Plus
$399/mo, 1,000,000 calls/mo, 300 calls/min, Edamam-owned recipes with cooking instructions, CO2e data.
Recipe Search Enterprise Unlimited
Custom — contact sales for unlimited usage and custom content.
Food Database Basic Vision
$14/mo, 100,000 calls + 500 Vision requests, includes MCP server access.
Food Database Core
$69/mo, 750,000 calls, pay-as-you-go Vision.
Food Database Plus
$299/mo, 5,000,000 calls, 10,000 Vision requests.
Meal Planner Developer
Free, 10 MAU, 20 meal-plan calls/day, 300 recipe calls/min, non-commercial.
Meal Planner Enterprise Core
$300/mo, 1,000 MAU, 30 meal-plan calls/day, 5,000 recipe calls/min, Instacart integration.
Scroll within the panel for all 9 ·
Resources
Every other property we hold for Edamam — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/edamam-recipes · machine-readable index on apis.io