Industry SDK quickstart
Developers configure SDK reporting. Administrators manage application and package access. Other roles can use the recorded evidence within their portal permissions.
These quick starts help developers govern regulated AI workflows with consistent evidence. Choose your industry, configure the core SDK, and pass the typed industry values that describe your workflow to each governed action.
Industry values extend the core governed action. They become policy fields under input.snapshot.industry and evidence attributes on the session. They do not activate policy rules or establish that an application meets a regulatory requirement.
Each guide covers:
- Install and configuration for TypeScript, Python, and .NET
- One governed action for the workflow, with policy checked before the action and before its result is released
- Typed industry value examples from each SDK’s generated vocabulary for the vertical
- Links to the full governance reference, policy patterns, and industry standards
Choose your industry
| Vertical | Quick start |
|---|---|
| Banking & Financial Services | Getting started |
| Mortgage & Loan Processing | Getting started |
| Insurance | Getting started |
| Healthcare & Life Sciences | Getting started |
| Clinical Trials (Healthcare & Life Sciences solution) | Getting started |
| Telecom & IT Operations | Getting started |
| Manufacturing & Supply Chain | Getting started |
| Higher Education | Getting started |
| Energy & Utilities | Getting started |
| Government & Public Sector | Getting started |
| Legal & RegTech | Getting started |
| HR & Workforce Management | Getting started |
| GRC, ESG & Enterprise Risk | Getting started |
| Professional Services & Consulting | Getting started |
| Agentic Payments & Stablecoins | Getting started |
How industry guides build on the core SDK
Every industry guide builds on the core SDK. Configure the core SDK once, then add the workflow fields for your industry.
The field names in these guides also appear in portal evidence, policy results, and exported compliance reports. Your development and review teams can use the same terms from setup through review.
| Layer | What you add here | Why it exists |
|---|---|---|
| Core SDK | One client, the governed action around each protected step, and application facts | Checks policy, records governed sessions, and returns a typed result |
| Industry values | Typed values from the vertical’s generated vocabulary | Supplies the policy fields and evidence attributes your rules and reviewers use |
| Portal and policies | Evidence review, policy inputs, and compliance reports | Keeps setup, review, and reporting consistent |
Start with the path that matches your intent
- Have a VeriProof account? Open Tools and SDKs for package access, then use Set up SDK for the application’s key, ID, and endpoint. Set
VERIPROOF_API_KEYfrom your secret manager. For Customer-managed Azure, use the supplied ingest base URL asVERIPROOF_ENDPOINT. - Need a VeriProof account? Start Developer free for 60 days
- Need to see a governed workflow first? Try a live simulator
- Need the standards reference before you instrument? Open the industry coverage library
- Need a commercial or architecture review? Contact VeriProof
Compare workflow coverage
Browse the industry coverage library to compare fields, permitted values, and referenced standards. Choose the fields that describe actual application data.