Async lifecycle
The public API is designed around create, upload, complete-upload, poll status, and download, so long-running mocap jobs do not block client requests.
MOCAP API
Video mocap API for async motion jobs
Use the AIMoCap video mocap API to create async jobs, upload source video, poll status, and download FBX or robot motion outputs.
For developers looking for an API-driven video mocap pipeline.
Short answer
AIMoCap provides an async mocap API for creating jobs, uploading video, polling status, and downloading supported motion outputs.
When to use AIMoCap
Use it when mocap must fit into a product workflow with upload URLs, status polling, result downloads, and API v-credit accounting.
When not to use AIMoCap
Do not use the API when you need synchronous frame-by-frame processing or a private custom target that has not been prepared for your account.
The AIMoCap API is designed for production integrations that need asynchronous video mocap jobs instead of manual browser-only workflows.
Developers can create a job, upload video to the returned upload URL, complete the upload, poll job status, and download available outputs.
This makes the API page different from a generic product page: it should help an engineer understand job state, supported targets, billing units, and failure boundaries before writing client code.
Current public API support
- Current public targets are Default and Unitree G1.
- FBX export FPS supports 24, 30, 60, and 120.
- API v-credit is separate from web Studio credits.
- Trim fields are optional; if no trim end is provided, AIMoCap resolves the processing window from the uploaded source video.
- The API is asynchronous by design, so clients should persist the job ID and poll status rather than wait on a single long request.
API integration facts
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Multi-target jobs
A single API job can request supported targets such as Default and Unitree G1 when the account and job limits allow it.
Separate accounting
API jobs use API v-credit, while browser Studio jobs use web credits; this keeps product integrations and manual use easier to audit.
Result retrieval
Client code should be prepared to download different result artifacts depending on requested targets, such as FBX for Default output or robot-oriented data for Unitree G1.
API integration flow
01
Create a job
Send job metadata such as title, supported target IDs, optional trim fields, and export FPS.
02
Upload and complete
Upload the source video to the provided upload URL, then call complete-upload so AIMoCap can queue processing.
03
Poll and download
Poll the job status and download available FBX, preview video, or Unitree G1 robot motion output when complete.
04
Separate API accounting
Track API v-credit separately from browser Studio credits so product usage, automated jobs, and manual Studio jobs can be audited independently.
Common questions
Can one API job request both Default and Unitree G1 outputs?
Yes. The API supports multiple target IDs in one job when the account and job limits allow it.
When are API v-credits used?
API usage is tracked with v-credit, which is separate from web Studio credits.
Where are API fields documented?
The API reference documents supported targets, trim fields, export FPS, upload, polling, and result download behavior.
Is the API synchronous?
No. AIMoCap API jobs are asynchronous: create the job, upload the video, complete the upload, poll status, and download results when processing finishes.
Do API jobs use the same credits as Studio?
No. API jobs use API v-credit, while browser Studio mocap jobs use web credits. This separation keeps automated product usage easier to track.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.