> 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/why-meerkats-the-power-of-community.md). # Why Meerkats? The Power of Community In the wild, meerkats are **small, often underestimated, yet they thrive where others fail.** They don’t survive alone—they **move as one, build together, and protect each other.** This is the foundation of $MERK. 🔹 **Strength in Numbers** – A single meerkat is vulnerable, but a **collective force is unstoppable.** In crypto, a project's strength lies in its **community.** $MERK is not just about individual gains—it’s about **building together.** 🔹 **Always Alert, Always Adapting** – Meerkats are constantly **watching, evolving, and staying ahead of threats.** $MERK follows the same principle—**innovation, resilience, and long-term sustainability.** 🔹 **Beyond the Hype** – Most meme tokens live and die by speculation. **Meerkats don’t rely on luck—they strategize.** $MERK ensures that **hype is just the beginning, not the end.** The **burrow** is not a place to hide—it’s the foundation of something bigger.\ And now, it’s time to rise. --- # 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/why-meerkats-the-power-of-community.md?ask=&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.