> For the complete documentation index, see [llms.txt](https://docs.meerkat.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meerkat.wtf/introduction/what-is-usdmerk.md).

# What is $MERK?

$MERK is a **community-driven meme ecosystem** designed to empower creators, projects, and communities with **AI-powered tokenization, governance frameworks, and real economic infrastructure.**

While most meme tokens rely on **hype and speculation**, $MERK introduces a **sustainable model** where anyone can **build, monetize, and automate their own ecosystem**—without requiring complex development knowledge or large teams.

At its core, $MERK provides:

* **The Burrow** – A platform where communities can launch AI-powered Meme Agents, automate content creation, and integrate bonding curve mechanics.
* **Meerkat Wallet** – A multi-chain gateway to access **+1M tokens across 20+ blockchains.**
* **Advanced Staking & Rewards** – A long-term staking model that ensures sustainability and incentivizes community participation.

$MERK is not just a token—it’s a **new paradigm for meme culture**, giving communities **the tools to evolve, innovate, and thrive beyond market cycles.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.meerkat.wtf/introduction/what-is-usdmerk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.