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

# Sigmora API

> Whole pipelines as single calls. Describe an object and get an animated 3D render; send raw footage and get an edited cut; hand over a transcript and get it captioned and dubbed with the cue timing intact.

## Three ideas cover almost everything

<CardGroup cols={3}>
  <Card title="Projects" icon="folder" href="/projects">
    The container your work lands in — the script, the footage, the renders and
    the thread that produced them.
  </Card>

  <Card title="Capabilities" icon="bolt" href="/api-reference/meta/what-this-deployment-can-serve-and-what-it-costs">
    One call that runs a whole pipeline. No orchestration on your side.
  </Card>

  <Card title="Jobs" icon="clock" href="/jobs">
    How you collect the result of the long-running ones. One endpoint, whatever
    produced the work.
  </Card>
</CardGroup>

## Your first call

`text.script` takes a seed video and returns a researched, fact-checked script —
`sourceUrl` is the video it watches, and every capability names the project it
files its output under.

```bash theme={null}
curl -X POST https://api.sigmora.org/v1/text/script \
  -H "Authorization: Bearer $SIGMORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"prj_...","sourceUrl":"https://www.youtube.com/watch?v=..."}'
```

<Card title="Quickstart" icon="rocket" href="/quickstart" horizontal>
  Get a key, read the live catalogue, create a project, run a capability.
</Card>

## The same API the dashboard uses

Our own frontends call the routes documented here — there is no private door
with extra capabilities. When you list your projects through this API you are
reading the same containers the dashboard shows, because it is the same API
underneath.

<Note>
  Every field, type and enum on these pages is read out of the schemas the routes
  validate against, so this reference cannot describe a shape the API would
  reject.

  It documents everything Sigmora sells. What a given host will run **right now**
  is a narrower question, and it is answered by that host: fetch
  [`https://api.sigmora.org/v1/openapi.json`](https://api.sigmora.org/v1/openapi.json)
  for the live description of that deployment, or `GET /v1/capabilities` for the
  same answer with prices and your balance attached. Capabilities that exist but
  are served elsewhere are routed here too, and say so with
  `503 capability_unavailable` rather than pretending the path does not exist.
</Note>