> 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 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.meerkat.wtf/introduction/what-is-usdmerk.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.