---
title: "Durable Recipes"
description: "What AgentMQ Recipes guarantee and where their private runtime boundary begins."
image: "https://help.agent.mq/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.agent.mq/llms.txt
> Use this file to discover all available pages before exploring further.

# Durable Recipes

A Recipe is persisted automation dispatched to a deterministic native execution. AgentMQ's workflow engine remains the scheduler and execution owner; the private Recipe runtime maintains domain state and receipts.

## Why Recipes are separate

Workflow YAML describes execution. Recipe state describes the durable automation product behavior around that execution. Keeping the two separate prevents an internal scheduler or queue from creating a second source of truth.

## Boundaries

- `/v1/internal/recipes/dispatch` and `/v1/internal/recipes/runtime` are private bridges, not developer endpoints.
- A Recipe does not bypass application authorization, service connection limits, idempotency, or human approval.
- The presence of a retained adapter does not make an unfinished channel or transport public.

## See also

- [Deploy and publish a workflow](/automation/workflows)
- [Private and callback endpoints](/reference/private-endpoints)

Source: https://help.agent.mq/automation/recipes/index.mdx