# Manage API Source Gaps

In various scenarios, attention is warranted when **gaps** exist between your **API sources**. 

Consider the following situations: [New APIs](/documentation/api-catalog/manage-api-source-gaps/new-apis.md), [Untested APIs](/documentation/api-catalog/manage-api-source-gaps/untested-apis.md), [Shadow API in Production](/documentation/api-catalog/manage-api-source-gaps/shadow-apis.md) or [Undocumented APIs](/documentation/api-catalog/manage-api-source-gaps/undocumented-apis.md). Each scenario has unique implications, requiring individualized handling for a comprehensive workflow.

To ensure a robust API security strategy, it is crucial to address and rectify such gaps by [adding all available sources](/documentation/applications-view/manage-sources-for-api-discovery.md). This approach allows Pynt to proactively track APIs, ensuring both security and operational insights are comprehensive and accurate.

Gain valuable **insights** into your API landscape with the API Catalog Insights, empowering you to effectively manage and bridge gaps within your API ecosystem.

<figure><img src="/files/CplpGgUvxvAZxA1VVh8I" alt=""><figcaption><p>API Catalog insights</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.pynt.io/documentation/api-catalog/manage-api-source-gaps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.