> For the complete documentation index, see [llms.txt](https://docs.teaproject.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teaproject.org/_3_token/tea-tokens.md).

# TEA Tokens

TEA tokens are the primary utility token for the TEA Project. TEA is used as gas on the TEA network and is necessary for signing transactions. TEA is also the currency that's exchanged by consumers in order to use TApps.

TEA can be purchased on Ethereum's layer-1 and shuttled [between Layer1 & Layer2](/_3_token/tea-tokens/billing-system-between-layer1-layer2.md). The total supply of TEA tokens is 100 million.

## How to Obtain TEA Tokens

#### Testnet

The TEA Fluencer TApp can be used as a retweet faucet (through Twitter) to secure some testnet TEA to compete in the contest.

#### Mainnet

After mainnet has launched, users will be able to use decentralized exchanges on Ethereum to purchase TEA tokens. Liquidity on centralized exchanges have not yet been formalized.


---

# 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.teaproject.org/_3_token/tea-tokens.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.