> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-enrichment-insights/how-to-filter-entities-by-current-enrichment-value.md).
# How to filter entities by current enrichment value
Tutorial going through the process of filtering entities by their current enrichment value.
### Filtering by current enrichment value
To filter [products](/fundamental-concepts/data-management.md) by their enrichment value, navigate to 'PIM' > 'Search'. Use the left menu to add filters and click 'Add filter' to begin.
'Search' page displaying all products
A dropdown menu will appear, asking you to select the type of filter you want to apply. Click it to display your filter options.
Dropdown menu containing the filter types
We will select the 'Completeness: Electronics Basic Information'. Choosing this option will reveal a slider, showing the progress of the enrichment process.
The completeness slider
You can now filter all the [products](/fundamental-concepts/data-management.md) by the completeness of their enrichment.
{% hint style="info" %}
You can mark all the products that show up when filtering by completeness, and add them to a new task by clicking the  above the products table.
{% endhint %}
---
# 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.struct.com/tutorials/guides/how-to-use-enrichment-insights/how-to-filter-entities-by-current-enrichment-value.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.
