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

# $SZN Token

### $SZN and the SUZUNA product

**$SZN** is the native token of SUZUNA on BNB Chain.

**Total Supply:** 1,000,000,000 SZN

The token is designed around a direct connection to the SUZUNA product. Its initial role is not to introduce a collection of unrelated token mechanics, but to provide utility within the platform's paid subscription model.

#### Before TGE

Before the Token Generation Event, SUZUNA focuses on building and improving the core product.

Users can access the free product tier and deploy up to **2 AI agents** without requiring $SZN.

This phase allows the product to establish real usage before token-based subscription functionality is introduced.

#### After TGE

Following TGE, SUZUNA will introduce the **Pro** subscription.

Pro users will be able to deploy up to **6 AI agents**, with the subscription paid using **$SZN**.

The exact subscription price and payment amount will be announced before Pro activation.

#### Product Utility

The primary utility of $SZN within SUZUNA is access to the Pro subscription.

This creates a direct product relationship between the token and the platform:

**$SZN → Pro Subscription → Up to 6 AI Agents**

The token is therefore integrated into an actual SUZUNA product function rather than being defined around additional mechanisms that are not part of the product.

#### Scope of $SZN Utility

At launch, SUZUNA does not define additional token mechanics such as:

* Staking
* Governance
* Token burns
* Buybacks
* Fee sharing
* Revenue distribution

Any future changes to token utility would be communicated separately and should not be assumed as part of the current product design.


---

# 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://suzuna.gitbook.io/whitepaper/usdszn-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.