Three ideas cover almost everything
Projects
The container your work lands in — the script, the footage, the renders and
the thread that produced them.
Capabilities
One call that runs a whole pipeline. No orchestration on your side.
Jobs
How you collect the result of the long-running ones. One endpoint, whatever
produced the work.
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.
Quickstart
Get a key, read the live catalogue, create a project, run a capability.
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.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
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.