paybondpaybond
Sign in

Use case

Agent spend controls for runtimes and orchestrators.

Paybond Kit provides integration primitives that make the invariants easier to keep than to break: tenant-scoped sessions, delegated spend authorization, tool-call budget checks, signed evidence submission, and proof-gated release with a portable receipt.

Start now>Explore KitKit quickstart

Integration primitives for production agent systems.

Kit keeps tenant, capability, and signing invariants intact while you integrate with the runtimes you already run.

  • Tenant-scoped sessions

    Keep tenant identity derived from authenticated credentials and carried end-to-end through SDK calls.

  • Spend checks in the workflow

    Authorize delegated spend and tool-call budget requests before agents execute paid APIs, vendor actions, or settlement work.

  • Signed evidence submission

    Attach signed artifacts to the same authorize → settle trail so evaluation, exports, and disputes all reference the same record.

  • Minimal integration surface

    Integrate with orchestrators and tool routers you already run, including x402 stablecoin funding when a tenant enables that rail.

How Kit fits into the workflow

From tenant-scoped session to evidence and settlement—without hand-rolled plumbing.

  1. Step 1

    Open a tenant session

    Create a tenant-scoped SDK session derived from authenticated credentials and runtime configuration.

  2. Step 2

    Check capabilities

    Verify which operations are allowed before invoking tools or delegating to sub-agents.

  3. Step 3

    Fund stablecoin intents

    When the tenant uses `x402_usdc_base`, advance Paybond's PAYMENT-REQUIRED and PAYMENT-SIGNATURE handshake to fund the intent in USDC on Base.

  4. Step 4

    Attach evidence

    Submit signed evidence artifacts as outputs are produced so provenance stays complete.

  5. Step 5

    Drive settlement

    Commit budgets and trigger evidence evaluation so release/refund decisions remain deterministic.

  6. Step 6

    Derive receipts

    Use ledger provenance and Signal receipts for downstream verification, compliance, and underwriting.

Integration should preserve the guarantees.

Kit’s role is to make tenant isolation, signing, and evidence capture the default behavior—so your orchestrator can scale without eroding the invariants that settlement depends on.

Guarantees

  • Tenant scope is derived from authenticated credentials—not browser-supplied identifiers.
  • Evidence artifacts are signed and attributable to operators/agents.
  • Capability checks keep delegation bounded and auditable.
  • SDK callers can request Stripe-backed or x402 rails without ever submitting raw settlement destinations.
Kit docs

Where it fits

Use Kit where your agents live: orchestrators, tool routers, and evidence pipelines.

  • Agent orchestrators

    Add settlement and evidence primitives around the planning and execution engine you already use.

  • Tool routers and sandboxes

    Enforce capabilities and attach signed tool outputs as evidence for later verification.

  • Org integrations

    Keep tenant boundaries explicit while connecting agent workflows to procurement, billing, and compliance controls.