> For the complete documentation index, see [llms.txt](https://pixelbands.gitbook.io/pixelbands/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pixelbands.gitbook.io/pixelbands/pixelbands.md). # PixelBands ## 🎧 Our Vision 🎧 To accelerate music on Solana by building a community of musicians that leverage on-chain tools to create, collaborate, and monetize music. ## **🔊 Building Value For Musicians 🔊** Musicians are the lifeblood of PixelBands as it relates to PixelBands’ mission to accelerate music on Solana. The value we bring to musicians is the marriage of innovations in royalties distributed through smart contracts on a permissionless and trust-less leger. With a strong and thriving community of artists who are motivated to create, collaborate, monetize, and build an audience we will achieve this mission. Gen1 of PixelBands set out to achieve the primary goal of getting music on chain and creating a smart contract to distribute royalties to creators for the content they have embedded in the project. Our goal is to build the tools musicians need to mint music NFTs as independent artists as well as enhance existing tools for music creation through the PixelBands Studio and our Holder tool Kit. --- # 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://pixelbands.gitbook.io/pixelbands/pixelbands.md?ask=&goal= ``` `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.