> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/en/userguide/signup/direct.md).
# Sign up on the website
Sign up for Charlla and enjoy a one-month free trial! Your free trial starts as soon as you sign up.
## Create your account
* Charlla website
Click **\[Get started]** at the top of the page.
* Email and platform page
In field 1, enter the work email you want to use to log in. Then click **\[Continue]** (2).
* Verification email sent
We've sent a verification email to the address you entered. Open the Charlla verification email in your inbox.
* Account creation page
In the verification email, click **\[Verify]**. This takes you to the page where you create your login account.
* Required information page
1. Fill in all the required information. The **\[Next]** button becomes active once you do.
2. Check the required terms. You must agree to them to sign up for Charlla.\
When you've checked all the required terms, click **\[Next]** (2).
* Welcome pop-up
When the Charlla tutorial starts, you're all signed up. Start by clicking **\[Upload Videos]**, then explore everything the Charlla player can do!
---
# 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://support.charlla.io/en/userguide/signup/direct.md?ask=&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.
