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

# Introduction

Motorica is a suite of tools for generating and iterating on 3D locomotion animation.

It allows animators to generate single takes, batch datasets, custom styles, and integrates with front-end engines and DCCs.

### What you’ll use

* [**Motion Stage**](/documentation/motion-stage.md): generate and export single-take locomotion animations.
* [**Motion Factory**](/documentation/motion-factory.md): generate locomotion datasets for motion matching pipelines.
* [**Style Cloning**](/documentation/style-cloning.md): build custom Styles from your own mocap.
* [**Integrations**](/documentation/integrations.md): plugins and tooling for Unreal and other front-end engines.

### Where to start

1. Open the app and get started: [Try Motorica Now!](https://app.beta.motorica.ai)
2. Learn the fundamentals: [Concepts](/learn/concepts.md)
3. Consult the docs to animate what you need: [Documentation](/documentation/overview.md)

{% hint style="info" %}
If you already know which product you need, start with our [Documentation](/documentation/overview.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.motorica.com/getting-started/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.