> For the complete documentation index, see [llms.txt](https://docs.inferix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inferix.io/inferix-whitepaper/decentralized-visual-computing/decentralized-storage-and-data-security/polygon-digester.md).

# Polygon digester

After a 3D data file is stored on Inferix, it may be queried multiple times by Worker Nodes or design software. Depending on the needs of the query, the original data is converted into different levels of polygon detail through a lossy conversion algorithm. This process is handled by the *Polygon Digester* tool within the Inferix storage system. This tool ensures that the appropriate level of detail is provided for each task, optimizing both storage and performance by reducing unnecessary complexity in the 3D models when high detail is not required.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inferix.io/inferix-whitepaper/decentralized-visual-computing/decentralized-storage-and-data-security/polygon-digester.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
