> 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/inform.md). # Inform Finout's Inform features provide powerful tools for gaining insights into cloud resource usage and cost optimization. By leveraging detailed metrics and customizable reports, Inform helps teams understand their cloud infrastructure more clearly. With advanced visualization and analysis capabilities, users can easily track spending, identify inefficiencies, and make data-driven decisions to optimize costs and resource allocation. Whether it’s forecasting future expenses or identifying waste in unused resources, Inform delivers actionable intelligence to improve financial planning and cloud operations. Includes the following features: * [Finout Overview](/user-guide/inform/finout-overview.md) * [MegaBill](/user-guide/inform/megabill.md) * [Custom Drilldown](/settings/custom-drilldown.md) * [Custom Cost Input](/user-guide/inform/custom-cost-input.md) * [Virtual Tags](/user-guide/inform/virtual-tags.md) * [Shared Cost Reallocation](/user-guide/inform/shared-cost-reallocation.md) * [FinOps Dashboards](/user-guide/inform/finops-dashboards.md) * [Financial Plans](/user-guide/inform/financial-plans.md) * [Data Explorer](/user-guide/inform/data-explorer.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.finout.io/user-guide/inform.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.