Queue-safe lifecycle
The create-upload-complete-poll flow lets client apps avoid long synchronous requests while the mocap job moves through queued, processing, and completed states.
MOTION CAPTURE API
Motion capture API for video jobs
Build async video mocap jobs with upload, polling, and downloadable motion outputs through the AIMoCap API.
For developers looking for a motion capture API instead of a manual-only mocap tool.
Short answer
AIMoCap provides an async motion capture API for creating video mocap jobs, uploading source video, polling status, and downloading completed motion outputs.
When to use AIMoCap
Use AIMoCap when a product workflow needs upload URLs, queued processing, result polling, v-credit accounting, and target-aware outputs such as Default or Unitree G1.
When not to use AIMoCap
Do not use this API when you need real-time live capture, synchronous per-frame solving, undocumented private targets, or hardware-ready robot control without downstream validation.
A motion capture API is useful when mocap needs to run inside another product, batch workflow, or internal tool rather than only inside a browser Studio.
AIMoCap uses an asynchronous job model: create a job, upload the video to the returned upload URL, complete the upload, poll for status, then download the available outputs.
The API path is intentionally separate from web Studio usage. API jobs use API v-credit and can be labeled separately in history so automated processing is not confused with manual Studio credits.
Developer-facing API boundaries
- The API is asynchronous; clients should poll job status rather than waiting for a single blocking response.
- Current public API targets are Default and Unitree G1.
- Default output is animation-oriented and can include downloadable FBX motion.
- Unitree G1 output is robot-oriented and should be validated in the downstream robotics or simulation environment.
- API v-credit is separate from web Studio credits.
- Trim start and end are optional; final validation uses AIMoCap-side source metadata rather than trusting user-provided file size.
- Supported FBX export FPS values are 24, 30, 60, and 120.
API integration facts
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Usage accounting boundary
API jobs consume API v-credit and should be displayed separately from web Studio credit usage, especially when the same account uses both interfaces.
Target-aware results
A single integration should request the output targets it actually needs; animation FBX output and Unitree G1 robot output are different artifacts.
Motion capture API lifecycle
01
Create an async job
Send a title, supported target IDs, optional trim fields, and export FPS. The response returns a job ID and an upload URL for the source video.
02
Upload and admit the source
Upload the video to the returned URL, then call complete-upload so AIMoCap can verify the source object, enforce file and plan limits, and place the job into the queue.
03
Poll and download outputs
Poll the job endpoint until completion. Download preview, FBX, or Unitree G1 motion output only when the requested target produced that artifact.
Common questions
Is the AIMoCap motion capture API synchronous?
No. It is designed as an async job API. Create the job, upload source video, complete the upload, poll status, and download outputs after completion.
Which targets can API jobs request?
The current public API target set includes Default and Unitree G1. Clients should request only the targets needed for their workflow.
When are API v-credits charged?
API v-credit is tied to API job processing and remains separate from web Studio credits. System-side failures should be handled by the API lifecycle and ledger logic rather than mixed with manual Studio usage.
Can the API return both animation and robot outputs?
A job can request supported targets, but each output type has a different downstream purpose. FBX is animation-oriented, while Unitree G1 output is robot-oriented.
Should clients send file size or duration as trusted billing values?
No. Clients can provide helpful metadata when documented, but AIMoCap validates source size and duration through the upload and processing lifecycle.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.
Sources reviewed
Competitor details are summarized from public official pages and public community or review discussions. Community feedback is treated as directional signal, not as a universal product claim.