> 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/use-case-examples.md).

# Use Case Examples

With a large amount of data and a range of unique tools built to access it, it's not always clear how to apply those tools to a workflow or project. This use case documentation shows use cases across a range of topics to help provide a basic framework you can mold to fit your own workflow. Below are the use cases that will be explored in these documents:

#### Use Cases <a href="#use-cases" id="use-cases"></a>

* [**Market Research**](https://docs.insuraviews.com/getting-started/use-case-examples/using-tools-and-reports.md#market-research): Quickly scan all filings in a specific state or line of business
* [**Competitive Intelligence**](https://docs.insuraviews.com/getting-started/use-case-examples/using-tools-and-reports.md#competitive-intelligence): Track specific carriers' filing patterns and strategies
* [**Regulatory Analysis**](https://docs.insuraviews.com/getting-started/use-case-examples/using-tools-and-reports.md#regulatory-analysis): Monitor DOI responses and approval patterns
* [**Due Diligence**](https://docs.insuraviews.com/getting-started/use-case-examples/using-tools-and-reports.md#due-diligence): Access both summaries and original documents for thorough analysis
* [**Trend Identification**](https://docs.insuraviews.com/getting-started/use-case-examples/using-tools-and-reports.md#trend-identification): Use saved filters to regularly monitor specific market segments


---

# 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/use-case-examples.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.
