Tandoor Recipes

Tandoor Recipes is an open-source, self-hostable recipe management, meal planning and shopping-list application built on Django and django-rest-framework, developed in Falkensee, Germany and offered both as freely self-hosted software (Docker, Kubernetes, Unraid, Synology, TrueNAS) and as a paid hosted service at app.tandoor.dev. Every feature of the product is driven by one REST API — recipes, steps, ingredients, foods, units, unit conversions, properties and nutrition, keywords, meal plans, meal types, shopping lists and shopping-list entries, supermarkets and supermarket category ordering, pantry inventory, recipe books, cook/view logs, spaces and households, user preferences, invite and share links, storage backends and external recipe sync, import/export of a dozen recipe formats, URL/image/PDF recipe scraping, an AI import and property-extraction pipeline routed through LiteLLM, and the Open Data food/unit/store reference database. The API is described by a live drf-spectacular OpenAPI 3.0.3 document served without authentication at /openapi/ on every instance, covering 244 paths and 462 operations across 244 component schemas, and it is the same contract the official Vue 3 frontend is generated against.

Tandoor Recipes publishes 1 API on the APIs.io network: Tandoor API. Tagged areas include Recipes, Meal Planning, Food, Nutrition, and Shopping Lists.

Tandoor Recipes’ developer surface includes documentation, getting-started guide, support, pricing, signup flow, changelog, authentication, and 22 more developer resources.

62.0/100 strong Agent 28/100 agent aware Full breakdown ↓
scored 2026-08-27 · rubric v0.15.1
1 APIs
RecipesMeal PlanningFoodNutritionShopping ListsOpen SourceSelf-HostedHome AutomationDjangoOpen Data

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-27 · rubric v0.15.1
Composite quality — 62.0/100 · strong
Contract Quality 8.2 / 21
Developer Ergonomics 9.3 / 17
Access Clarity 13.0 / 17
Operational Transparency 8.7 / 11
Contract Governance 3.1 / 10
Discoverability 5.8 / 9
Regulatory Posture 8.6 / 15
Agent readiness — 28/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
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/tandoor: 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.

Tandoor API

The single REST API behind Tandoor Recipes, generated by django-rest-framework and described by a drf-spectacular OpenAPI 3.0.3 document. 244 paths / 462 operations covering rec...

Pricing Plans 1

Published pricing tiers and plan structures.

Tandoor Plans Pricing

5 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Tandoor Rate Limits

3 limits

RATE LIMITS

Security Posture 3

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

Tandoor Authentication

3 schemes

SECURITY

Tandoor Domain Security

TLSv1.3 · DMARC

SECURITY

Tandoor Vulnerability Disclosure

disclosure policy published

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: tandoor
name: Tandoor Recipes
description: Tandoor Recipes is an open-source, self-hostable recipe management, meal planning and shopping-list application
  built on Django and django-rest-framework, developed in Falkensee, Germany and offered both as freely self-hosted software
  (Docker, Kubernetes, Unraid, Synology, TrueNAS) and as a paid hosted service at app.tandoor.dev. Every feature of the product
  is driven by one REST API — recipes, steps, ingredients, foods, units, unit conversions, properties and nutrition, keywords,
  meal plans, meal types, shopping lists and shopping-list entries, supermarkets and supermarket category ordering, pantry
  inventory, recipe books, cook/view logs, spaces and households, user preferences, invite and share links, storage backends
  and external recipe sync, import/export of a dozen recipe formats, URL/image/PDF recipe scraping, an AI import and property-extraction
  pipeline routed through LiteLLM, and the Open Data food/unit/store reference database. The API is described by a live drf-spectacular
  OpenAPI 3.0.3 document served without authentication at /openapi/ on every instance, covering 244 paths and 462 operations
  across 244 component schemas, and it is the same contract the official Vue 3 frontend is generated against.
