paybondpaybond
Sign in

Use case

Drop-in SDKs for agent runtimes and orchestrators.

Paybond Kit provides integration primitives that make the invariants easier to keep than to break: tenant-scoped sessions, capability checks, signed evidence submission, and clean handoffs into Harbor, the Ledger, and Signal.

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.

  • Capability checks in the workflow

    Enforce which agents can perform which actions before they execute, not after something goes wrong.

  • Signed evidence submission

    Attach signed artifacts to the intent lifecycle so evaluation, exports, and disputes all reference the same record.

  • Minimal integration surface

    Integrate with orchestrators and tool routers without replacing your runtime or reshaping your entire system.

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

    Attach evidence

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

  4. Step 4

    Drive settlement

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

  5. Step 5

    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.
Kit docs

Where it fits

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

  • Agent orchestrators

    Add settlement and evidence primitives without replacing the planning/execution engine you already use.

  • Tool routers and sandboxes

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

  • Enterprise integrations

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

Agent SDK integrations FAQ

Questions about runtimes, languages, and invariants.

Do I need to adopt a specific agent framework?

No. Kit is designed to integrate with orchestrators and runtimes you already use. It provides primitives for tenant context, capability checks, and evidence submission.

What languages are supported?

Kit focuses on practical SDK coverage for production stacks. See the Kit docs for current language support and reference implementations.

Is tenant identity passed from the client?

No. Tenant scope should be derived from authenticated credentials and enforced at every boundary. The SDK is designed to keep that model intact.

How does this connect to Harbor, Ledger, and Signal?

Kit helps attach evidence and enforce capabilities while you drive settlement through Harbor. The Ledger records signed provenance; Signal derives receipts and rollups from that history.