Private-beta documentation

Understand what happens before you spend a credit.

This guide documents the account and production path currently exposed to beta users. Internal providers and secrets are intentionally not part of the public contract.

Access Production brief Credits Run states

01 / Access

Identity first, production second.

Create and verify an accountRegistration is paused until email delivery is validated.

identity

Request private-beta accessDescribe channels and expected workload.

review

Receive an approved role and creditsBoth are enforced server-side.

access

02 / Brief

Define the outcome and resource mix.

A run requires a title, meaningful production brief, duration from 1 to 60 minutes and production options. The browser never supplies the amount to charge.

Duration: preserved as a full-run requirement, including the tested 60-minute path.
Motion: controls planned motion-scene density.
Subtitles: optional and represented in the structured job configuration.
Thumbnail: optional and included in the estimate only when selected.

03 / Credits

Estimate, reserve, capture or release.

Estimate

The API uses active versioned pricing rules and returns a per-stage breakdown.

Reserve

Available credits move to reserved before the production worker provisions a run.

Capture

A successful terminal run captures the reservation once and records the ledger snapshot.

Release

Provisioning failure, cancellation or terminal failure releases the unused reservation once.

04 / States

Every run has a durable lifecycle.

Queued / provisioningCredits reserved; account, project and run linkage being created.

system

Running / review / blockedStage is active, needs a human decision or requires configuration.

control

Completed / failed / cancelledTerminal state triggers the matching credit action.

ledger