Core SDK
Check policy before application-owned work starts and before its result is released. Handle typed results, human review, and Stop directives.
Developer SDK
Connect your application in the language you use
Bring policy decisions, human review, and evidence into your application. Start with a 1.0.0 core SDK, then add an adapter only for its documented framework boundary.
TypeScriptPython.NETGoJavaRust
SDK 1.0
Released SDKs and framework integrations
The 1.0.0 catalog includes 6 core SDKs and 35 Enforce adapters. Every package in the release enforces policy: a core SDK for each language, and an Enforce adapter for each supported framework.
Tools and SDKs lists the packages available in your environment and provides their installation commands. Rust 1.96 or later is required for the Rust SDK. Go 1.26.6 or later is required for the Go SDK. Find all runtime requirements and exact boundaries in the SDK package catalog.
Framework adapters
Find the adapter for your framework
Start with the core SDK for your language, then add the adapter for the framework your agent runs on. Select a language to see exactly what each adapter checks.
Scroll horizontally to see all columns.
| Language | Core SDK | Enforce adapters for |
|---|---|---|
| TypeScript | @veriproof/sdk-core | Anthropic SDK, Express, Fastify, Genkit, Google GenAI, LangChain.js, LlamaIndexTS, Mastra, Next.js, OpenAI Agents, Vercel AI SDK |
| Python | veriproof-sdk | Anthropic SDK, CrewAI, Google ADK, LangGraph, LlamaIndex, Microsoft Agent Framework, OpenAI Agents, Pydantic AI |
| .NET | Veriproof.Sdk.Core | AutoGen, Microsoft Agent Framework, OpenAI .NET, Prompty, Semantic Kernel |
| Java | com.veriproof:veriproof-sdk-core | LangChain4j, Micronaut LangChain4j, OpenAI Java, Quarkus LangChain4j, Semantic Kernel Java, Spring AI |
| Go | veriproof.app/sdk/go | Anthropic Go, LangChainGo, OpenAI Go |
| Rust | veriproof-sdk | async-openai, Rig |
Framework coverage
Enforce only where the adapter owns the operation
An Enforce adapter enforces policy only when it controls three things for its documented operation: whether the call is sent, whether the change it would make happens, and whether its output is released. Calls that go around the adapter are not covered.
Enforce adapter
Apply core SDK decisions to one documented framework operation. Calls outside that boundary remain application-owned.
The framework matrix shows the category and documented boundary for each package.
Govern application-owned framework calls
For a framework without an adapter, or a step an adapter doesn't cover, place the core SDK around the application-owned model call, tool, workflow, or business action.
Find the 1.0.0 packages and confirm each adapter boundary before installation.
Connect the decision to what happened
Capture decision evidence
Keep the decision context, policy result, and reported application outcome connected across supported languages.
Evaluate policy before protected actions
Can this action proceed? The policy result tells your application whether to continue, change the action, pause for review, or stop.
Bring in a reviewer
Some decisions need judgment. A review can capture an approval, limit, choice, or permitted correction with the context behind it.
Record the application outcome
Signed-response helpers connect the human decision to your application, which retains its progress and carries out the action.
Keep human review connected to your workflow
Your application receives a signed response tied to the paused action. The SDK checks that response, while your application manages its saved progress and final outcome.
Find the right fit for your framework
Start with the actions you want to control. The capability matrix helps you choose a package for your model calls, tools, and review workflow.
Use the language guides for maintained 1.0.0 setup and examples.
License and source access
The SDKs use the standard VeriProof software license, not an open-source one. Source for the SDKs and the platform is available on request. On SaaS plans, your team gets the security review tier, to read and inspect the code. Changing it and running it in your own environment is the modification tier, which comes only with Private Enterprise. How source access works
Which application will you connect?
Connecting the agent is the developer's part. The business owner, compliance, reviewers, and auditors each work in their own portal. When one of their rules needs data the agent doesn't send, the fix request comes to you.