Spoonacular
The Spoonacular Recipe and Food API provides programmatic access to thousands of recipes, thousands of ingredients, 800,000+ food products, and 100,000+ menu items, plus nutrition analysis, meal planning, wine pairing, and food classification. Authentication is via an API key sent in the x-api-key header.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Spoonacular the way a machine reads it — 56 machine-readable artifacts across 7 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 — Spoonacular scores 60.2/100 (strong), with a separate agent-readiness read of 55/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 Spoonacular
Each block below is one kind of artifact we hold for Spoonacular. 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 7
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.
Spoonacular Ingredients API
The Ingredients API from Spoonacular — 9 operation(s) for ingredients.
Spoonacular Meal Planning API
The Meal Planning API from Spoonacular — 12 operation(s) for meal planning.
Spoonacular Menu Items API
The Menu Items API from Spoonacular — 8 operation(s) for menu items.
Spoonacular Misc API
The Misc API from Spoonacular — 11 operation(s) for misc.
Spoonacular Products API
The Products API from Spoonacular — 11 operation(s) for products.
Spoonacular Recipes API
The Recipes API from Spoonacular — 42 operation(s) for recipes.
Spoonacular Wine API
The Wine API from Spoonacular — 4 operation(s) for wine.
Scroll within the panel for all 7 ·
Open Collections 1
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).
spoonacular 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.
Spoonacular 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.
Spoonacular Finops
FINOPSFeatures 8
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.
Recipe Search and Information
Complex multi-filter search, search by ingredients or nutrients, full recipe information, similar/random recipes, autocomplete, and analyzed instructions.
Nutrition Analysis
Compute and visualize nutrition for recipes, ingredients, products, and menu items including macro- and micronutrient breakdowns.
Ingredient Intelligence
Search ingredients, get information and substitutes, parse ingredient strings, compute conversions, and look up glycemic load.
Grocery Products
Search 800,000+ packaged food products by name or UPC, retrieve product information, compare products, and classify them.
Menu Items
Search and retrieve 100,000+ restaurant menu items with nutrition and autocomplete.
Meal Planning
Generate daily and weekly meal plans, build shopping lists, and manage meal plan templates.
Wine Pairing
Recommend wine pairings for dishes and recipes and return wine descriptions and recommendations.
Food Classification and Media
Classify food in images, search recipe videos, extract recipes from web pages, and return food jokes and trivia.
Scroll within the panel for all 8 ·
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.
Spoonacular 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.
Spoonacular API Rules
SPECTRALSpoonacular API Rules
SPECTRALJSON Schema 8
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.
ComparableProduct
JSON SCHEMAIngredientBasics
JSON SCHEMAIngredientInformation
JSON SCHEMAMenuItem
JSON SCHEMAProductInformation
JSON SCHEMARecipeInformation
JSON SCHEMASearchResult
JSON SCHEMATasteInformation
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
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.
Spoonacular Comparable Product Structure
JSON STRUCTURESpoonacular Ingredient Basics Structure
JSON STRUCTURESpoonacular Ingredient Information Structure
JSON STRUCTURESpoonacular Menu Item Structure
JSON STRUCTURESpoonacular Product Information Structure
JSON STRUCTURESpoonacular Recipe Information Structure
JSON STRUCTURESpoonacular Search Result Structure
JSON STRUCTURESpoonacular Taste Information Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 8
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 8 ·
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 4
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 and Cooking Apps
Power consumer cooking apps with searchable recipes, step-by-step instructions, and ingredient-based discovery.
Diet and Nutrition Tracking
Analyze meals and products for calories and nutrients to drive diet, fitness, and health applications.
Grocery and Shopping List Tools
Build shopping lists from meal plans and look up packaged products by name or UPC.
AI Cooking Assistants
Expose recipe, nutrition, and meal-planning operations to LLM agents through the official MCP server.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Model Context Protocol
Official spoonacular-mcp server exposes the API as MCP tools for AI assistants.
OpenAPI Generator
Official multi-language client SDKs are generated from the OpenAPI 3 spec with OpenAPI Generator.
RapidAPI
The Spoonacular API is also available through the RapidAPI marketplace.
Resources
Every other property we hold for Spoonacular — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
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/spoonacular · machine-readable index on apis.io