> For the complete documentation index, see [llms.txt](https://mmfinance.gitbook.io/mad-bucks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mmfinance.gitbook.io/mad-bucks/about-usdmad/what-is-usdmad.md).

# What is $MAD?

![](/files/xCN9UwPYhjG0fUmgU4WJ)

### What is Mad Bucks?

Having made our first two collections, the CRO MAD MEERKAT NFT and MM TREEHOUSE, a resounding success , we are constantly pushing ourselves further in innovative ways to reinvent the NFT space.

Introducing the Mad Bucks, a long-term utility token which forms the foundation of Mad Meerkat NFT Ecosystem.&#x20;

Our key aim is to create a holistic, complete and extensive MM NFT Ecosystem. This means that there is a need for a utility token to create an economy that allows for people to transact to purchase the goods and services that they desire in the ecosystem. Mad Bucks is the answer to this and ties all such initiatives together.

There are three main use cases for $MAD - The Mad Meerkat Arena, minting the Degen Mad Meerkat NFT, and for Cronos Project Partnerships.<br>


---

# 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://mmfinance.gitbook.io/mad-bucks/about-usdmad/what-is-usdmad.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.
