> For the complete documentation index, see [llms.txt](https://docs.icepanel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icepanel.io/integrations/accuracy-score.md).
# Inaccuracy score
It's hard always to trust diagrams because they get out-of-date quickly. Even with modelling efficiencies, keeping tabs on what needs to be updated can be overwhelming, especially if you have a complex system.
IcePanel's Inaccuracy Score helps you make meaningful documentation that can be trusted from the start without asking creators if it accurately depicts the current reality.
## What is the Inaccuracy Score?
Each domain or diagram has its inaccuracy count in the header bar on the top right. This score is diagram-specific, so it's always contextual to what you're looking at. The score reflects the unique number of out-of-date links or unresolved inaccuracy comments.
The Inaccuracy Score flags:
1. Inaccuracy [Comments](/collaboration/commenting.md) - Your teammates can add inaccurate comments to mark things that need to be updated. These comments will increase your inaccuracy score.
## Improving your Inaccuracy Score
To improve your Inaccuracy Score:
* Resolve all inaccurate comments. This is the best way to keep your docs up-to-date and keep that score at "inbox 0".
---
# 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.icepanel.io/integrations/accuracy-score.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.
