> For the complete documentation index, see [llms.txt](https://docs.squidex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squidex.io/id-02-documentation/concepts/assets/querying-assets.md). # Querying Assets This documentation is based on the *FoodCrunch* use case. Please open the link below alongside this page to understand the examples. {% content-ref url="/pages/-MSTfiNBwo8C1m-UB3WL" %} [Introduction and Use Case](/id-02-documentation/introduction-and-use-case.md) {% endcontent-ref %} Squidex provides the capability of querying your uploaded assets. You can query (search) by **tags**, or **name**, or use a combination of both. The following tag types are supported as of this writing: * `image` * `image/small` * `image/large` * `type/png` * `type/jpg` The following example shows how to search based on a tag `type/png`.

Additionally, you can also save the query and decide whether or not to share it with others. To save the query, simply click on the star button next to the search fields.

On the pop-up window, enter a name under **Name your query** (1) and click **Create** (2).

--- # 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.squidex.io/id-02-documentation/concepts/assets/querying-assets.md?ask=&goal= ``` `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.