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

# Our-Mission

We've been obsessed with how creators have been able to grow such tight knit communities. There’s something to be said about how well connected web3 has become with one another. We grow and move as one — almost like a hive mind.

IF we can take the current way that musicians release and market music to their audiences and add just a tinge of what makes web3, well web3, then there is a good possibility that the two will connect rather seamlessly.

Now this isn’t to push products or to aimlessly present more assets to the market to sit with no intrinsic “utility”.

*Voidcaller* aims to show that musicians are able to create such a community of support **WITHOUT** needing to fall victim to the current web2 meta of subscription-based platforms.

With a little bit of creativity, and a lot of hard work. *Voidcaller* hopes to create a legacy for musicians to be able to bring their audiences closer, as well as promote a new way to provide digital ownership to their listeners.


---

# 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://voidcaller.gitbook.io/void-paper/our-mission.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.