G1 artifact downloads successfully
Treat this as artifact availability, then run simulation or controller validation before marking it accepted.
Calling the API job successful and skipping robot-side validation.
UNITREE G1 API
Unitree G1 robot 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.
Related AIMoCap resources
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
- For the Unitree G1 API page, G1 is the named public target that clients request for robot-oriented output.
- The G1 target can be requested together with Default when a client needs both robot data and animation review.
- Unitree G1 API jobs use API v-credit separately 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.
- A production API client should treat completed G1 output as an artifact handoff, then record whether simulation or controller validation accepted, rejected, or modified the motion.
- If both Default and Unitree G1 are requested, keep animation review artifacts separate from robot artifacts in storage and UI labels.
- A G1 API result should be labeled by downstream outcome: accepted for validation, rejected by source quality, rejected by mapping, rejected by contact or balance, or rejected by controller tracking.
- If a G1 artifact is converted by another robotics tool, that conversion should be logged separately from the original AIMoCap output so errors can be traced.
- A source clip that passes Default animation review can still fail G1 validation because robot contact, balance, morphology, and controller assumptions are stricter than visual preview.
Unitree G1 API validation matrix
Use this matrix to decide whether a completed G1 API job is ready for downstream robotics work or needs source, target, or controller review.
Scenario
Recommended action
Watch for
Default output passes but G1 validation fails
Keep both artifacts separate and classify the G1 rejection as contact, balance, morphology, mapping, controller, or source-video ambiguity.
Using animation acceptance to approve robot-oriented data.
G1 artifact is converted downstream
Record the converter, schema assumptions, timing changes, controller version, and validation verdict as a separate handoff record.
Blaming AIMoCap output for a downstream conversion change that was not logged.
Unitree G1 API objections
Unitree G1 API searches are high-intent robotics searches, so the page should be explicit about target support, artifact handling, and safety boundaries.
G1 output should be versioned as an artifact
Store the job ID, source clip, trim range, target ID, and downloaded G1 artifact together so downstream robot tests can be reproduced.
Simulation is not optional
A generated G1 artifact should be tested in simulation or robot-specific tooling before hardware use because balance, contacts, and joint limits can fail after conversion.
Default and G1 outputs answer different questions
Request Default only when animation review or an FBX handoff is also needed; Unitree G1 output should be evaluated as robot-oriented motion data.
What makes G1 integration different
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
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.
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.
Operational trace
API integrations should preserve job state, requested target list, artifact identity, and validation result so failed clips can be retried without guessing what changed.
G1 validation packet
A reliable G1 API integration stores source clip, target list, artifact URL, conversion tool, simulator/controller version, contact result, and accepted or rejected status.
Multi-target separation
Default animation output and Unitree G1 output can come from the same job, but they should have separate artifact labels, acceptance criteria, and downstream owners.
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.
04
Store the robot handoff record
Persist the job ID, requested targets, source video metadata, result artifact URL, v-credit cost, and downstream validation status so retries and audits stay traceable.
05
Validate before robotics reuse
Record simulator or controller environment, artifact version, contact result, timing notes, and accepted/rejected status before a G1 output becomes reusable motion data.
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 the Unitree G1 API target control robot hardware 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.
What should an API client store after a G1 job completes?
Store the job ID, requested targets, downloaded artifact, v-credit cost, source clip reference, validation environment, acceptance status, and any reason for rejection or retry.
What makes a Unitree G1 API result accepted?
Acceptance should depend on downstream validation: simulator or controller environment, contact behavior, timing, mapping, conversion notes, and whether the artifact passes the robotics team's criteria.
Can Default success prove G1 success?
No. Default animation output and G1 robot-oriented output should be reviewed separately because robot validation has stricter contact, balance, morphology, and controller constraints.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.
Mocap API
Async job creation, upload, polling, and downloads.
API decision checklist
Use output, limits, and accounting to evaluate fit.
Output formats guide
Compare animation, preview, and robot artifacts.
AI mocap API for production pipelines
Use AIMoCap API v-credit, async jobs, and target-aware outputs to add AI video mocap to production tools.
Async mocap API job workflow
Understand the async job lifecycle for AIMoCap API jobs: create, upload, complete, poll, and download.
Custom avatar mocap API planning
Plan AIMoCap API usage around published custom avatar targets, web setup, and repeatable motion jobs.
Sources reviewed
These related AIMoCap resources document the workflow boundaries, output formats, and implementation details referenced on this page.