FBX ANIMATION API
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.
An FBX animation API should help animation tools request mocap processing, monitor async job state, and download animation-ready FBX output after processing.
Use AIMoCap when your product needs repeatable FBX motion generation from uploaded video for review, cleanup, prototyping, or downstream DCC/game-engine workflows.
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.
Use this matrix to decide whether FBX animation API should be implemented as an async AIMoCap API job, a manual Studio workflow, or a separate integration plan.
FBX API searches usually come from teams that need animation files, not only a status endpoint, so the page should explain file handling and downstream validation.
A client can successfully download FBX and still need downstream checks for scale, root motion, contact quality, retarget fit, and engine or DCC import behavior.
When a job requests multiple targets, clients should not assume every result is FBX. Handle Default animation output separately from robot or custom-target artifacts.
The useful audit trail includes source filename, trim range, export FPS, target IDs, job status, and downloaded file keys so bad outputs can be traced.
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
This page is for workflows that need downloadable animation motion, not robotics command data or live camera capture.
A preview artifact lets applications or operators inspect the solved motion before a pipeline commits to FBX import and cleanup.
Automated FBX animation jobs should be measured with API v-credit so product usage does not blend with web Studio credit activity.
FBX animation integrations should record whether the artifact was accepted, needed cleanup, failed import, or needed a better source clip.
Stateful job records make it possible to trace a source clip through upload, queue, processing, v-credit, result download, and downstream cleanup.
The strongest FBX integration records whether the downloaded file imports correctly in the receiving DCC or engine, not only whether a URL was returned.
Separating ready-for-blocking from needs-cleanup gives downstream artists and product users a clearer next action after the API job completes.
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.
After the job completes, use the preview output to inspect the motion before importing FBX into DCC tools, game engines, or internal review systems.
After download, check export FPS, skeleton mapping, scale, root motion, foot contact, and import behavior in the receiving DCC or engine before accepting the FBX.
API jobs consume API v-credit, which keeps automated animation processing separate from web Studio credit usage and manual mocap experiments.
Store job ID, source clip, trim range, target, export FPS, artifact URL, preview verdict, cleanup outcome, and any failed stage so reruns are traceable.
Before marking the FBX accepted, import it into the receiving DCC or engine and record whether skeleton scale, root motion, frame rate, and contact behavior match expectations.
Label whether the FBX is ready for blocking, needs animator cleanup, needs retargeting changes, or needs a better source clip so product users see the right next step.
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.
The workflow is related, but this page focuses on animation pipeline usage: export FPS, preview review, FBX import, cleanup boundaries, and API usage accounting.
AIMoCap documents FBX export FPS values of 24, 30, 60, and 120 for API job requests.
No. The API generates motion output, but production characters may still need review, cleanup, and retargeting checks in downstream tools.
Validate export FPS, skeleton mapping, scale, root motion, foot contact, import behavior, and whether cleanup is acceptable for the receiving character or engine.
A job can request supported targets, but robot artifacts such as Unitree G1 output should be handled separately from animation-oriented FBX output.
Store job ID, requested target, trim range, export FPS, upload status, terminal status, artifact URL, v-credit record, preview verdict, and downstream acceptance result.
Import the downloaded FBX into the receiving DCC or engine and check skeleton scale, root motion, frame rate, foot contact, and whether the result can enter cleanup or blocking.
Use labels such as ready for blocking, needs cleanup, needs retargeting review, import failed, or recapture source clip instead of treating every downloaded FBX as equally production-ready.
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.
Async job creation, upload, polling, and downloads.
Use output, limits, and accounting to evaluate fit.
Compare animation, preview, and robot artifacts.
Build async video mocap jobs with upload, polling, and downloadable motion outputs through the AIMoCap API.
Use target-aware AIMoCap API jobs when your integration needs robot motion output such as Unitree G1.
Create AIMoCap video-to-FBX API jobs, upload source clips, poll status, and download outputs when processing completes.
These related AIMoCap resources document the workflow boundaries, output formats, and implementation details referenced on this page.
