FBX-specific target choice
A video-to-FBX integration should request animation-oriented output explicitly instead of assuming that every target returns the same artifact type.
VIDEO TO FBX API
Video to FBX API
Create video-to-FBX API jobs, upload source clips, poll status, and download outputs when processing completes.
For developers searching specifically for a video to FBX API.
Short answer
A video to FBX API should let a client create an async job, upload a source video, poll processing status, and download an FBX motion result when the job completes.
When to use AIMoCap
Use AIMoCap when your product needs automated video-to-FBX processing for animation review, internal tools, or batch workflows without sending users through Studio each time.
When not to use AIMoCap
Do not use this flow when you need real-time live capture, guaranteed cleanup-free character animation, or a robot-specific artifact instead of animation-oriented FBX output.
A video-to-FBX API page should answer a narrower question than a general mocap API page: can a developer upload video and programmatically retrieve an animation-friendly FBX result?
AIMoCap handles this as an asynchronous job lifecycle. The client creates the job, uploads the source clip to the returned upload URL, completes the upload, polls status, and downloads the result artifact after processing.
For FBX-focused integrations, request the Default target when you need animation-oriented output. Robot targets such as Unitree G1 are separate target-aware artifacts and should not be treated as generic FBX replacements.
Video-to-FBX integration facts
- AIMoCap API jobs are asynchronous; clients should poll status instead of waiting on a blocking request.
- Default is the animation-oriented target for FBX-focused workflows.
- Supported FBX export FPS values are 24, 30, 60, and 120.
- Trim start and end are optional fields; source validation happens through the upload and processing lifecycle.
- API jobs consume API v-credit, separate from web Studio credits.
- A job can request multiple supported targets, but FBX and robot outputs should be handled as different artifacts.
- The API is designed for uploaded source video, not live capture or frame-by-frame streaming.
Why this is not just a generic API page
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Pipeline-friendly FPS control
Export FPS belongs in the job request so downstream animation tools can receive motion at the cadence expected by the pipeline.
Separated usage accounting
API v-credit keeps automated video-to-FBX usage separate from browser Studio credit usage, which matters for product integrations and batch jobs.
Video to FBX API workflow
01
Create a Default-target job
Create an API mocap job with the target IDs your workflow needs. For animation-oriented FBX output, request the Default target and set the export FPS if your pipeline requires 24, 30, 60, or 120 FPS.
02
Upload and admit the video
Upload the source video to the returned URL, then call complete-upload. AIMoCap verifies the uploaded source, applies file and plan limits, and queues the job for processing.
03
Poll and download FBX
Poll the job endpoint until a terminal status. When the Default target completes successfully, download the FBX artifact and preview assets for downstream animation review.
Common questions
Can AIMoCap API convert video to FBX?
Yes. Create an async API job, request the animation-oriented Default target, upload the source video, poll status, and download the FBX result after completion.
Which target should I request for FBX output?
Use the Default target for animation-oriented FBX workflows. Robot-specific targets such as Unitree G1 produce different downstream artifacts.
Can I choose the FBX export frame rate?
Yes. The API supports documented export FPS values including 24, 30, 60, and 120.
Does video-to-FBX API usage consume Studio credits?
No. Public API jobs use API v-credit, which is tracked separately from web Studio credits.
Is the video-to-FBX API real time?
No. It is an asynchronous upload-and-process workflow designed for queued jobs, polling, and downloadable results.
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.