Introduction

UnifyApps connects to Anthropic managed agents and returns the agents that account hosts, so they can be inventoried, monitored and brought under policy alongside every other platform you run.

This is one of two routes for Anthropic-based agents. Use this one for managed agents; use Anthropic Agent SDK for agents you built and run yourself.

What UnifyApps discovers

Discovery reads the platform's own APIs through a connection your tenant already holds. Each agent it returns becomes a record in the Agent Registry, and the traces those agents produce are collected from that point on.

The connection also supports model registration, so models served through it can be imported into the Model Registry.

Capability support

Capability	Support	Maturity
Discovery of agents	Yes	GA
Model import	Yes	GA
Manual agent registration	Yes	GA
Trace ingestion	Yes	GA
`Observe · Advisory`	Yes	GA
`Control · Enforced`	Not selectable	—

Note: You do not instrument a discovered agent. Its traces arrive through the connection — there is no SDK step and nothing to install. A discovered agent shows Setup Pending until its first trace lands, which usually means it simply has not run yet, not that you owe it work. Give it real usage and it flips to Active on its own. While it is pending, the agent detail page still shows a Setup tab carrying SDK and OTLP instructions. On a discovered agent those do not apply — the tab appears for anything awaiting a first trace, however it was registered. See Agent Statuses.

Managed agents or the SDK

Your agent is	Use	How it reports
Hosted as a managed agent	`Anthropic` in Discovery	Swept from the connection
Built and run by you	`Anthropic Agent SDK` in `+ Register Agent`	Instrumented, reports in

An asset found on more than one connection is one record linked to each connection, and its Register toggle is shared. A manual registration of the same agent through Anthropic Agent SDK is a separate record — pick one route.

Before you begin

Create the connection first — Discovery sweeps an existing connection; it does not collect credentials. See Create a Connection.
Know which account you are scanning — One connection covers one account. Separate production and development accounts need one connection each.

Add the connection

Step 1: Open the Add application panel

AI Governance > Discovery > + Add Application.

Step 2: Select Anthropic

Step 3: Confirm the connection type

Observe · Advisory is preselected and is the only tier available.

Step 4: Choose the connection and connect

Verify

The row shows PLATFORM as Anthropic, STATUS as Connected, and DISCOVERED populates with an agent count once the first sweep finishes. The assets appear on the connection's Assets table as Excluded until you register them.

Limitations

Observation only — Controls set to Block or Mask cannot take effect. Flag works as documented and every violation is recorded.
Coverage stops at the connection's permissions — Agents the connection identity cannot list will not appear, and will not be flagged as missing.
Two routes, two records — Managed agents and SDK agents are separate registration paths.

Troubleshooting

The sweep returned nothing. The connection identity probably cannot list agents on that account. Discovery sees exactly what that identity sees.

An agent I built with the SDK is not appearing. SDK agents are not swept. Register them manually against Anthropic Agent SDK.

Agents appear but never accumulate traces. Check LAST TRACE on the registry row against known usage before treating it as a fault.