FBX is the integration artifact
This page is for workflows that need downloadable animation motion, not robotics command data or live camera capture.
FBX ANIMATION API
FBX animation API from video
Use AIMoCap API jobs to request Default output and download animation-ready FBX motion after processing.
For developers searching for an FBX animation API from source video.
Short answer
An FBX animation API should help animation tools request mocap processing, monitor async job state, and download animation-ready FBX output after processing.
When to use AIMoCap
Use AIMoCap when your product needs repeatable FBX motion generation from uploaded video for review, cleanup, prototyping, or downstream DCC/game-engine workflows.
When not to use AIMoCap
Do not position this as a full animation cleanup replacement. Generated FBX motion still needs review, retargeting checks, and downstream polish for production characters.
The phrase FBX animation API usually means a developer wants programmatic animation output, not a one-off browser export.
AIMoCap exposes this through async mocap jobs: create the job, upload the video, complete the upload, poll status, then download FBX output for the requested animation-oriented target.
This page focuses on FBX animation integration details: export FPS, result readiness, preview review, usage accounting, and where cleanup or character-specific retargeting remains outside the API response itself.
FBX animation integration facts
- FBX output is animation-oriented and should be requested through the Default target.
- The public API is asynchronous and should be polled until completed or failed.
- Supported export FPS values are 24, 30, 60, and 120.
- Preview output helps teams review motion quality before importing or retargeting FBX.
- API v-credit is separate from web Studio credits.
- Robot targets such as Unitree G1 produce different artifacts and should not be treated as animation FBX output.
- Generated FBX motion can reduce capture friction, but production animation may still need cleanup and target-specific retargeting review.
Animation-pipeline boundaries
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Preview-first review
A preview artifact lets applications or operators inspect the solved motion before a pipeline commits to FBX import and cleanup.
Clear credit separation
Automated FBX animation jobs should be measured with API v-credit so product usage does not blend with web Studio credit activity.
FBX animation API workflow
01
Create an animation-oriented job
Create an API job for the animation output your integration needs. For FBX animation workflows, use the Default target and set export FPS to match the downstream animation pipeline.
02
Use preview before consuming FBX
After the job completes, use the preview output to inspect the motion before importing FBX into DCC tools, game engines, or internal review systems.
03
Track API usage separately
API jobs consume API v-credit, which keeps automated animation processing separate from web Studio credit usage and manual mocap experiments.
Common questions
Can AIMoCap API return FBX animation output?
Yes. Request the animation-oriented Default target in an async API job, upload the video, poll for completion, and download the FBX result when available.
Is this different from a video-to-FBX API?
The workflow is related, but this page focuses on animation pipeline usage: export FPS, preview review, FBX import, cleanup boundaries, and API usage accounting.
Which export FPS values are supported?
AIMoCap documents FBX export FPS values of 24, 30, 60, and 120 for API job requests.
Does the API guarantee production-clean animation?
No. The API generates motion output, but production characters may still need review, cleanup, and retargeting checks in downstream tools.
Can the same job request robot output too?
A job can request supported targets, but robot artifacts such as Unitree G1 output should be handled separately from animation-oriented FBX output.
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.