Input freedom
The API can be added to products that receive uploaded user video, without requiring a suit-based or marker-based capture setup at the point of recording.
MARKERLESS MOCAP API
Markerless mocap API
AIMoCap exposes a markerless video mocap API for supported targets, trim fields, export FPS, polling, and result download.
For teams integrating markerless mocap into an automated product flow.
Short answer
A markerless mocap API lets a product submit ordinary source video for async motion capture without asking users to wear suits, attach markers, or operate a capture volume.
When to use AIMoCap
Use AIMoCap when your workflow needs uploaded-video mocap jobs, supported output targets, trim controls, polling, and downloadable results inside an automated product flow.
When not to use AIMoCap
Do not use markerless mocap API as a promise of real-time capture, multi-person scene solving, cleanup-free animation, or robot-ready control data without downstream validation.
Markerless mocap API searches usually come from teams that want the capture step to disappear from the product workflow: users upload a video, the system processes it, and the app retrieves motion output later.
AIMoCap fits that model with an asynchronous job lifecycle. The client creates the job, uploads source video to the returned upload URL, completes the upload, polls status, and downloads the artifacts produced by the requested targets.
The important boundary is that markerless describes the input method, not a guarantee that every video is production-clean. Source quality, trim range, subject visibility, and downstream target validation still matter.
Markerless API boundaries
- Markerless means the source video does not require a mocap suit, optical markers, or a studio capture volume.
- The public API is asynchronous; clients should create, upload, complete, poll, and download instead of expecting a blocking response.
- Current public API targets include Default and Unitree G1.
- Default is animation-oriented; Unitree G1 is robot-oriented and should be validated downstream.
- Optional trim fields can limit the processed section, but final validation still happens in the AIMoCap-side processing lifecycle.
- API jobs consume API v-credit, separate from web Studio credits.
- Markerless input still depends on source quality: single-subject framing, visibility, lighting, and limited occlusion improve results.
Why markerless mocap API needs clear limits
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Async reliability
Queued processing, polling, and downloadable artifacts make the workflow safer for product integrations than a long synchronous request.
Output-specific handling
Markerless capture is only the input side. FBX animation, custom avatar output, and Unitree G1 robot data have different validation and downstream use cases.
Markerless mocap API workflow
01
Create a markerless video job
Send a title, supported target IDs, optional trim start/end, and export FPS when needed. The response gives the client a job ID and a source upload URL.
02
Upload without a capture rig
Upload ordinary video recorded without a mocap suit or optical markers, then call complete-upload. AIMoCap verifies the source, enforces account limits, and admits the job to the queue.
03
Poll and consume target outputs
Poll job status until completion. Use animation-oriented outputs for Default jobs, robot-oriented output for Unitree G1 jobs, and custom avatar outputs only after the avatar target is prepared.
Common questions
What does markerless mocap API mean?
It means the client can submit ordinary source video for motion capture processing without requiring a suit, optical markers, or a dedicated capture stage.
Is markerless mocap API real time?
No. AIMoCap uses an async job lifecycle with upload, queueing, polling, and downloadable results after processing.
Which videos work best for markerless mocap?
Single-subject clips with clear full-body visibility, stable framing, reasonable lighting, and limited occlusion are better candidates than crowded or heavily obstructed footage.
Can markerless mocap API return FBX or robot output?
A job can request supported targets. Default output is animation-oriented, while Unitree G1 is robot-oriented and should be validated in downstream robotics or simulation workflows.
Does markerless API usage use the same credits as Studio?
No. Public API jobs use API v-credit, which is tracked separately from web Studio credits.
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.