> For the complete documentation index, see [llms.txt](https://docs.nearweek.com/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nearweek.com/start/content-overview/audio-and-podcast.md).

# AUDIO & PODCAST

<figure><img src="/files/iDbFc9Xqzozsw6bStFEX" alt=""><figcaption><p><strong>Content from the NEARWEEK audio library, as shown on the website</strong></p></figcaption></figure>

## AUDIO & PODCAST

The NEAR ecosystem audio and podcast library (shown above) is an additional example of a useful product NEARWEEK has designed to specifically service the community.

NEARWEEK regularly curates and maintains a selection of different podcasts and twitter spaces that cover the NEAR, Aurora, and Octopus Network ecosystem and their respective developments.&#x20;

Our library ranges from audio recordings of technical developer talks, to more casual community fireside discussions.&#x20;

We publish the content on NEARWEEK.COM, as well as Spotify & Apple Music for your convenience. On behalf of your project or community, submit your own audio content for review to be featured!

### 🎧 [NEARWEEK: AUDIO CONTENT SUBMISSIONS](https://4efdmh2cgdi.typeform.com/NEARWEEK-audio?)


---

# 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.nearweek.com/start/content-overview/audio-and-podcast.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.