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

# Token Economy

The TAO token is the governance token of Meta-Soul, and is a token based on the klaytn network. It is used to purchase NFT cards within the Meta-Soul platform, and you can get TAO coins as a battle mode reward when you complete coin dungeons and collect character collections.

The Meta-Soul team wants both the vitalization of NFT card transactions and the increase of the value of TAO coins, and we hope that many users will enjoy the real pleasure of P2E services through TAO coin rewards while enjoying the game within the Meta-Soul platform.

Token Name : TAO Token

Token Symbol : TAO

Token Issuance : 3,300,000,000

Network Type : Klaytn

![](/files/ZGBi53WZqPKz9OiBTUjD)


---

# 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://soul-meta.gitbook.io/meta-soul_en/token-economy.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.