paybondpaybond
Sign in

Use case

Settle delegated agent work without trusting the whole chain.

When one job fans out across agents, tools, vendors, and reviewers, payment still needs one reviewable release-or-refund record. Paybond keeps the commercial decision tied to an agreed budget, signed evidence, and a replayable settlement history.

Your orchestrator runs the work. Paybond verifies what happened before money moves, records the review path when work is partial or disputed, and produces records finance, compliance, and partners can inspect later.

Start now>View walkthroughKit quickstartIntent and evidence example

One commercial job, many contributors.

A practical multi-agent flow needs flexible execution and a stricter settlement record. The buyer should not have to reconstruct what happened from callbacks, chats, and screenshots.

  1. A buyer funds one commercial job

    The job has a budget, deadline, parties, and clear completion criteria before agents start spending time or calling tools.

  2. The orchestrator delegates execution

    Planner agents, tool routers, vendor agents, and internal reviewers can all contribute without making Paybond the workflow engine.

  3. Evidence lands in one record

    Structured results, artifact hashes, operator review events, and dispute materials point back to the same settlement lifecycle.

  4. Settlement stays reviewable

    Paybond evaluates the evidence, routes exceptions into review when needed, and preserves a release/refund record that can be replayed.

Your runtime runs the work. Paybond wraps settlement.

Keep planning, retries, model choices, and tool routing in your own system while Paybond keeps the commercial boundary reviewable.

Your orchestrator runs execution
It plans the job, assigns agents and tools, handles retries, stores raw artifacts, and owns model/runtime behavior.
Paybond controls the settlement boundary
It binds the budget, allowed actions, evidence requirements, release/refund rule, review actions, and settlement history.
Customer systems keep their records
Large files, logs, PDFs, and application data can stay in your storage while Paybond stores signed bindings and artifact hashes.

Control the money decision while execution stays flexible.

Your workflow can fan out across agents and tools. The settlement record stays tied to the same agreement, evidence, and review path.

  • One agreement for fanned-out work

    Define who is involved, what budget is reserved, what evidence is expected, and what counts as completion before execution spreads across agents.

  • Evidence from every contributor

    Agents and operators can attach signed tool outputs, structured result envelopes, artifact hashes, review decisions, and dispute materials to the same lifecycle.

  • Guardrails before side effects

    Capability checks confirm which agents and tools are allowed to act before delegated work runs, keeping spend and authority bounded.

  • Review paths for partial outcomes

    When a task fails, arrives late, or needs human judgment, operators can review the same evidence trail without silently editing the settlement record.

A reference flow for multi-agent settlement

Use your existing runtime for execution; keep funding, evidence, review, and release/refund decisions on one track.

  1. Step 1

    Define the commercial job

    Capture the parties, budget, deadline, evidence requirements, and release/refund rule as the agreement boundary.

  2. Step 2

    Reserve the budget

    Commit funds through an approved rail so delegated work happens inside an explicit spend boundary.

  3. Step 3

    Verify delegated actions

    Use Kit, runtime wrappers, or protocol trust to check allowed actions before an agent or tool performs side-effecting work.

  4. Step 4

    Collect signed evidence

    Attach structured results, artifact hashes, and operator decisions to one settlement record as the workflow runs.

  5. Step 5

    Settle and export the record

    Evaluate the evidence, route release, refund, or dispute review, and anchor the canonical history in the Ledger. Gateway emits protocol receipts when a delegated mandate is imported; Signal derives tenant-private standing artifacts from verified outcomes.

Exception path

Partial work should not become an off-ledger negotiation.

Multi-agent work often fails in uneven ways: one tool succeeds, one vendor misses an SLA, and an operator needs to decide whether to release, refund, split, or escalate. Paybond keeps that decision inside the same settlement record.

  • The funded budget remains tied to the original agreement while review happens.
  • Operators see the submitted evidence, timeline, and dispute material before acting.
  • Resolution actions become attributable events that can be exported for finance, compliance, partners, or arbitration.

What teams can use after the work is done

The useful output is not another task log. It is a portable record that explains why money moved, paused, or returned.

  • Reviewable settlement record

    A single record tying the agreement, budget, evidence, operator actions, and release/refund decision together.

  • Signed evidence trail

    Attributable evidence bindings and artifact hashes that reviewers can connect back to the workflow without relying on screenshots or ad-hoc callbacks.

  • Dispute and audit package

    Evidence, timeline, provenance, and case material that can be exported for internal review, partner assurance, or arbitration handoff.

  • Protocol receipts and standing artifacts

    Gateway produces protocol authorization and settlement receipts for imported delegated mandates. Signal produces private operator and portfolio standing artifacts from verified settlement history.

How it plugs into agent systems

Choose the integration path that matches where delegation already happens.

  • Kit guardrails for agent runtimes

    Use TypeScript or Python Kit to open tenant-bound sessions, verify capabilities before tool work, and submit signed evidence after guarded execution.

  • Framework-specific wrappers

    Use provider-agnostic Kit wrappers with OpenAI, Gemini, Claude/Anthropic, LangGraph, local models, custom runtimes, or the tenant-bound MCP server depending on where your agents run.

  • Protocol trust for delegated systems

    Publish A2A discovery, import verified external mandates, recognition-gate Harbor mutations, and export protocol receipts when the bound workflow reaches a terminal outcome.

  • Console review and exports

    Operators can review intent queues, disputes, settlement exceptions, Signal standing, and compliance exports from tenant-scoped product surfaces.

Agent integration docsProtocol trust docs

Multi-agent coordination without losing the settlement guarantees.

Paybond is designed so tenant identity comes from authenticated credentials, delegated actions stay bounded by capabilities, and release/refund decisions remain explicit and replayable.

Guarantees

  • No tenant IDs accepted from unauthenticated clients; scope is derived from credentials.
  • Evidence and operator actions remain attributable via signed provenance.
  • Release/refund decisions follow deterministic evaluation over the recorded evidence.
Explore platform docs

Where it fits

Use this where delegated work crosses agents, teams, tools, or partners.

  • Agent marketplaces

    Coordinate buyers, sellers, and agent providers with funded tasks, evidence-backed completion, and a neutral dispute path.

  • Enterprise agent fleets

    Keep delegated spend, operator review, dispute handling, and audit exports tenant-safe as workflows scale across teams and tools.

  • Risk & underwriting

    Derive standing and reliability signals from signed settlement history rather than unverifiable dashboards or self-reported task status.

Multi-agent workflows FAQ

Common questions about coordination, evidence, and deterministic settlement.

Is Paybond a workflow engine?

No. Your orchestrator still plans and runs the work. Paybond provides the settlement boundary around that work: budget, capability checks, signed evidence, review actions, provenance, and receipts where the protocol flow supports them.

How do you handle non-deterministic agent behavior?

Execution can be non-deterministic; settlement should not be. Paybond keeps release and refund decisions tied to a deterministic check over signed evidence and a canonical provenance history.

What counts as evidence?

Evidence is any signed artifact your workflow produces: tool outputs, structured result envelopes, artifact hashes, operator review events, or dispute materials. Raw files can remain in your systems while Paybond stores the signed binding and references.

How do protocol receipts and Signal artifacts differ?

Protocol receipts are Gateway-issued authorization or settlement records for imported delegated mandates. Signal artifacts are tenant-private standing, receipt, and portfolio records derived from verified settlement history.

What does tenant isolation mean in practice?

All reads, writes, and exports remain explicitly scoped to tenant and operator identity derived from authenticated credentials. Cross-tenant access is treated as a severity-zero incident and defended at every boundary.