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

# Access and membership

**Kyela is free until membership launches.** There is no three-day cutoff during this period. You do not need a wallet or tokens to start using your inbox.

Open **My access** in the bot to check your current access.

## What happens when membership launches?

We will announce the membership terms and instructions before access changes. The planned holding requirement is **3,000,000 tokens**. The official token contract and verification steps will be published when membership opens.

Three-day trials are planned for the membership phase. They do not limit access during the current free period.

Do not identify a token by its name or ticker alone. There is no live membership contract in this guide, and no purchase is needed now.

Telegram sign-in and wallet verification are separate. Kyela's Telegram connection page never asks for a wallet recovery phrase or private key.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://kyela-inbox.gitbook.io/kyela-inbox-docs/access.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 `build a script that syncs our docs to a CMS` 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.