Skip to main content
Capabilities are priced in credits, drawn from your workspace balance. Reading and managing records — projects, Brands, campaigns, jobs, themes, usage — is free; generating something costs credits. Buy credits and choose a plan on the pricing page.

Read live prices

GET /v1/capabilities returns every capability with its current price, whether it can run right now, and your balance. Prices come from the same table charges are taken from, so the catalogue and your bill always agree. Reading it is free.
Each entry carries id, method, path, credits, available, and — for capabilities that return a job — async: true. Some capabilities are priced per unit, such as per language-minute for translation or per output for footage edits; the price is per unit and the response reports the units counted.

What a call costs

Every paid response reports what happened to your balance:
  • credits is what was actually charged, not what was quoted.
  • creditBalance is your balance afterwards.
  • A call that fails before producing a usable result is free.
  • An async job that ends failed, cancelled or qa_failed after being charged is refunded.
  • Retrying with the same Idempotency-Key replays the first response and never charges twice. See Errors.

When you cannot spend

The balance check accounts for work already in flight, so parallel calls cannot all spend the same remaining credits.

Get a quote before you run

Operations that list the x-sigmora-quote-only and x-sigmora-max-credits headers in the API reference — currently the UGC Studio frame, animation and AI creator operations — support a two-step quote and run:
  1. Send the request with x-sigmora-quote-only: 1. Nothing runs and nothing is charged; the response carries a quote with credits, balance, sufficient and budgetCapped.
  2. Show the price, then send the same request with x-sigmora-max-credits set to the price you accepted. If the live price has risen above it, the call is refused with 400 invalid_request before any work starts, nothing is charged, and details carries required and maxCredits. Quote again and confirm the new price.
POST /v1/video/footage takes the same two steps as body fields instead: quoteOnly: true, then maxCredits. A live price above maxCredits is refused with 409 conflict, the response carries the new quote, and nothing is charged.
A quote does not use your idempotency key, so the run that follows it is the first real call with that key. Over MCP and in ChatGPT, priced tools follow the same pattern with a maxCredits argument: a call without it returns a quote and runs nothing. See Sigmora in ChatGPT.

Workflows that reserve credits

Some multi-step workflows quote their maximum cost up front and reserve it before they start. A content autopilot run, for example, reserves its whole creditQuote when it is accepted and refunds every step it does not complete. Variation batches and paid work proposed by Sigma return a quote you approve before anything runs.

Track usage

GET /v1/usage reports calls, errors and credits by capability, by key and by day. It defaults to the last 30 days and accepts from and to dates (YYYY-MM-DD). Any key can read it, including keys that cannot spend.
Response