> For the complete documentation index, see [llms.txt](https://help.movin3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.movin3d.com/movin-tracin/movin.md).

# MOVIN

Get started with MOVIN TRACIN: device connection, 3-second calibration, capture, retargeting, and export to .fbx and .bvh.

{% hint style="success" %}
MOVIN Studio has been updated with brand new features.\
For details, please refer to [What's New?](/movin-tracin/miscellaneous/whats-new.md) page.
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=FN8E385PfMo>" %}

MOVIN TRACIN is MOVIN’s flagship product, powered by our real-time, full-body markerless motion capture technology. With just a single device, you can capture studio-quality motion anytime, anywhere.

MOVIN TRACIN works together with its dedicated software, MOVIN Studio.\
This documentation will guide you through how to set up and use both components.

Once you get the hang of it, you can set everything up and start capturing in just 5 minutes!

Ready to get started?


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.movin3d.com/movin-tracin/movin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
