Skip to main content
Every completed MVNT job can expose multiple outputs: a preview MP4 video, motion files for 3D pipelines, and JSON metadata. After GET /job/{job_id} returns status: "completed", call the output endpoint that matches the artifact you need.

Output endpoints

Use the job_id returned by POST /generate-motion in each output path:
FormatEndpointTypical filename
Preview MP4GET /render-mp4/{job_id}preview.mp4
BVH motionGET /download-bvh/{job_id}motion.bvh
GLB motionGET /download-glb/{job_id}motion.glb
All output endpoints require your API key and are authenticated the same way as every other MVNT API request. Downloading an output does not consume additional credits.

Formats

The preview MP4 is a rendered video of the generated motion — a character performing the dance against a neutral background. It is the fastest way to see your generation result and is ready for immediate human review or display in a product UI.Endpoint
Download example
When to use preview MP4
  • Display motion generation results in your product UI without any 3D rendering on your side
  • QA and visual review before exporting to a motion file
  • Motion-transfer workflows where the MP4 is the input to a downstream model
  • ComfyUI preview nodes that accept video input
  • Partner model cards, demos, and product screenshots
Use the -L flag with curl to follow redirects if the endpoint returns one.

Output path parameter

job_id
string
required
The job ID returned by POST /generate-motion. Replace {job_id} with that returned value.

Choosing a format

FormatBest for
Preview MP4Product UI, QA, demos, ComfyUI
BVHBlender, retargeting, game engines
GLBWeb 3D, glTF pipelines, mesh-inclusive previews