> 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/welcome-to-movin.md).

# Welcome to MOVIN 🙌

Setup and usage guides for MOVIN TRACIN, TRACIN for Stage, and MOVIN Studio — connection, calibration, capture, retargeting, and export. English and Korean.

Hello there! Welcome to **MOVIN** — the world's simplest and fastest professional-grade markerless motion capture service.

The content market has evolved from text to images, and then to videos. \
*What's next?* Motion data that captures dynamic human movement is becoming the next frontier.

However, motion capture has traditionally faced major barriers:\
complex setup, expensive equipment, and time-consuming data processing.

We've developed a technology that allows you to capture full-body motion data without any additional wearables or markers.

Our mission is bold: to set the new standard for motion capture in the industry,\
and we’re moving full speed ahead to achieve it.

> If you want to see the instruction of MOVIN TRACIN,\
> please move to [MOVIN TRACIN | EN](https://help.movin3d.com/movin-tracin/) or [MOVIN TRACIN | KR](https://help.movin3d.com/movin-tracin-kr/).

> If you want to see the instruction of MOVIN TRACIN Stage,\
> please move to [MOVIN TRACIN Stage | EN](https://help.movin3d.com/movin-tracin-stage/) or [MOVIN TRACIN Stage | KR](https://help.movin3d.com/movin-tracin-stage-kr/).

*Shall we dive in?*


---

# 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/welcome-to-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.