> For the complete documentation index, see [llms.txt](https://soundr.gitbook.io/soundr-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://soundr.gitbook.io/soundr-docs/readme.md).
# Introduction
**Soundr** is an AI-native, real-time information infrastructure layer purpose-built for the Web3 ecosystem. In an era where critical insights are buried across thousands of fragmented and ephemeral channels, Soundr brings order to chaos—**indexing, structuring, and scoring the unstructured**.
We go beyond traditional Web2 paradigms of search and discovery by creating a **context-aware, narrative-driven intelligence engine** that understands Web3’s unique dynamics. From decentralized governance discussions to tokenomics debates on Twitter Spaces, from cryptographic protocol research to meme meta-trends—Soundr **captures the pulse** of the on-chain and off-chain ecosystem in real time.
### Jump right in
---
# 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://soundr.gitbook.io/soundr-docs/readme.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.