> For the complete documentation index, see [llms.txt](https://docs.sinfonia.zone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sinfonia.zone/italian/nft-podcast/intro.md). # Intro A podcast is a form of media content designed as a collection of digital audio files. Think of it as the modernization of the radio. Each individual audio is called an episode and can be downloaded or listened to online. Whether it be news, sports, celebrities, finance, or lifestyle, there is an endless list of subjects in today’s most popular podcasts that ensures anyone can find something entertaining. Successful podcasts come from both recognizable companies and small creators alike. Like any digital asset, podcasts can even be turned into NFTs. While visual NFTs are often most talked about, audio NFTs could be the medium of the future. They would offer an experience for the listener. Podcast hosts could allow fans to bid on a chance to own their favourite podcast episode. By offering non-fungible podcasts, hosts can strengthen their relationship with listeners and promote a greater sense of community. Using NFTs as podcasts is a creative way for creators to engage their listeners, and for listeners to be rewarded. This idea has endless possibilities and benefits for everyone involved in the art of podcasting. --- # 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://docs.sinfonia.zone/italian/nft-podcast/intro.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.