Soustack is a composable recipe data standard

Soustack defines a portable, machine-readable contract for recipes that need to be validated, extended, and reused across systems. Start with a minimal JSON recipe, then declare additional capabilities—like prep, scaling, timing, or storage—only when you need them.

Get started

Publish or consume recipes in minutes — no migration required.

Read the spec →

Real-world cooking, structured

Soustack defines a contract for computational recipes so applications can understand quantities, timing, preparation, equipment, and storage without guesswork.

The contract is composable: adopt only what you need via stacks, then upgrade incrementally when you're ready. Profiles declare what recipes can do, acting as trust badges for apps and users.

How Soustack fits with Schema.org

Soustack builds on Schema.org's vocabulary layer, adding an intelligence layer that enables validation, normalization, and task-ready views for computational recipes.

Web ContentHTML, CMS, source docsSchema.org — Vocabulary LayerShared semantics, SEO, interoperabilitySoustack — Intelligence LayerValidation, normalization, capability stacks, task-ready viewsApplicationsAI agents, RAG pipelines, planning toolsSchema.org defines what a recipe is. Soustack defines what you can do with it.

Getting started with Soustack

Soustack recipes can start small and grow incrementally. Follow these steps to get started:

  1. Get a recipe into Soustack

    Start with a minimal JSON recipe that establishes a portable envelope for interchange.

  2. See what it can do

    Understand how Soustack recipes can be validated, displayed, and consumed by applications.

  3. Upgrade capabilities

    Add stacks to declare additional capabilities like prep, scaling, timing, or storage when you need stronger guarantees.

  4. Import the rest

    Use ingestion tools to convert existing recipe formats into Soustack.

  5. Automate workflows

    Integrate Soustack recipes into automated systems and workflows using MCP and other tool interfaces.

Composable stacks

Recipes upgrade incrementally via optional capability modules. Stacks are monotonic: they add power, never remove expressiveness. Each stack is validated by schema and fixtures.

Profile-based adoption

Profiles are named conformance bundles that promise what apps and users can rely on. You don't need to start at the top—apps can support as much as they want, and recipes declare what they can do.

Execution-focused

Soustack supports real-world cooking: ingredient prep annotations, equipment requirements, scaling-aware calculations, timing and scheduling, and storage guidance for leftovers.

What to do next