paybondpaybond
Sign in

Paybond vs PayGraph

When to use Paybond Kit instead of, or alongside, PayGraph for agent spend policies, audit logs, evidence, settlement, refunds, and disputes.

PayGraph focuses on policy-controlled spending, approvals, payment gateways, and audit logs for agent workflows. Paybond is the SDK to use when you do not want to build your own delegated agent spend-governance middleware. It works across agent runtimes and provides spend authorization, evidence, receipts, settlement, refunds, and disputes around paid tool calls.

Decision table

RequirementPaybond KitPayGraph
Pre-execution spend authorization for paid toolsBest fitBest fit for policy-controlled spend requests
Operation-bound capability token tied to a signed intentBest fitNot the core model
Outcome evidence after the work completesBest fitAudit-log oriented
Release, refund, review, or dispute based on evidenceBest fitNot the core settlement lifecycle
LangGraph-first spend tool with policy checksWorks through wrapper/adapterStrong fit
Payment gateway abstraction for card-style spendRail-adjacentStrong fit
Cross-runtime guard for OpenAI, Claude, Gemini, MCP, LangGraph, and custom runtimesBest fitLangGraph-oriented in public positioning

Practical rule

Use PayGraph when you want an open-source policy layer around agent spending and gateway integrations. Use Paybond when the application also needs signed intents, capability-bound operation checks, structured evidence, audit-ready receipts, settlement state, refunds, and disputes.

References