Industry SDK Quick Start
These guides are for Developers instrumenting regulated AI workflows and Administrators configuring API access. Governance Engineers, Compliance Officers, Business Owners, and Auditors work with the governed output in the portal — your Developer sets this up. Start with your role’s Training Academy track instead.
VeriProof provides a governed vocabulary for every major regulated industry. These quick-start guides take you from install to your first attributed evidence record using the real OTel attribute names from the vertical catalog files.
If you are coming from the public site, this is the developer handoff. Start with the core SDK once, then add the vertical vocabulary that matches the regulated workflow you are instrumenting.
Each guide covers:
- Install and configuration for TypeScript, Python, and .NET
- The key OTel attributes for the vertical, drawn directly from the mirrored catalog files
- A working instrumentation example with
.withMetadata()orspan.set_attribute()calls - Links to the full governance reference, policy patterns, and source standards
Choose your vertical
| Vertical | Quick start |
|---|---|
| Banking & Financial Services | Getting started |
| Mortgage & Loan Processing | Getting started |
| Insurance | Getting started |
| Healthcare & Life Sciences | 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 |
How the layering works
All vertical packages build on top of the core SDK using the same session-builder pattern. Start with the core SDK reference if you need the cross-industry governance baseline, then step into the vertical quick start when you are ready to use the regulated workflow vocabulary specific to your market.
The attribute names in these guides are the same names that appear in portal evidence records, in policy evaluations, and in any exported compliance report. There is no translation between instrumentation and review — the vocabulary carries through unchanged.
| Layer | What you add here | Why it exists |
|---|---|---|
| Core SDK | client setup, session lifecycle, export configuration, base governance fields | Gives every implementation one common instrumentation model |
| Vertical vocabulary | regulated workflow attributes, standards-aware values, market-specific metadata | Lets the same SDK emit the evidence contract your market actually requires |
| Portal and policy surfaces | evidence review labels, rule inputs, framework-aligned outputs | Keeps instrumentation, governance review, and exports on the same vocabulary |
Start with the path that matches your intent
- Need an API key and a working account? Get API access
- Need to see the portal first? Try the live demo
- Need the standards reference before you instrument? Open the industry coverage library
- Need a commercial or architecture review? Contact VeriProof
Not sure which vertical fits?
Browse the full industry coverage library to compare OTel namespaces, standards coverage, and operating depth across all verticals before you start instrumenting.