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

# Getting started

Season 00 runs on invite codes. Get one from a friend who plays.

1. Sign in with Telegram, or with your wallet in the Android app or on a computer. You're on the waitlist.
2. Enter your [invite code](/beatking-docs/rewards/invite-codes.md). You're in.
3. Take your golden ticket to the MAKE-A-RIG Machine. It gives you your training rig.
4. Play your first song. It shows you how to play.

## Your training rig

The training rig is yours to keep, and it earns crowns. It earns up to 500 gems, and they count toward your first [mint](/beatking-docs/rewards/minting.md). You can't sell it or send it. You get more devices from minting and from other players.

## Waitlist players

If you joined the waitlist early, you get the DAY ONE HIFI, an epic device, when you get in, and 3 invite codes to bring your friends in. The DAY ONE HIFI is locked to your account and earns fully.

## Seeker and Saga owners

Own a Seeker or a Saga? Sign in with the wallet on your phone, or link it in your account later. You get the SEEKER BOOMBOX, an uncommon device, when you get in. It's locked to your account and earns fully.

## Wallet

On the web, your account comes with a wallet. In the Android app or on a computer, you can use your own wallet. You play on your phone; on a computer you can look around and trade. Top it up with SOL to buy things. You pay your own transaction fees.


---

# 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://beatking.gitbook.io/beatking-docs/getting-started.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.
