API Overview

What the API is for

The AIMoCap API is built for:

• internal production pipelines
• creator tools
• enterprise integrations
• robot motion automation workflows

The API is asynchronous. A typical flow is:

1. create a mocap job
2. upload the source video
3. complete upload admission
4. poll job status
5. download the finished result

Output targets

The API currently supports these target types:

• default
• unitree_g1
• avatar:{avatarId}

Output formats depend on the target:

• default -> fbx
• unitree_g1 -> robot_motion_json
• avatar:{avatarId} -> fbx

API key and billing

The API uses a dedicated API key and a dedicated v-credit balance.

• API billing is separate from normal web membership credits
• 1 v-credit = 1 second of video
• requests are admitted only when your API account is active and within plan limits

Read the detailed docs next:

• Authentication
• Reference
• Pricing