Agent integrations
Start with the task your agent needs to complete. Reading evidence, sending runtime records, and changing a customer system need different connections.
| You need to… | Use |
|---|---|
| Configure applications, keys, or integration health | VeriProof CLI |
| Investigate evidence or complete role-approved review work | MCP server |
| Connect Copilot Studio to VeriProof records | Copilot Studio quickstart |
| Govern an action that changes a customer system | Copilot Studio quickstart |
| Send governed runtime evidence | SDK ingest |
| Run frequent policy checks beside an application | Edge Gateway |
| Check exported evidence without trusting the VeriProof API | Verify evidence |
Use your organization’s VeriProof portal URL to find the service addresses and sign-in instructions. Do not copy an address from another deployment, even if its hostname looks similar.
Keep credentials separate
- Package access: use the customer portal to download entitled SDK and CLI packages.
- Application key: sends runtime evidence and v2.2 policy evaluation requests.
- User sign-in: authorizes CLI and MCP work using your VeriProof role.
- Azure verifier identity: reads the customer-owned Azure SQL Ledger and protected digests.
Keep each credential with its intended task. An application key cannot replace user sign-in for MCP tools. Check the signed-in role and application scope before asking an agent to act.
Start here
Follow Set up an AI agent. For a customer-managed deployment, review Dedicated deployments first.
Last updated on