> 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.&#x20;

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).&#x20;


---

# 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.sportradar.com/storytelling-tools/storytelling-tools.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.
