AI agent discovery and inventory, from your traffic, telemetry and code.
Praesidia's agent discovery builds one inventory of your AI agents from the traces you send, the agents and MCP servers you register, the unregistered agents that try to reach yours, and the GitHub and GitLab repositories you connect. It does not scan cloud accounts, data warehouses or endpoints.
Every row is something you can act on in the same console: adopt it, restrict it, or take it out of service.
Three things the list gives you
A list that fills itself in
Built from traffic, telemetry and code you already have, not from a spreadsheet somebody remembers to update.
The awkward gaps, named
Agents with no owner are called out as such — usually the ones still holding a credential from a project that ended.
An action on every row
Adopt an observed agent and it becomes a governed one, with its own credentials and an explicit list of what it may reach.
Five sources, and nothing else
- 1
Send your OpenTelemetry GenAI traces to Praesidia and the agents in them are listed as observed.
- 2
Register an agent or an MCP server through the API or the SDK and it arrives with credentials and an owner.
- 3
An unregistered agent that tries to reach one of yours is captured for you to claim or ignore.
- 4
Every MCP server you register is inventoried tool by tool, with drift flagged when a definition changes.
- 5
Connect a GitHub or GitLab organization and the agents, MCP servers, tools, prompts and vector stores defined in its repositories are found and re-checked on a schedule.
- 6
Adopt what you found: an identity of its own, an owner, and the connections you grant it.
Where the inventory stops
- It works from traffic, telemetry and code
- The five sources above are the closed list. Repository scanning reads the GitHub and GitLab organizations you connect; it does not scan your cloud accounts, data warehouses or endpoints today, and we would rather say so than let you find out later.
- Tools are inventoried once a server is registered
- Tool-level inventory and drift detection apply to MCP servers you have registered. A server found in a repository is listed for you to adopt; until it is registered, its tools are a gap in the list, which is why registering servers is the first thing we ask for.
- Observed is not governed
- An agent seen in your traces is listed as observed — seen doing work, not yet under control. It gets an identity, rules and evidence only once you adopt it.
- Then: observe before you enforce
- Once an agent is governed, a rule can be evaluated and recorded without changing behaviour, so you can read a week of real decisions before anything is blocked.
Works with
- LangGraph
- CrewAI
- OpenAI Agents SDK
- Google ADK
- Microsoft Agent Framework
- MCP server configurations
Repository scans recognise agents built with these frameworks and the MCP servers configured in code. Each framework also has a connection recipe, limited to the setup its page lists. Compare every runtime in the catalog.
Read the docs: getting started. Then: what each agent can reach · runtime security · MCP server governance.
Common questions about AI agent discovery
AI agent discovery is finding the AI agents an organization actually runs, including the ones nobody registered, and keeping them in one inventory with an owner. Praesidia builds that inventory from your traces, the agents and MCP servers you register, the unregistered agents that try to reach yours, and the GitHub and GitLab repositories you connect.
Five, and nothing else: the OpenTelemetry GenAI traces you send; agents and MCP servers registered through the API or SDK; unregistered agents that try to reach one of yours; the tools of each MCP server you register; and the agents, MCP servers, tools, prompts and vector stores defined in the GitHub and GitLab repositories you connect, re-checked on a schedule.
No. Cloud accounts, data warehouses, SaaS agent platforms and endpoints are not scanned today. Repository discovery reads only the GitHub and GitLab organizations you connect.
It is listed as observed: seen doing work, not yet under control. Adopt it and it becomes a governed agent with an identity of its own, an owner and the connections you grant it; until then it gets no rules and no evidence. New policies on an adopted agent start in observe mode.
Not until you register them. A server found in a repository is listed for you to adopt; tool-level inventory and drift detection apply to the MCP servers you have registered.
Yes. Discovery and the inventory are in every plan, including the free Developer plan; the governance dashboard is on the Team plan's Advanced tier and on Enterprise.
Go deeper
- Building an AI agent inventory — how to discover, register and maintain the agents you deploy.
- OTLP telemetry ingest for agent discovery — turning the traces you already send into an inventory.
- The AI governance guide — what to do with the inventory once you have it.
- The AI agent security guide — identity, authorization and guardrails for the agents you found.
- Shadow AI and AI agent governance, defined in the glossary.
Find out how many agents you are actually running
Start the inventory with one workspace and your existing traces.