Applications and models
Bring selected application inventories, declared models, and recorded model activity into your own reporting.
Data Access · Preview
Bring VeriProof evidence into your own system
Give your compliance application a way to retrieve application inventories, oversight records, and saved framework assessments. Your team keeps the workflow it already uses.
Choose the records your team needs
Runtime oversight
Retrieve policy-decision summaries, human-review records, and application-reported execution outcomes. Each keeps its own meaning and source context.
Framework assessments
Retrieve saved assessments and control results for supported registered frameworks, with evaluation IDs and assessment periods preserved.
Connect to your existing review process
Set the scope
An administrator chooses the applications, datasets, and frameworks the integration can read, then registers a signing key or client secret.
Retrieve the publication
Your system checks for new publications and retrieves structured JSON, a matching PDF, and a signed manifest. An optional webhook signals when files are ready.
Use your existing workflow
Map the records into your internal application. Keep source references with the imported evidence so reviewers can follow a result back to its assessment.
The same VeriProof interface serves different receiving systems. Your integration team owns the destination mapping; VeriProof provides the scoped records and retrieval contract.
Start with a working receiver
The reference compliance receiver imports publications into a local SQLite database. It keeps assessment controls, original files, and import receipts together, and reuses the receipt when a publication arrives again.
Open its read-only view to inspect imported revisions, compare recorded control results, and download the source files. The package includes setup instructions, recovery guidance, and executable checks.
Your developers can adapt its import transaction to the database and review process your organization already runs.
Keep the evidence traceable
Publication IDs and source evaluation IDs keep revisions distinct. Signed manifests bind the JSON and PDF to their recorded hashes, so your receiver can check the files before committing an import.
Your system can poll for publications it missed. Access controls, expiry, and withdrawal are checked when it retrieves the files.