Skip to content
FLORA FLORA API

Generate without a Technique

Techniques are FLORA’s superpower — saved workflows with locked-in inputs and post-processing. But sometimes you just want a raw model run: a prompt, a model, an image. For that, the agent uses client.generations.create instead of a Technique. No slug, no saved workflow.

What you type

Section titled “What you type”

Generate 3 cinematic product shots of a ceramic mug on a sunlit table. Use a good image model, 4:3.

What the agent does

Section titled “What the agent does”

  1. Resolve a workspace and project

    Generations are billed to a workspace and attach to a project, so the agent first calls client.workspaces.list() and either picks an existing project (client.projects.list(...)) or creates one with client.projects.create(...).

  2. Pick a model

    The agent calls client.models.list({ type: "image" }) to find an available model_id and the parameters it accepts (aspect ratio, seed, etc.).

  3. Start the generation

    It calls client.generations.create(...) with type, prompt, workspace_id, project_id, the chosen model, and any model-specific params.

  4. Poll until complete

    Generations don’t have a saved-Technique run to poll, so the agent polls history: client.generations.list(...) (newest first), matches its run_id, and renders the outputs once status is completed.

What you see

Section titled “What you see”

The requested images render inline in the chat as each generation completes — same as a Technique run, just without a Technique behind them.

Techniques vs. generations

Section titled “Techniques vs. generations”
Technique runGeneration
Entry pointclient.techniques.runs.create(techniqueId, …)client.generations.create(…)
Needs a saved TechniqueYesNo
InputsThe Technique’s input schema (inputs[])type + prompt + optional model/params
Best forRepeatable, branded, multi-step workflowsOne-off, ad-hoc model runs
Post-processingBaked into the TechniqueNone — raw model output

Under the hood

Section titled “Under the hood”
  1. flora_list_workspaces and flora_create_project — resolve a workspace and a project; generations need both.
  2. flora_list_models with type: "image" — pick an image model.
  3. flora_create_generations — start the generation:
{
  "generations": [
    {
      "type": "image",
      "prompt": "a cinematic product photo of a ceramic mug on a sunlit table",
      "workspace_id": "<workspace_id>",
      "project_id": "<project_id>",
      "model": "<model_id>",
      "params": { "aspect_ratio": "4:3" }
    }
  ]
}
  1. flora_list_generations with run_ids: [run_id] — poll until the run completes and returns its output URLs.

Tips

Section titled “Tips”
  • type must be exactly one of image, video, audio, or text — not a model family like t2i or text-to-image.
  • model must be a model_id from client.models.list(...). If you see “Model … is not available”, list models for the same type and retry with one of the returned IDs. Omit model to use the workspace default.
  • workspace_id and project_id are both required. The generation shows up on that project’s canvas in FLORA.
  • Output URLs are long-lived but not permanent — download anything you need to keep.
Section titled “Related”