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

# Token

SHEERLUCK was deployed on 2nd January through Pump.fun

5% of supply was bought and vested through StreamFlow, you can find the link at [Official Links](/getting-started/quickstart.md).

**Purpose of the Token**

The token will be used to authenticate holders for access to all of Sheerluck features, along with revenue share from the profits / fees amassed by Sheerluck utilities.

The **token gating** is not live yet for marketing purposes, but will be live in near future.

There is no public information on how much tokens will be needed to access each feature.

The groups that want to continue using Sheerluck features will either have to hold certain amount of tokens depending on the group size or pay decided amount monthly as renewal (Which would be used for buyback), this has not yet been decided.

There is only one [official token](https://jup.ag/swap/SOL-DhteZLhKP6xPNcHVtdYvcE5FFcPN5smU7pxJw14Cpump), and there won't be any other tokens issued when we add support for other chains.


---

# 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.sheerluck.ai/getting-started/token.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.