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

# Start here

Learn about how the $CHEQ token operates

The $CHEQ token at a basic level is used for three core functions:

1. **Network decisions:** cheqd is a Delegated Proof of Stake network, where individuals can vote on network decisions via a decentralised governance framework.
2. **Identity writes:** $CHEQ can be used to write Decentralised Identifiers (DIDs) and DID-Linked Resources to the network. This write also includes a percentage of tokens burnt from the network.
3. **Credential Payments:** $CHEQ can be used to pay for decrypting on-ledger resources for the purpose of a Verifier paying a Credential Issuer. 

## Getting started

Learn about the different mechanisms of the $CHEQ token below:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Tokenomics</strong></mark></td><td>Understand how $CHEQ works at an economic level.</td><td><a href="/product/learning-docs/cheq/tokenomics.md">Tokenomics</a></td></tr><tr><td><mark style="color:blue;"><strong>Identity writes</strong></mark></td><td>Learn how $CHEQ can be used to create DIDs and DLRs.</td><td><a href="/product/learning-docs/cheq/identity-writes.md">Identity writes</a></td></tr><tr><td><mark style="color:blue;"><strong>Credential Payments</strong></mark></td><td>Undestand how $CHEQ can be used for incentivising credential adoption.</td><td><a href="/product/learning-docs/cheq/credential-payments.md">Credential Payments</a></td></tr></tbody></table>


---

# 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://docs.cheqd.io/product/learning-docs/cheq/start.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.