> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/agents/onboarding-agents/discovering-agents-from-integrations.md).

# Discovering Agents from Integrations

### Overview

Some application integrations can **extract agents** automatically into BalkanID. Extracted agents appear on **Configure → Agents** with an application association and source-controlled fields.

Extraction is the preferred path when BalkanID has a direct integration that understands the application’s agent model.

{% hint style="info" %}
**Early Access:** Agent extraction requires Agents (Early Access) to be enabled for your tenant. Contact Customer Support to enable it.
{% endhint %}

### How extraction works

1. Configure a supported application integration in BalkanID.
2. Provide any credentials required for agent discovery for that application.
3. After sync completes and data is available, extracted agents appear on the Agents page.
4. Assign an owner in BalkanID for accountability.
5. Review the agent’s **Has access to**, **Identities**, **Credentials**, and capabilities tabs.
6. [Map additional identities or credentials](/agents/mapping-identities-and-credentials-to-agents.md) when you need to record access associations beyond what was extracted.

Extracted agents remain linked to the source integration:

* Inventory and most attributes refresh from the source on sync
* You can assign an owner in BalkanID
* Other fields stay read-only

### What extraction can include

Depending on the application, BalkanID may discover:

* Agent inventory and status
* Agent type
* Access relationships (resources and connections)
* Associated credentials
* Source-specific capabilities such as MCP servers or built-in tools

Exact coverage varies by integration. Refer to the application-specific subpages under this section in the documentation for supported integrations and setup details.

If an application you need is not covered by extraction, you can still govern those automation actors with [Manual Registration](/agents/onboarding-agents/manual-registration.md) or [Uploading Agents by CSV](/agents/onboarding-agents/uploading-agents-by-csv.md).


---

# 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.balkan.id/agents/onboarding-agents/discovering-agents-from-integrations.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.