> 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/rewards/invite-codes.md).

# Invite codes

Season 00 runs on invite codes. Sign in and you're on the waitlist. Enter a code and you're in.

## Getting codes

Runs drop codes. Play properly and you'll have some to share. You don't need to be the best, but you do need to actually play. A run with almost no hits drops none.

You hold up to 3 unused codes at a time. Share one and the next good runs can drop another.

## Sharing a code

Tap a code in your account to share it. Your friend gets a link that opens BEATKING and fills the code in after they sign in. Each code works once.

Codes are yours alone. You can't sell or trade them.

## Inviting pays

When a player who used your code plays, you get a plug bonus: 3 extra crowns for every 100 they earn. It comes on top, so your friend keeps all of theirs.


---

# 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/rewards/invite-codes.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.