spoonacular API

Name: spoonacular API API
Brand: spoonacular API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey99 EndpointsREST

For Agents

Programmatically search recipes, search recipes by ingredients. Covers 99 operations with apiKey authentication.

Quickstart

Get started with spoonacular API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search recipes"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with spoonacular API API.

Search Recipes

Get Recipe Information

Integrate spoonacular API into automated workflows

Query and filter spoonacular API records by parameters

Monitor spoonacular API operational status and events

GET STARTED

Start building with spoonacular API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for spoonacular API, keeping it validated and agent-ready.

The spoonacular Nutrition, Recipe, and Food API allows you to access over thousands of recipes, thousands of ingredients, 800,000 food products, over 100,000 menu items, and restaurants. Our food ontology and semantic recipe search engine makes it possible to search for recipes using natural language queries, such as "gluten free brownies without sugar" or "low fat vegan cupcakes." You can automat. The API exposes 99 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use spoonacular API API for, with concrete tasks.

★ E-Commerce Operations

Use the spoonacular API to perform e commerce operations programmatically. The API provides 99 endpoints covering core functionality including search recipes, search recipes by ingredients, search recipes by nutrients.

Call GET /recipes/complexSearch to search recipes

Automated ingredients Management

Automate ingredients operations by combining multiple spoonacular API endpoints. Agents can search recipes by ingredients and then search recipes by nutrients in a single workflow.

Call GET /recipes/findByIngredients to search recipes by ingredients, then verify the result

AI Agent Integration via Jentic

AI agents discover and call spoonacular API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'search recipes', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

99 endpoints — the spoonacular nutrition, recipe, and food api allows you to access over thousands of recipes, thousands of ingredients, 800,000 food products, over 100,000 menu items, and restaurants.

METHOD

PATH

DESCRIPTION

GET

/recipes/complexSearch

Search Recipes

GET

/recipes/findByIngredients

Search Recipes by Ingredients

GET

/recipes/findByNutrients

Search Recipes by Nutrients

GET

/recipes/{id}/information

Get Recipe Information

GET

/recipes/informationBulk

Get Recipe Information Bulk

GET

/recipes/{id}/similar

Get Similar Recipes

GET

/recipes/random

Get Random Recipes

GET

/recipes/autocomplete

Autocomplete Recipe Search

GET

/recipes/complexSearch

Search Recipes

GET

/recipes/findByIngredients

Search Recipes by Ingredients

GET

/recipes/findByNutrients

Search Recipes by Nutrients

GET

/recipes/{id}/information

Get Recipe Information

GET

/recipes/informationBulk

Get Recipe Information Bulk

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

spoonacular API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'search recipes') and Jentic returns the matching spoonacular API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct spoonacular API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using spoonacular API API through Jentic.

What authentication does the spoonacular API use?

The spoonacular API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I search recipes with the spoonacular API?

Yes. Use the GET /recipes/complexSearch endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the spoonacular API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I search recipes through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'search recipes'. Jentic returns the matching spoonacular API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the spoonacular API have?

The spoonacular API exposes 99 endpoints covering ingredients, meal planning, menu items operations.