Rust SDK

The VeriProof Rust SDK requires Rust 1.96 or later and uses edition 2024. It checks policy before a governed action runs and before its result is released, records session evidence, handles signed human review, and stops an active governed run through the governed context’s StopToken.

Available crates

Adapters install their required Core SDK dependency automatically.

What the core crate includes

• Veriproof::from_env() and Veriproof::configure(api_key, options) for one application-scoped client.
• govern(action_name, input, action, options) with typed results and a ReviewRequired checkpoint.
• HumanReviewRuntime with save, receive, resume, reconcile, and flush_acknowledgments, plus SqliteReviewStore.
• Generated industry vocabularies under veriproof_sdk::generated::industry.
• VeriproofTestHarness, TestPolicyDecision, and TestPolicyField for network-free tests.
• SqliteDirectiveStateStore and InMemoryDirectiveStateStore for Stop directive state.

Start using the SDK

Open Tools and SDKs in the VeriProof portal, select Rust, and copy its registry configuration and cargo add commands. Start with veriproof-sdk, then add the adapter for each framework your application uses.

Set the application SDK key as VERIPROOF_API_KEY. Hosted VeriProof uses https://ingest.veriproof.app. VeriProof Private uses the ingest API base URL for that instance as VERIPROOF_ENDPOINT. Set VERIPROOF_EDGE_ENDPOINT to route governance calls through a licensed Edge Gateway.

Use the Rust SDK guide for setup and governed-action examples and the Rig and async-openai guides for each adapter boundary. Check SDK categories and framework coverage for what each adapter controls and what stays with the core governed-action helper.