Integrations, LangGraph

Put business rules around LangGraph actions

Keep building in LangGraph. The VeriProof LangGraph adapter checks each graph run against your rules, and the Python core SDK covers the individual steps that need their own check. Your graph keeps its state and flow.

How it connects:LangGraph Enforce adapterPython core SDKGraph state stays in LangGraph

Control the work that matters

A message sent or a record changed can have real consequences. Use a policy-controlled run when the graph needs permission to proceed.

Keep your graph and its state

Your graph stays in LangGraph, along with its state and the logic that selects the next branch.

Give business rules a place in the workflow

Check a proposed action against your VeriProof policies. The decision stays available for later review.

Act on the policy result

Continue, stop, or wait for review. Your application applies the result where it controls the action.

Connect with the LangGraph adapter

veriproof-sdk-adapter-langgraph checks a complete graph run: the input before the graph starts, and the result before your application releases it. It installs the Python core SDK, veriproof-sdk, along with it.

The adapter doesn't check each node on its own, streamed output, or graph calls made outside it. When one node sends a message, moves money, or changes a record, wrap that action with the core SDK so it gets its own check.

Your application keeps the LangGraph checkpoint, the wait for a reviewer, cancellation, and the final business outcome.

Developers find package access in Tools and SDKs. See what the LangGraph adapter checks →

Common integration questions

LangGraph continues to run the graph, keep its state, and select the next branch. VeriProof supplies the policy result and decision history for the actions you choose to control.

Your application keeps the checkpoint, validates the signed review result through the core SDK, and directs LangGraph to the next branch. The adapter and the core SDK return the same typed results, so the handling is the same either way.

Start with nodes that change records, send messages, or call external tools. Send only the details your policy and reviewers need.

Keep your graph. Add control and decision history.

Try it on your own graph with a free Developer account, or tell us which action you want to govern.