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

# Quick Start

**Quickstart Guide**

Welcome to the Quickstart guide for Livy.AI. This section will guide you through the initial steps to get your platform up and running, from account creation to your first content generation.

**1. Creating an Account:**

To start, visit the Livy.AI homepage and click "Sign Up". You'll need to provide some basic information, including your name, email address, and a secure password. Once you've agreed to the terms of service and privacy policy, click on "Create Account". You'll receive an email to verify your account.

**2. Logging In:**

After verifying your email, you can log in to your account from the Livy.AI homepage. Just click on "Log In" and enter your email and password.

**3. Navigating the Dashboard:**

Once logged in, you'll be taken to your personal dashboard. This is where you can manage your projects, view analytics, and access various features of Livy.AI. Take some time to familiarize yourself with the layout and functions.


---

# 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.livy.ai/getting-started/quick-start.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.