Target-aware output
A robot motion integration should request the robot target explicitly instead of assuming that any animation file can be used as a robot motion artifact.
ROBOT MOTION API
Robot motion API for video mocap
Use target-aware AIMoCap API jobs when your integration needs robot motion output such as Unitree G1.
For robotics teams searching for an API that can produce robot motion data from video.
Short answer
A robot motion API should turn source video into target-aware motion artifacts that can be reviewed, downloaded, and validated in a robotics pipeline.
When to use AIMoCap
Use AIMoCap when your integration needs an async video mocap job that can request a robot-oriented target such as Unitree G1 alongside animation review outputs.
When not to use AIMoCap
Do not treat generated robot motion as a direct hardware control command; validate it in your simulation, retargeting, or robot control stack before any physical deployment.
Robotics teams often need motion data that starts from human video but ends in a target-specific format rather than a generic animation clip.
AIMoCap exposes this through the same async API lifecycle as other mocap jobs, while keeping robot-oriented output separate from browser-only Studio credits and manual workflows.
The practical benefit is not just an upload endpoint. It is the ability to request supported targets, poll job state, and download artifacts that downstream robotics tools can inspect before use.
Robot motion API boundaries
- The public robot-oriented API target is Unitree G1.
- Robot motion output is target-aware; it is not the same artifact as a generic FBX animation file.
- AIMoCap API jobs are asynchronous and should be polled until completed or failed.
- API jobs consume API v-credit, which is separate from web Studio credits.
- The API can support multi-target jobs such as Default plus Unitree G1 when the client needs both animation review and robot output.
- Generated robot motion should be validated downstream before hardware use.
- The public API is for uploaded source video, not real-time robot teleoperation.
Why this page is robot-specific
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Review before control
The API result is useful for robotics data and validation workflows, but physical robot execution remains the responsibility of the downstream control stack.
Separate API accounting
Because API v-credit is separate from web credit, automated robotics pipelines can track usage without mixing it with Studio mocap jobs.
Robot motion API workflow
01
Request robot-aware targets
Create a mocap API job with the supported target IDs your integration needs. For robot motion workflows, Unitree G1 is the public robot-oriented target to request.
02
Upload once, process asynchronously
Upload the source video to the returned upload URL and call complete-upload. AIMoCap verifies the source, applies account limits, and queues the job without requiring a blocking API call.
03
Download and validate outputs
After completion, download the available preview and target artifacts. Robot motion output should be checked in simulation, retargeting review, or the downstream control environment.
Common questions
Can AIMoCap API create robot motion from video?
Yes, for supported robot-oriented targets. The current public robot target is Unitree G1, requested through the async mocap API job workflow.
Is robot motion output the same as FBX?
No. FBX is animation-oriented, while robot motion output is target-aware and intended for downstream robotics validation or conversion workflows.
Can one API job request both Default and Unitree G1?
Yes, clients can request supported target IDs together when they need both animation review output and robot-oriented output from the same source video.
Does AIMoCap send commands directly to a robot?
No. AIMoCap provides processed motion artifacts. Robotics teams should validate and adapt those artifacts in their own simulation, retargeting, and control systems.
How is robot motion API usage billed?
Robot motion API jobs use API v-credit, which is tracked separately from web Studio credits and should appear as API usage in account ledgers.
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.