Skip to Content
supedocs

Recipes

Jobs of several steps, written down once.

A recipe is a job of several tool calls, written down: its inputs and its steps, each step a tool id and its input. "Product photo to video ad" or "research a company and email its CEO" are recipes.

Find one

supe recipes "product photo to video ad"   # search the Cookbook and your own
supe recipes                               # just your own
supe recipe <id>                           # its inputs and steps

Some recipes have tiers, like a budget and a premium version: supe recipe <id> --tier budget.

Follow one

Each step is an ordinary supe run. Fill {{inputs.name}} with the job's inputs and {{steps.<id>.<field>}} with an earlier step's answer. Open one run for the whole recipe so it has one budget and one receipt.

Any text a step needs, like a summary, an email or a script, the agent writes itself. Recipes have no step that writes text.

Community recipes in the Cookbook aren't checked by supe. Read the steps before running one.

Keep or write one

supe recipe save <id>          # copy a Cookbook recipe into your workspace
supe recipe save -f recipe.json   # write your own: name, description, inputs, steps

Saved recipes show up on the dashboard under Recipes.

Over HTTP: GET /v1/recipes?query=, GET /v1/recipes/{id}, POST /v1/recipes. Over MCP: find_recipe, get_recipe, save_recipe, and the recipe prompt.

On this page