> For the complete documentation index, see [llms.txt](https://docs.pynt.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pynt.io/documentation/api-catalog/navigate-api-catalog/filtering-api-catalog-by-application.md).
# Filtering API Catalog by Application
Easily filter your API catalog by application in Pynt to quickly locate and manage specific APIs within your environment. This powerful filtering feature allows you to focus on the APIs that matter most, streamlining your workflow and enhancing your ability to monitor and secure your applications. By narrowing down your view to a particular application, you can efficiently review its associated APIs, assess their security status, and take any necessary actions. Pynt’s intuitive filtering capabilities make it simple to maintain a clear and organized overview of your API landscape, ensuring that your security management remains targeted and effective.
\
Firstly, you have the capability to **filter** the view **by application**, displaying only the APIs associated with a specific application or viewing all APIs collectively.
Filtering the API Catalog by app
---
# 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.pynt.io/documentation/api-catalog/navigate-api-catalog/filtering-api-catalog-by-application.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.