> For the complete documentation index, see [llms.txt](https://docs.finout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finout.io/user-guide/optimize/findings-beta.md).

# Findings \[Beta]

An finding is a single finding raised by one of your agents — the unit of work for investigating and acting on what an agent found. Every finding exists from the moment it's created until it reaches a terminal state, and stays tied to the agent, resource, and use case that produced it.

{% hint style="info" %}
To use the agentic product, enable the AI features in your account. See [AI Opt-In](https://docs.finout.io/cross-platform-features/list-of-cross-platform-features/ai-in-finout/ai-opt-in).
{% endhint %}

{% hint style="info" %}
You need at least one active agent configured to see any issues.
{% endhint %}

* **Findings List** — the table view of every issue: columns, grouping, filtering, and sorting. Read more [here](https://docs.finout.io/user-guide/agentic-product-beta/issues-beta/issues-list-beta).
* **Finding Lifecycle** — statuses, and how issues get deduplicated across agent runs. Read more [here](https://docs.finout.io/user-guide/agentic-product-beta/issues-beta/issue-lifecycle-beta).
* **View Single Finding Details** — findings, and metrics. Read more [here](https://docs.finout.io/user-guide/agentic-product-beta/issues-beta/view-single-issue-details-beta).


---

# 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.finout.io/user-guide/optimize/findings-beta.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.