Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Move API review

#20 of 23 in Game Motion Capture Software

A developer-focused capture API with flexible models, retargeting, and broad exports.

7.2/10Editor score
Visit Move API
Move API7.2 Visit Move API

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Move API converts video footage into 3D motion-capture data through AI, physics, and biomechanics models. It is aimed at developers and studios building capture workflows into applications, games, and production pipelines. The service supports single-camera and multi-camera processing, configurable models, rig-based animation retargeting, job monitoring, webhooks, and API-key authentication. Its web and API delivery model makes it a fit for teams that want capture capabilities inside their own software rather than a standalone capture workspace.

The plan structure separates capture mode from model generation. The s1 and s2 plans provide single-camera processing, with s1 using a first-generation model and s2 using a quality-optimized model. The m1 and m2 plans add multi-camera processing with the same model distinction. rt1 is an enterprise-only real-time multi-camera model with multi-person tracking and streaming-oriented processing. The published pricing approach is usage-based rather than subscription-based, and the rt1 model is priced through sales contact. Teams should review expected processing volume and model requirements before selecting a tier.

Move API’s main advantage is its developer breadth. GraphQL, a Python SDK, Unity integration, and support for Unity and Unreal Engine give teams several ways to connect capture to existing workflows. Outputs span animation, scene, motion-data, and preview-video use cases, including FBX, GLB, USD, BVH, C3D, Blend, JSON, CSV, and video formats. Job status monitoring and webhooks also support asynchronous processing. Choose Move API when application integration, retargeting, multiple capture modes, and export flexibility matter most. Teams seeking a free starting tier, a simple fixed subscription, or real-time access without an enterprise plan should consider alternatives.

Move API pros and cons

  • Where it wins
    • Supports both single-camera and multi-camera motion capture
    • GraphQL, Python, Unity, and Unreal Engine integration options
    • Exports FBX, GLB, USD, BVH, C3D, Blend, JSON, CSV, and video
  • Where it doesn't
    • No free plan is available
    • Real-time multi-camera tracking is limited to the enterprise-only rt1 model
    • Usage-based pricing is less straightforward than fixed subscription tiers

Move API fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update