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

# $TOOL

$TOOL is the coin that powers the CNFT Tools and TOOLHEADS ecosystem

<figure><img src="/files/9tsM3n1bhXv6UYO3AcQ7" alt="" width="375"><figcaption></figcaption></figure>

### Key Facts

* $TOOL will have a supply of 1,000,000,000 (1 Billion)
* $TOOL will be decimalised to 6 places.&#x20;
* $TOOL will be available to buy and sell on Cardano DEXs

### Tokenomics

<figure><img src="/files/HHh7OeoGhtzv1KSojIZB" alt=""><figcaption></figcaption></figure>

* 10% of $TOOL supply (100,000,000) is reserved for an initial liquidity fund. This will be paired with 100,000 ADA to create initial liquidity pool(s) for trading.&#x20;
* 5% of $TOOL supply  (50,000,000) is reserved for marketing purposes.&#x20;
* 85% of $TOOL supply is reserved to be emitted through the TOOLHEAD staking platform. There is **NO presale.** The only way to initially acquire $TOOL will be through the TOOLHEAD STAKING PLATFORM.


---

# 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://toolheads.gitbook.io/toolpaper/staking/usdtool.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.