> ## Documentation Index
> Fetch the complete documentation index at: https://support.myapps.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What you can automate

> Exactly which parts of Pixio are reachable from an integration — and which aren't

Most of Pixio is scriptable, but not all of it. This page is the honest boundary, so you find out here rather than halfway through a build.

## Supported

<CardGroup cols={2}>
  <Card icon="wand-magic-sparkles" title="Generation">
    Start generations, estimate their credit cost before running, and check status and history.
  </Card>

  <Card icon="image" title="Assets">
    List, upload, import, fetch, download, and delete generated and uploaded media.
  </Card>

  <Card icon="layer-group" title="Model discovery">
    List models, inspect their parameters, and optimize prompts.
  </Card>

  <Card icon="coins" title="Account">
    Read credit balance, ledger, plan, and API limits.
  </Card>

  <Card icon="diagram-project" title="Workflows">
    List workflows already saved in Pixio and run them.
  </Card>

  <Card icon="grid-2" title="Boards & Canvas">
    Full project CRUD and operations for Boards, spatial canvas, and Canvas designs.
  </Card>

  <Card icon="film" title="Cinema & Cam View">
    Storyboard CRUD with prompt-to-storyboard direction; Cam View scene CRUD with prompt-to-keyed-scene direction.
  </Card>

  <Card icon="timeline" title="Agent & timeline projects">
    Persist chat and Video Agent projects; timeline project CRUD with validated editor operations.
  </Card>

  <Card icon="user-gear" title="Characters, prompts & training">
    Locked character CRUD, prompt history, and model-training status.
  </Card>
</CardGroup>

## Not supported

These are deliberately app-only. Don't design around them.

| Not available                                                          | Why it matters                                                             |
| ---------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| **Running Agent chat tools** through the internal streaming chat route | You can persist a conversation, but you can't drive the agent's tool calls |
| **Cam View controller pairing** and live sensor streaming              | Scene setup is scriptable; the live phone-as-camera link isn't             |
| **Headless timeline renders**, exports, and render progress            | You can build and edit a timeline; you can't trigger the final render      |
| **Autonomous Video Agent orchestration** and final assembly            | Project state is scriptable; the end-to-end autonomous run isn't           |
| **Starting or cancelling training jobs**                               | You can read training *status*, but jobs are started in the app            |

<Info>
  The pattern: **authoring and reading are open, long-running orchestration and live device links are not.** You can construct the work, then finish it in the app.
</Info>

## Planning around the gaps

<AccordionGroup>
  <Accordion title="I want a fully automated video pipeline">
    Generate clips through the API and assemble them yourself, or build the timeline via the API and do the final render in the app. Headless render isn't exposed.
  </Accordion>

  <Accordion title="I want to train a LoRA on a schedule">
    Not possible today — training starts in the app. You *can* poll training status and react when one finishes.
  </Accordion>

  <Accordion title="I want my own chat UI over Pixio">
    Build it on the generation endpoints directly rather than the internal chat route. You get the same models without depending on an unsupported surface.
  </Accordion>

  <Accordion title="I want the same chain every time">
    Build it once as a **workflow** in the app, then call it by ID. Cheaper than reimplementing the chain in your own code, and it stays in sync when you edit it.
  </Accordion>
</AccordionGroup>

## Reference

Every supported operation has its own page with parameters and a live playground, generated from the API's own specifications:

| Section                | Covers                                                                                                                        | Endpoints |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------- | --------- |
| **Pixio Integrations** | Generation, assets, models, credits, saved workflows                                                                          | 29        |
| **Pixio Project API**  | Boards, Canvas, Cinema storyboards, Cam View scenes, chat, Video Agent, editor projects, characters, prompt library, training | 55        |

`GET /capabilities` returns the supported surfaces programmatically, so an integration can check rather than assume.