> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/storytelling-tools/storytelling-tools.md). # Storytelling Tools Radar360 puts the world’s deepest sports database at your fingertips, letting you surface streaks, milestones, and one-of-a-kind stats in seconds. Powerful filters, advanced search, and saved custom reports help writers, editors, and producers give every piece richer context and historical perspective. Switch seamlessly between leagues, pull fresh data instantly, and keep reports updating in real time. Whether you’re sparking a new idea or strengthening a breaking story, Radar360 keeps your content sharp and engaging. See how it works and start exploring the tools [here](https://developer.sportradar.com/broadcast/docs/radar360-intro). --- # 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.sportradar.com/storytelling-tools/storytelling-tools.md?ask=&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.