> 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 user guide for MOVIN TRACIN, TRACIN for Stage, and MOVIN Studio - this help center covers the full workflow: connection, calibration, capture, retargeting, export. (ENG/KOR)

Hello there! Welcome to MOVIN, real-time 3D motion capture, Markerless and Limitless. \
Powered by LiDAR and on-device AI, MOVIN turns real movement into live 3D motion, no suits, markers, or wearables required.

Our Mission is bold: **be the new standard for motion capture**, and we are moving full speed to get there.\
\
We are breaking the walls of traditional motion capture - complex setup, expensive equipment, and time-consuming data processing. With MOVIN, you can capture full-body motion data without any suits, markers - so you can go from setup to clean data in minutes, not days.

> 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.