---
title: "Recipe formats and deep links"
description: "Understand canonical operation names, argument order, JSON exports, and URL installation."
---

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

# Recipe formats and deep links

Serialize recipes preserve canonical internal operation names for compatibility across localized interfaces. Argument order follows each operation's declared schema.

## Export choices

- **Readable JSON** is preferred for review, documentation, and version control.
- **Compact JSON** minimizes transport size.
- **Deep links** open the workspace with a recipe and optionally input.

## Review rules

1. Resolve every operation by its canonical name.
2. Confirm positional arguments against the operation description.
3. Decode URL-escaped values before reviewing them.
4. Treat embedded input as potentially sensitive.
5. Test with a known harmless sample after import.

## Stable documentation

When documenting a production workflow, record the recipe, a redacted sample, expected output shape, failure conditions, and the date it was verified.

Source: https://help.serialize.dev/reference/recipe-formats/index.mdx