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

# Intro

     The rise of Web3 and decentralized technologies has transformed digital media. Traditional radio remains largely centralized, limiting accessibility, transparency, and community participation. 

<p align="center">     Spaces Media is a 24/7 blockchain-powered broadcast network dedicated to Web3 culture, cryptocurrency, and decentralized innovation. We deliver round-the-clock programming featuring industry insights, live discussions, expert interviews, and curated music. </p>

<p align="center"></p>

$SPACES is the culture token of the Spaces Media community — a digital collectible that celebrates Web3 radio culture and memes. The Spaces Media Decentralized Organization (DO) lets the community vote on fun cultural matters using Access Pass NFTs as voting passes.&#x20;

<p align="center">The founding team implements approved proposals. Everything is built for entertainment, community vibes, and cultural participation. $SPACES and the NFTs exist for fun, social connection, and supply-and-demand dynamics — nothing more.</p>


---

# 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.spaces.media/intro.md?ask=<question>&goal=<user_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.