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

# Intro

### FOR THE COMMUNITY. BY THE COMMUNITY.

$NOBDY is Solana’s first TRUE multi-project backed coin.

Backed by a diverse group of trailblazing Solana projects, $NOBDY stands as a defiant symbol of innovation and collaboration. We’re tearing down the old barriers, challenging the status quo, and proving that a token can be much more than a digital asset or a meme—it can be a catalyst for unfettered growth and limitless possibilities. Join us as we lead the charge in the Solana ecosystem, empowering projects to rise, disrupt, and dominate. Because when it comes to revolutionizing DeFi, **$NOBDY CARES and $NOBDY DOES IT BETTER.**

**Stay tuned as we will be continuing to add to this documentation.**


---

# 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://nobdy-token.gitbook.io/nobdy/intro.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.