Skip to main content
Works with Personal and Team keys. Create a key first.

1. Start generation

The response is 202 Accepted. Save the job_id:
Use a new Idempotency-Key for each asset you want, and reuse it only to retry that same request. Team keys must send one. See Retry generation safely.

Request fields

Write a good prompt

Be specific about the things a simulator cares about:
  • Size: “60 cm tall”, “fits in one hand”, “standard 16 cm cereal bowl”.
  • Moving parts: “two doors on vertical hinges”, “a drawer that slides out 30 cm”, “a lid that flips open”.
  • Materials and look: “brushed steel handles”, “matte black plastic”, “worn oak”.
Use interactions when a task depends on a specific motion:
Interactions guide how the parts, joints and colliders are built and checked. They are not a guarantee of how the asset will behave under arbitrary forces in your simulator. To generate from a photo:
Replace the example URL with a public image. For local files or several views, see Reference images.

2. Wait for the result

Poll every 30 to 60 seconds until job.status is succeeded, failed or cancelled. Most assets take 10 to 50 minutes; estimated_seconds is a rough guide, not a deadline. While the job runs, result is null. On success:
Responses include more fields than shown here. Use result.asset.id as the asset ID. If the job failed, read job.error. Personal keys can also stream progress instead of polling.

3. Download the result

The response is the file itself. See Downloads & bundle formats for every format and what is inside the GLB bundle.

Endpoint reference

Generate an asset · Get job status · Export an asset For many assets at once, use a batch.