Rules outside the code
Risk and compliance set the limits in VeriProof. Changing a refund limit doesn't wait for the next release of the agent.
Integrations, agent frameworks
Keep your agent framework. Add the check before the action.
Your developers chose a framework for good reasons, and nobody wants to rebuild the agent to add controls. VeriProof fits around the calls the framework already makes. Each action is checked against the rules for its application, exceptions reach whoever holds the authority, and agents built on different frameworks end up in the same portals and records.
An Enforce adapter for the framework you already use
An adapter sits inside the framework's own calls, so the check runs without your developers writing it around each one. The 1.0.0 release includes 35 of them across six languages, and every one enforces your rules: the action goes ahead, changes, waits for a person with authority, or stops.
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 |
Each adapter covers a specific part of its framework, such as a model call, a tool call, or a complete run. The coverage guide shows exactly what each one checks and what it leaves to your code.
Anything else: wrap the action you own
For a framework your team wrote, or a step an adapter doesn't cover, place the VeriProof core SDK around the model call, tool, or business action your application controls. Core SDKs ship for TypeScript, Python, .NET, Java, Rust, and Go, and they apply the same rules as the adapters.
The framework keeps its state and flow. Your code applies the answer, whether it's Allow, Warn, Transform, Escalate, or Deny. See the LangGraph example for how an adapter and the core SDK work together in one graph.
What the business owner gets
The right person for each exception
A request the rules won't allow on their own reaches someone with authority, with the facts attached, while the application holds the work.
One record per decision
The rule version, the reviewer's answer, and the reported outcome sit together, and each role reads them in its own portal.
Where does your agent need a check?
Bring the action your agent takes and the framework it runs on. We'll show you where the check goes and reply within one business day.