url: https://raw.githubusercontent.com/api-evangelist/tandoor/refs/heads/main/apis.yml
image: https://raw.githubusercontent.com/TandoorRecipes/recipes/develop/docs/logo_color.svg
x-type: company
x-source: harvest:health-device-stack
specificationVersion: '0.20'
created: '2026-08-27'
modified: '2026-08-27'
tags:
- Recipes
- Meal Planning
- Food
- Nutrition
- Shopping Lists
- Open Source
- Self-Hosted
- Home Automation
- Django
- Open Data
tags_raw:
- recipes
- meal-planning
- food
- nutrition
- shopping-lists
- open-source
- self-hosted
- home-automation
- django
- open-data
apis:
- name: Tandoor API
  description: The single REST API behind Tandoor Recipes, generated by django-rest-framework and described by a drf-spectacular
    OpenAPI 3.0.3 document. 244 paths / 462 operations covering recipes, steps and ingredients, foods, units and unit conversions,
    properties and nutrition, keywords, meal plans, shopping lists, supermarkets and category ordering, pantry inventory,
    recipe books, spaces and households, user preferences and permissions, invite/share links, external storage sync, import/export,
    URL and AI recipe import, and the Open Data reference database. Authentication is by an access token sent in the Authorization
    header (ApiKeyAuth in the spec) or by session cookie; page/page_size cursorless pagination is used on every list endpoint.
  humanURL: https://docs.tandoor.dev/
  baseURL: https://app.tandoor.dev/api/
  tags:
  - Recipes
  - Meal Planning
  - Food
  - Nutrition
  - Shopping Lists
  - Open Source
  - Self-Hosted
  - Open Data
  tags_raw:
  - recipes
  - meal-planning
  - food
  - nutrition
  - shopping-lists
  - open-source
  - self-hosted
  - open-data
  properties:
  - type: OpenAPI
    url: openapi/tandoor-api-openapi.yml
  - type: OpenAPI
    url: https://app.tandoor.dev/openapi/
  - type: Documentation
    url: https://docs.tandoor.dev/
  - type: Authentication
    url: authentication/tandoor-authentication.yml
  - type: Conventions
    url: conventions/tandoor-conventions.yml
  - type: DataModel
    url: data-model/tandoor-data-model.yml
  - type: Overlay
    url: overlays/tandoor-api-overlay.yaml
common:
- type: DomainSecurity
  url: security/tandoor-domain-security.yml
- type: Website
  url: https://tandoor.dev
- type: DeveloperPortal
  url: https://docs.tandoor.dev/
- type: Documentation
  url: https://docs.tandoor.dev/
- type: GettingStarted
  url: https://docs.tandoor.dev/install/docker/
- type: Support
  url: https://tandoor.dev/support/
- type: HelpCenter
  url: https://community.tandoor.dev/
- type: GitHubOrganization
  url: https://github.com/TandoorRecipes
- type: SourceCode
  url: https://github.com/TandoorRecipes/recipes
- type: Pricing
  url: https://tandoor.dev/#pricing
- type: SignUp
  url: https://app.tandoor.dev/accounts/signup/
- type: Login
  url: https://app.tandoor.dev/accounts/login/
- type: TermsOfService
  url: https://tandoor.dev/terms/
- type: PrivacyPolicy
  url: https://tandoor.dev/privacy/
- type: StatusPage
  url: https://status.tandoor.dev/status/tandoor
- type: ChangeLog
  url: https://github.com/TandoorRecipes/recipes/releases
- type: ChangeLog
  url: changelog/tandoor-changelog.yml
- type: Security
  url: https://github.com/TandoorRecipes/recipes/security/policy
- type: Plans
  url: plans/tandoor-plans-pricing.yml
- type: RateLimits
  url: rate-limits/tandoor-rate-limits.yml
- type: Packages
  url: packages/tandoor-packages.yml
- type: Lifecycle
  url: lifecycle/tandoor-lifecycle.yml
- type: Conformance
  url: conformance/tandoor-conformance.yml
- type: LLMsTxt
  url: llms/tandoor-llms.txt
- type: Authentication
  url: authentication/tandoor-authentication.yml
- type: Conventions
  url: conventions/tandoor-conventions.yml
- type: DataModel
  url: data-model/tandoor-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: VulnerabilityDisclosure
  url: security/tandoor-vulnerability-disclosure.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-08-27'
  status: enriched
  artifacts_added: 17
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/tandoor"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/tandoor/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/tandoor/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.