> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/ship-your-work/reports.md). # Reports Turn a notebook into an interactive report your team can ask questions of. A **report** turns a notebook's analysis into a shareable summary for stakeholders, without extra work. Reports aren't static: anyone you share a report with can ask the agent questions about it. ## Creating a report | Method | What it does | | ----------------- | ------------------------------------------------------------------------------------------------------------------ | | **Automatic** | Zerve builds a report from the notebook's blocks and outputs, including its charts, tables and logic | | **From a prompt** | Tell the agent what to focus on, such as particular KPIs, an anomaly to explain, or the audience the report is for | ## Asking questions Readers can ask the report's agent follow-up questions, such as "Why did churn spike in October?" The agent answers from the analysis behind the report. ## Sharing Share a report with your team, and they can ask the agent questions too. See [Sharing and privacy](/zerve-docs/administration/sharing-and-privacy.md). --- # 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.zerve.ai/zerve-docs/ship-your-work/reports.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.