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

# What is Avis Creative Studio?

Avis Creative Studio is an AI movie generator and filmmaking studio. Turn ideas into short films, trailers and micro-dramas, from previs to final cut.

Avis Creative Studio is an **AI-native creative production environment** for creative professionals and production teams. Studio connects image, video, audio, 3D, VFX and editing in one visual workflow, helping you turn ideas into content you can use in real projects, while keeping control over the creative process and your own signature in the work.

Use Avis Creative Studio as an AI movie generator and AI filmmaking studio. Turn an idea, script or reference into short films, trailers, micro-dramas and animation. Build a previs in 3D first, then generate and finish your shots in the same Canvas project.

Avis Creative Studio is the **creative application layer** of the Avis ecosystem. **Avis Gateway** provides the infrastructure for builders and businesses to access, integrate and operate AI models. Creative Studio is where creators directly make and finish their work.


---

# 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://docs.avis.net/avis-creative-studio/getting-started/what-is-avis-creative-studio.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.
