Pay-per-use data and tools (x402)
The agent pays a small amount each time it uses a paid data source or tool. Your rules cap what it spends and which payment networks it can use.
Supported agents
Framework, custom code, Microsoft Copilot Studio, MCP, or a browser: however an agent was built, VeriProof checks its actions against your rules and records each decision the same way.
Find the closest match. Many teams use more than one.
An adapter plugs into the agent framework your developers already use, so they don't have to add the check by hand at every step. 35 adapters are available today.
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 |
An agent that spends money needs a limit, and a person who approves the exceptions. VeriProof checks each payment before your wallet or provider moves any money, and sends anything over the limit to the budget owner.
The agent pays a small amount each time it uses a paid data source or tool. Your rules cap what it spends and which payment networks it can use.
The agent picks a paid provider from a catalog. Rules check that the provider is verified and that the session stays under its cap.
The agent checks out for a customer or employee. Your rules hold it to the payee, amount, and time limit that person approved.
The agent pays suppliers in stablecoins. Payments to new suppliers and large cross-border transfers go to your treasury team first.
Same record, six portals
However an agent connects, its decisions land in portals built for the business owner, risk and compliance, governance engineers, developers, auditors, and administrators. Work moves between them through built-in handoffs.
An agent action needs a person
Reviewer with authority
A rule needs data the agent does not send
Developer
A governance engineer changes a rule for a production agent
Administrator or Compliance Officer
A control is not met
Assigned owner
A risk needs a business decision
Business Owner
An audit begins
Auditor
Those connect the tools your teams work in rather than your agents, so they have their own directory, organized by human-in-the-loop reviews, GRC and compliance, and security and monitoring. Browse integrations →
Tell us where it runs and what it needs to do. We'll tell you which connection fits and reply within one business day. If you build agents for clients, the partner program covers implementation work.