FLORA

FLORA Runs API

Top-level run creation endpoints.

Documentation GitHub OpenAPI

Operations 4

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /runs/{runId} Check a run's status and outputs · Get a run #

Ask an LLM

“How do I check whether my generation or action run has finished?”

“Where do I get the output URLs once a run completes?”

Tell an agent

Get the status of run {runId}.

Fetch the output URLs for run {runId}.

POST /runs/action Run a prebuilt action headlessly · Start an action run #

Ask an LLM

“Can I run an action like rotate-image on an image URL without touching any canvas?”

“What inputs does a headless action run need, and is the project canvas changed by it?”

Tell an agent

Run action {action_id} headlessly on {inputs} in workspace {workspace_id} and project {project_id}.

Start a direct {action_id} run with inputs {inputs} and params {params}, billed to project {project_id} in workspace {workspace_id}.

POST /runs/generation Start a generation run on a project canvas · Start a generation run #

Ask an LLM

“How do I generate an image into a project canvas through the normalized runs resource?”

“Can a generation started under /runs use a specific model and parameters?”

Tell an agent

Start a {type} generation run on the canvas of project {project_id} in workspace {workspace_id} with prompt {prompt}.

Create a canvas generation run with model {model} for prompt {prompt}, type {type}, project {project_id}, workspace {workspace_id}.

POST /runs/technique Start a technique run via the top-level runs route · Start a top-level technique run #

Ask an LLM

“How do I start a technique run using the newer top-level runs endpoint?”

“Can I launch a technique by passing its ID in the body rather than the URL path?”

Tell an agent

Start a top-level run of technique {technique_id} in workspace {workspace_id} with inputs {inputs}.

Launch technique {technique_id} through /runs/technique for workspace {workspace_id} using inputs {inputs}.

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/flora-fauna:flora-fauna-runs-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Flora.ai Runs API
  version: 1.6.0
  license:
    name: Proprietary
    identifier: LicenseRef-Proprietary
  description: Top-level run creation endpoints.
servers:
- url: https://app.flora.ai/api/v1
security:
- bearerAuth: []
tags:


# --- truncated at 32 KB (97 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/flora-fauna/refs/heads/main/openapi/flora-fauna-runs-api-openapi.yml

FLORA Runs API

Operations 4

Documentation

Specifications

Other Resources

Work with this as data

MCP server

Tools for apis

Call it yourself

Get an API key

OpenAPI Specification