Data Rooms — Agents & MCP
The diligence agent, agent runs and approvals, and connecting external sources to Data Rooms via MCP.
Data Rooms is agent-first. This page covers the agent that does the work, how you review what it does, and how you connect the data it reads.
The diligence agent
The diligence agent reads a room's documents and performs operational due diligence — extracting facts, answering questions, comparing documents, and drafting reports. You start it with the Run diligence action (see Workflows).
Intelligence scans
Beyond the diligence agent, the Intelligence suite runs seven targeted AI scans over a room — red flags, completeness, anticipated Q&A, change detection, entity mapping, benchmarking, and compliance. Each scan is its own agent run with a result count (flags / alerts / questions / changes).
Agent runs
Each execution is an agent run under AI Operations → Agent Runs. A run records the agent's steps, what it extracted, and the outputs or actions it proposes — so the work is inspectable, not a black box.
Approvals
Agent-proposed state changes can route through AI Operations → Approvals, where a human reviews and signs off before they're committed. This human-in-the-loop pattern is shared across modules, not just Data Rooms.
MCP connections
VantedgeAI is MCP-native. Connect external systems — SharePoint, Egnyte, Google Drive, email, and others — as MCP connections, and the diligence agent reads from them directly (this is what powers BYOD sources and ODD on Drive).
For agents: fetch any of these pages as clean markdown via
/llms.txt,/llms-full.txt, or by appending.mdto any page URL.