Generations

A generation is a single creation job. Every generation records the type of work, its current status, a progress value, the exact settings that were submitted, and a normalized snapshot of the result.

Types

Type	What it does
`TEXT_TO_3D`	Prompt to 3D geometry, then an optional texture pass.
`IMAGE_TO_3D`	One image to a textured mesh.
`MULTI_IMAGE_TO_3D`	Up to four images of the same object to a mesh.
`RETEXTURE`	Restyle the surface of an existing model.
`REMESH`	Rebuild geometry to a polygon budget.
`RIG`	Add a skeleton to a humanoid model.
`ANIMATE`	Apply a motion clip to a rigged model.

Status

Every generation moves through one state machine:

DRAFT → UPLOADING → QUEUED → IN_PROGRESS → SUCCEEDED | FAILED | CANCELED

state

Being assembled in the client, not submitted.

state

Input files are transferring.

state

Accepted and waiting for a worker.

state

Running. progress climbs from 0 to 100 with a stage label.

terminal

Done. An asset is available.

terminal

Could not complete. Credits are refunded automatically.

terminal

Stopped before completion.

DRAFT and UPLOADING are client-side only. The backend emits QUEUED onward.

Result shape

Responses are normalized. You never receive a raw engine payload.

{ "id": "gen_…", "type": "IMAGE_TO_3D", "status": "QUEUED", "progress": 0, "createdAt": "…" }

{ "id": "gen_…", "status": "IN_PROGRESS", "progress": 42, "stage": "Generating texture", "asset": null }

{
  "id": "gen_…",
  "status": "SUCCEEDED",
  "progress": 100,
  "asset": { "id": "ast_…", "thumbnailUrl": "…", "modelUrl": "…" }
}

Running in the background

A generation does not depend on the browser staying open. Once submitted it runs on the backend; progress is delivered by webhook, with polling as a fallback.

​Types

​Status

​Result shape

​Running in the background

Types

Status

Result shape

Running in the background