> For the complete documentation index, see [llms.txt](https://docs.insuraviews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.insuraviews.com/getting-started/run-reports.md).

# Run Reports

**Reports Overview**

Insuraviews offers five comprehensive report types to transform your rate filing research into actionable strategic insights:

[**Single Carrier View**](https://docs.insuraviews.com/getting-started/run-reports/single-carrier-view.md) - Generate focused analysis on one specific insurance company's rate filing activity, strategies, and patterns across states and lines of business

[**Multi Carrier View**](https://docs.insuraviews.com/getting-started/run-reports/multi-carrier-view.md) - Compare and analyze multiple insurance carriers simultaneously to understand competitive dynamics, market positioning, and industry-wide trends

[**DOI View**](https://docs.insuraviews.com/getting-started/run-reports/doi-view.md) - Access regulatory perspective reports that summarize Department of Insurance activity, approval patterns, objection trends, and regulatory decision-making across jurisdictions

[**Rating Factors View**](https://docs.insuraviews.com/getting-started/run-reports/rating-factors-view.md) - Dive deep into the actuarial components of rate filings, analyzing loss ratios, trend factors, expense ratios, and other key rating elements that drive rate changes

[**State View**](https://docs.insuraviews.com/getting-started/run-reports/state-view.md) - Examine market activity from a geographic perspective, understanding state-specific trends, regulatory environments, and competitive landscapes

<br>


---

# 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.insuraviews.com/getting-started/run-reports.md?ask=<question>&goal=<user_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.
