Recipe API

Recipe API is a B2B recipe and nutrition API providing structured recipes with comprehensive, USDA-backed nutrition data — 32 nutrients per recipe, structured preparation steps, and per-100g nutrition on individual ingredients. Beyond browsing and filtering an existing catalog by category, cuisine, dietary flag and macro, it will generate a new recipe with nutrition on demand, and generate food photography from a recipe. It positions itself as a lighter-weight alternative for developers who want clean recipe data without much setup, and publishes both an llms.txt and an official MCP server so that AI clients can use it directly. Self-serve from a free evaluation tier through to a paid scale tier, with a documented keyless quick-start call so a developer can try the API before signing up.

Recipe API publishes 1 API on the APIs.io network: Recipe API. Tagged areas include Recipes, Food, Nutrition, Ingredients, and Data.

Recipe API’s developer surface includes documentation, pricing, signup flow, authentication, and 8 more developer resources.

🌐 Visit website 📡 Source on GitHub
48.5/100 developing ▬ flat Agent 60/100 agent ready Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
1 APIs 1 MCP Servers
RecipesFoodNutritionIngredientsDataGenerative AIMCPAgents

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 48.5/100 · developing
Contract Quality 15.9 / 25
Developer Ergonomics 5.7 / 20
Commercial Clarity 15.3 / 20
Operational Transparency 4.1 / 13
Governance 0.0 / 12
Discoverability 7.6 / 10
Agent readiness — 60/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 4 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/recipe-api: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Recipe API

B2B Recipe API providing structured recipes with comprehensive nutrition data.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

recipe-api-mcp.yml

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Recipe Api Plans

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Recipe Api Rate Limits

4 limits

RATE LIMITS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Recipe Api Authentication

1 scheme

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Signup
Signup
 Login
Login

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LlmsText
LlmsText
 MCPServer
MCPServer

Access & Security 1

Authentication, authorization, and security posture

Authentication
Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits
RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans

Company 1

The organization behind the API

Website
Website

Source (apis.yml)

apis.yml Raw ↑ 
aid: recipe-api
url: https://raw.githubusercontent.com/api-evangelist/recipe-api/refs/heads/main/apis.yml
name: Recipe API
description: Recipe API is a B2B recipe and nutrition API providing structured recipes with comprehensive, USDA-backed nutrition
  data — 32 nutrients per recipe, structured preparation steps, and per-100g nutrition on individual ingredients. Beyond browsing
  and filtering an existing catalog by category, cuisine, dietary flag and macro, it will generate a new recipe with nutrition
  on demand, and generate food photography from a recipe. It positions itself as a lighter-weight alternative for developers
  who want clean recipe data without much setup, and publishes both an llms.txt and an official MCP server so that AI clients
  can use it directly. Self-serve from a free evaluation tier through to a paid scale tier, with a documented keyless quick-start
  call so a developer can try the API before signing up.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/recipe-api.png
created: '2026-08-03'
modified: '2026-08-03'
specificationVersion: '0.21'
type: Index
position: Producing
access: 3rd-Party
kind: contract
tags:
- Recipes
- Food
- Nutrition
- Ingredients
- Data
- Generative AI
- MCP
- Agents
apis:
- aid: recipe-api:recipe-api
  name: Recipe API
  description: B2B Recipe API providing structured recipes with comprehensive nutrition data.
  humanURL: https://recipe-api.com/docs
  baseURL: https://recipe-api.com
  tags:
  - Recipes
  - Nutrition
  - Ingredients
  - Discovery
  - Generative AI
  properties:
  - url: openapi/recipe-api-openapi.json
    type: OpenAPI
  - url: https://recipe-api.com/openapi.json
    type: X-OpenAPI-Source
  - url: https://recipe-api.com/docs
    type: Documentation
  - url: https://recipe-api.com/signup
    type: Signup
  - url: https://recipe-api.com/login
    type: Login
  - url: https://recipe-api.com/pricing
    type: Pricing
  - url: https://recipe-api.com/terms
    type: TermsOfService
  - url: https://recipe-api.com/privacy
    type: PrivacyPolicy
  - url: authentication/recipe-api-authentication.yml
    type: Authentication
  - url: plans/recipe-api-plans.yml
    type: Plans
  - url: rate-limits/recipe-api-rate-limits.yml
    type: RateLimits
  - url: mcp/recipe-api-mcp.yml
    type: MCPServer
  - url: https://recipe-api.com/llms.txt
    type: LlmsText
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
common:
- url: https://recipe-api.com
  type: Website
- url: https://recipe-api.com/docs
  type: Documentation
- url: https://recipe-api.com/pricing
  type: Pricing
- url: https://recipe-api.com/signup
  type: Signup
- url: https://recipe-api.com/login
  type: Login
- url: https://recipe-api.com/terms
  type: TermsOfService
- url: https://recipe-api.com/privacy
  type: PrivacyPolicy
- url: https://recipe-api.com/llms.txt
  type: LlmsText
- url: mcp/recipe-api-mcp.yml
  type: MCPServer
- url: plans/recipe-api-plans.yml
  type: Plans
- url: rate-limits/recipe-api-rate-limits.yml
  type: RateLimits
- url: authentication/recipe-api-authentication.yml
  type: Authentication
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
X-Discovery:
  date: '2026-08-03'
  method: probed
  note: Provider wrote in to info@apievangelist.com. Every surface below was fetched before the profile was written; nothing
    here is modelled on their behalf.
  findings:
  - surface: OpenAPI
    url: https://recipe-api.com/openapi.json
    http_status: 200
    real: true
    note: OpenAPI 3.0.3, 12 operations, 20 schemas, ApiKeyAuth, real server URL.
  - surface: LlmsTxt
    url: https://recipe-api.com/llms.txt
    http_status: 200
    real: true
  - surface: MCPServer
    url: https://recipe-api.com/api/mcp
    http_status: 401
    real: true
    note: Exists and is auth-gated; documented at /mcp.
  - surface: WellKnown
    url: https://recipe-api.com/.well-known/api-catalog
    http_status: 404
    real: false