> For the complete documentation index, see [llms.txt](https://docs.avis.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avis.xyz/guide/get-started/avis-login-signup.md).

# How to login/ sign up

Logging in to Avis takes under a minute, you can use either a Google account or email verification, and the same flow creates your account the first time you use it. Once you're in, you can top up credits, create an API key, and start building.

Avis offers two ways to sign in, both available from the same screen:

* **Sign in with Google:** fastest if you already have a Google account.
* **Sign in with email verification:** a one-time code sent to your inbox, no password to remember.

## Getting to the Login Screen

**Step 1:** On the main page at **avis.xyz**, click the **Login** button.

<figure><img src="/files/d5FH3gdaJTABCxoo3xhU" alt=""><figcaption></figcaption></figure>

You'll be offered the two sign-in options:

<figure><img src="/files/tryiwFJnRHgVxecUSvy0" alt=""><figcaption></figcaption></figure>

***

## Sign In with Google

**Step 1:** Select **Sign in with Google**.

**Step 2:** Choose the Google account you want to use.

<figure><img src="/files/MYUTlrOJVy4nnyobodc3" alt=""><figcaption></figcaption></figure>

**Step 3:** Review the permissions and click **Allow** to grant access.

<figure><img src="/files/9nk4rMqeI9VRBvmmGUgg" alt=""><figcaption></figcaption></figure>

You're now signed in.

<figure><img src="/files/P1tcKXdeN4KARapT4eey" alt=""><figcaption></figcaption></figure>

***

## Sign In with Email Verification

**Step 1:** Enter the email address you want to use, then continue.

<figure><img src="/files/2qHD0pJTlL86OdbGdgJU" alt=""><figcaption></figcaption></figure>

**Step 2:** Check your inbox for the verification code, enter it, and confirm.

<figure><img src="/files/Y07D1iKLexmt3dmWD3ov" alt=""><figcaption></figcaption></figure>

You're now signed in.

<figure><img src="/files/PGnJynYx5qn8cWAaeihl" alt=""><figcaption></figcaption></figure>

**Tip:** If the verification email doesn't arrive within a minute, check your spam folder and confirm you entered the address correctly before requesting a new code.

**Note:** Whichever method you choose the first time becomes the way you log back in. Signing in with Google and signing in with the same address by email create separate accounts, so pick one method and stick with it.

***

## What's Next

Once you're signed in, head to your profile to get set up:

* Add credits to your balance, see [How to top up your balance](/guide/get-started/avis-topup.md).
* Create an API key to start building, see [How to get API Key](/guide/get-started/avis-api-key.md).

***

## FAQ

### Do I need a password to use Avis?

No. Avis uses Google sign-in or a one-time email verification code, so there's no password to set or remember.

### Can I switch from email login to Google login later?

They're treated as separate accounts. To keep one balance and history, always sign in with the same method you used when you first created your account.

### I didn't receive my verification code — what should I do?

Check your spam folder first, confirm the email address is correct, then request a new code. Codes are time-limited, so use the most recent one.


---

# 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.avis.xyz/guide/get-started/avis-login-signup.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.
