paybondpaybond
Sign in

Paybond Kit

Integrate Harbor without rewriting your runtime.

Kit is the SDK layer that handles tenant-scoped sessions, signing, and Harbor routes from your agent environment—so you don’t hand-roll JWT plumbing or provenance formatting.

Start now>View docs

Integration primitives that keep guarantees intact.

Kit makes the tenant and signing invariants easier to keep than to break.

  • Tenant-bound sessions

    Kit exchanges long-lived credentials for short-lived, tenant-scoped sessions to keep calls isolated by default.

  • Signing built in

    Submit intents and evidence with explicit identity and signatures so downstream settlement and receipts stay verifiable.

  • Capability-aware requests

    Attach capability context and your own delegated tool names so agent actions stay bounded and policy-checkable.

  • Works in real runtimes

    Designed for agent orchestration stacks: retries, idempotency expectations, and structured evidence payloads.

How Kit fits into the settlement lifecycle

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

  1. Step 1

    Open a session

    Use your service account credentials to open a tenant-scoped session for Harbor operations.

  2. Step 2

    Create an intent

    Sign the budget, predicate, and payee binding so the clearing intent is cryptographically anchored.

  3. Step 3

    Perform the work

    Your agent executes in your preferred runtime while keeping evidence and your own tool namespace explicit.

  4. Step 4

    Submit evidence

    Kit signs and submits structured evidence payloads to Harbor for deterministic evaluation.

  5. Step 5

    Verify outcomes

    Harbor’s settlement decision and Signal receipts can be derived from the signed provenance Kit helped produce.

The SDK should reinforce the platform invariants.

Kit is designed to keep tenant identity and signing explicit, so settlement and receipts don’t depend on ad-hoc conventions in your app.

Guarantees

  • Tenant identity is explicit and carried across requests.
  • Signing flows are standard across languages and runtimes.
  • Evidence schemas remain structured to support deterministic evaluation.
Explore APIs

Designed for agent runtimes

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

  • Agent orchestration stacks

    Integrate Harbor into tool routers and runtimes with minimal surface area and predictable request shapes.

  • Evidence pipelines

    Produce structured evidence artifacts and submit them with signatures—ready for disputes, exports, and receipts.

  • Multi-tenant platforms

    Keep tenant boundaries consistent between your product, Paybond Gateway, and Harbor settlement operations.

Kit FAQ

Language support, invariants, and when to go direct-to-API.

Do I have to use Kit to use Paybond?

No—but Kit is the fastest path to correct tenant-scoped sessions and signing. You can integrate directly with APIs if you implement the same invariants yourself.

Which languages are supported?

Kit currently highlights TypeScript on Node.js 22+ and Python. The goal is consistent request shapes and signing semantics across runtimes.

How does Kit relate to Harbor?

Kit is the client-side integration layer. Harbor is the settlement engine that evaluates predicates and releases/refunds funds based on verifiable outcomes.

What does “tenant-bound” mean in practice?

Requests carry explicit tenant context derived from authenticated credentials. Kit’s session handling is designed to prevent accidental cross-tenant calls.