> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/api/recipes.md).

# FLORA API recipes

End-to-end FLORA API recipes in TypeScript and the CLI: grids of variants, iterating on favorites, uploading your own files, and CSV batches.

Recipes are complete scripts for common jobs, built on the [TypeScript SDK](https://docs.flora.ai/api/quickstarts/typescript.md) (several also have a CLI version). Each one starts from a Technique you already have; read its inputs first, because every Technique defines its own.

* [Generate a grid](https://docs.flora.ai/api/recipes/generate-a-grid.md): run a Technique several times from one brief and lay the results out as a grid.
* [Iterate on outputs](https://docs.flora.ai/api/recipes/iterate-on-outputs.md): re-run a Technique with your favorite outputs as image references.
* [Upload an asset](https://docs.flora.ai/api/recipes/upload-an-asset.md): turn a local or hosted file into a FLORA URL you can pass to a run.
* [Batch from a CSV](https://docs.flora.ai/api/recipes/batch-from-csv.md): run a Technique per spreadsheet row with idempotency keys, parallelism and backoff.

Driving FLORA from an AI client instead of code? See the [FLORA MCP recipes](https://docs.flora.ai/mcp/recipes.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/api/recipes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
