Named target selection
Unitree G1 should be requested as a target, so clients do not have to infer robot output from a generic animation result.
UNITREE G1 API
Unitree G1 motion API
Request Unitree G1 as an AIMoCap API target when your integration needs robot motion output from video.
For robotics developers searching for Unitree G1 motion data through an API workflow.
Short answer
AIMoCap lets API clients request Unitree G1 as a robot-oriented mocap target when turning uploaded video into target-aware motion output.
When to use AIMoCap
Use this workflow when your product needs a repeatable upload, queue, poll, and download flow for Unitree G1 motion data rather than a manual Studio-only process.
When not to use AIMoCap
Do not use the Unitree G1 API output as a direct robot command stream. Treat it as processed motion data that still needs downstream validation and control-layer adaptation.
The Unitree G1 API page is for developers who already know they want G1-oriented output, not just a generic robot motion endpoint.
AIMoCap uses a standard async API lifecycle: create a job with the Unitree G1 target, upload the source video, complete the upload, poll status, and download the completed artifacts.
Because this is an API workflow, usage is tracked with API v-credit and can be separated from web Studio motion capture jobs in account history and ledgers.
Unitree G1 API facts
- Unitree G1 is a public API target for robot-oriented output.
- The G1 target can be requested together with Default when a client needs both robot data and animation review.
- API v-credit is separate from web Studio credit.
- The workflow is asynchronous and should be polled until a terminal status.
- Source video upload and complete-upload happen before queue admission.
- G1 output should be validated in downstream robotics tooling before physical use.
- The public API is designed for uploaded video jobs, not real-time teleoperation.
What makes G1 integration different
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Dual-output option
A single job can request Default plus Unitree G1 when a pipeline needs previewable animation output and robot-oriented data from the same source clip.
Validation boundary
AIMoCap provides processed motion artifacts; the robotics application remains responsible for safety, simulation checks, and hardware-specific control.
Unitree G1 API workflow
01
Create a G1-targeted job
Create an API job and include the Unitree G1 target ID when the client needs robot-oriented output. Add Default only when the integration also needs animation review output.
02
Upload the source video
Upload to the returned upload URL and call complete-upload. AIMoCap validates the uploaded source and queues the job before the runner processes it.
03
Poll for G1 artifacts
Poll job status until completion, then download the available preview and Unitree G1 result artifact for downstream robotics validation.
Common questions
How do I request Unitree G1 output through the API?
Create an async mocap API job and include the Unitree G1 target ID in the requested target list. Then upload, complete, poll, and download results after completion.
Can the same job return Default and Unitree G1 outputs?
Yes. Request both supported targets when your integration needs animation review output and Unitree G1 robot-oriented output from one source video.
Is Unitree G1 API usage charged with web credits?
No. API jobs use API v-credit, which is tracked separately from web Studio credits.
Does AIMoCap control the Unitree G1 robot directly?
No. AIMoCap returns processed motion artifacts. Your downstream robotics stack should validate, adapt, and control any physical robot behavior.
Should I use Unitree G1 API or the general robot motion API page?
Use this page when you specifically need G1-targeted output. Use the general robot motion API page when comparing broader robot motion API workflows and boundaries.
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.