Connect to the right deployment
One portal address identifies your environment. The CLI discovers its services and saves a named profile without storing secrets in it.
VeriProof CLI
Keep VeriProof operations in your terminal
Some work belongs in a script. The VeriProof CLI brings application setup, session investigations, and evidence exports to your terminal, using the access already assigned to you.
From application setup to decision evidence
Use repeatable commands for operating tasks, then return to the portal when the work calls for visual review or collaboration.
Create an application and application key
Register applications and issue ingestion keys from the command line. New secrets appear once, ready for your team's secret manager.
Inspect authorized sessions
Find the session behind a question, including archived activity. The CLI follows results across pages within your assigned access.
Export and verify evidence
Share a session evidence pack for independent review. The CLI can run the separately installed verifier; reviewers do not need a VeriProof account.
Access that fits where you work
Interactive sign-in
Use your deployment's sign-in provider. The operating-system credential store protects the saved refresh credential.
Remote terminal
No browser on the terminal? A device code lets you complete sign-in through your deployment's customer portal.
Approved automation
Private Enterprise, coming soon to Azure Marketplace, will support workload identity for short-lived access, so scheduled jobs don't store a user's refresh credential.
Keep routine operations under control
Explicit key changes
Key rotation invalidates the old secret immediately. Your team chooses when to rotate it and update the application that uses it.
Protect local files
Project profiles contain no secrets, and evidence exports do not replace an existing file unless the operator explicitly allows it.
Diagnose without changing state
Connection failed? Read-only health checks help you distinguish a local configuration error from a deployment failure.
Readable for people, structured for scripts
An operator needs a clear result. Automation also needs to know whether a command completed, needs sign-in, or was denied.
Structured results
JSON output includes the result details scripts need. Correlation IDs help connect a failed request to its investigation.
Clear failure categories
Authentication, authorization, invalid commands, and service failures use distinct results so automation can stop or retry appropriately.
Work within assigned access
Your application permissions carry through to scripts, keeping automated work within the signed-in account's assigned access.
Get the CLI through your customer portal
The VeriProof CLI is generally available. Download it from Tools and SDKs in the customer portal, where you can also find installation instructions.
Working with agents? VeriProof MCP brings governance analysis, reviews, and policy-controlled workflows to Copilot Studio and other compatible apps. Its action tools pair computer-use actions with key screen evidence and policy results for the connected application to enforce.
For policy checks inside application code, explore the SDK integrations.