paybondpaybond
Sign in

Your agents can spend. Funds don't release until the work is proven.

Approvals clear charges one by one. None of them prove the work was delivered.

Authorize the action. Verify the outcome.

No signup required

npx -p @paybond/kit paybond dev loop --offline

Offline Kit loop: authorize spend → execute tool → verify evidence. No account.

Kit authorizes the spend, verifies completion evidence, then releases or refunds — one signed receipt Finance can replay.

Payments Ask "Can It?" Paybond Asks "Should It — And Did It Deliver?"

A successful charge is not proof the work was done

Banks settle the payments. Paybond settles the argument.

Your payment provider can confirm that $197.50 moved. It can’t tell you whether the booking actually completed, what evidence satisfied release, or why finance should trust the payout — the enemy is treating a cleared charge as delivery.

  1. Who delegated this agent's authority?
  2. Which signed intent bound the spend?
  3. What evidence satisfied completion?
  4. Can Finance replay the release or refund?

Why today's controls fail

Payment systems authorize spend. They don't verify outcomes.

Traditional approvals answer "Can this charge happen?" Paybond answers "Did the work actually happen?"

46%
of CFOs name cost uncertainty / lack of transparency as their #1 internal AI concern (Deloitte CFO Signals)

  • $4,788

    in three minutes

    Traditional controls

    A $500 approval limit allowed twelve $399 purchases to clear independently. Every payment succeeded. None proved the work was completed.

    With Paybond

    Funds stay pending until completion evidence is verified. Successful work settles automatically. Failed or incomplete work can be refunded before money is released.

    Proxy post-mortem ↗

  • $47,200

    over 11 days

    Traditional controls

    A retry spiral kept charging while health checks stayed green — billing truth arrived after the damage.

    With Paybond

    Funds aren't released simply because a service stays healthy. They settle only after verified completion.

    clyro.dev ↗

Paybond doesn't just stop bad payments—it creates an audit trail Finance can replay months later, with the intent, evidence, decision, and settlement tied together in one signed receipt.

From authorize to signed receipt

Authorize → execute → verify → settle. Each step maps to a Kit call — paybond.authorize, your tool, paybond.verify, then a signed receipt.

  1. Authorize

    paybond.authorize

    Bind operation, budget, and completion rule before the tool runs.

  2. Execute

    Your tool call

    Agent runs the paid tool under that authorization.

  3. Verify

    paybond.verify

    Submit completion evidence against the signed rule.

  4. Settle

    Signed receipt

    Funds release on pass — or refund on fail — Finance can replay.

Portable receipt

The object finance can keep

One signed record: intent, evidence decision, release or refund. Rail-neutral. Runtime-portable.

  • Release — evidence passed; funds paid out
  • Refund — evidence failed; funds returned
  • Held — awaiting completion evidence
Illustrative travel receiptpaybond.agent_receipt_v1
"operation"
"travel.booker.purchase"
"budget_cap"
"$200.00"
"evidence.confirmation"
"AA-8JZ3QK"
"outcome"
"release · $197.50"
signature · offline-verifiable

Wrap the paid tool call

Install Kit, authorize spend, run the tool, verify evidence. Same loop as paybond dev loop --offline.

  • paybond.authorizeBind spend before the tool runs
  • paybond.verifySubmit evidence; release or refund
  • paybond loginMint a sandbox API key
  • paybond dev loop --offlineRehearse the full loop with no account
  • paybond agent sandbox smokeEnd-to-end smoke without writing integration code
Full Kit docs →
paybond.kit.ts
$ npm install @paybond/kit
const decision = await paybond.authorize(toolCall);const result = await tool.execute(args);await paybond.verify({ evidence: result });

Sandbox is free. Production is pay-as-you-go or credits.

See pricing →

Settlement isn't proof.

Prove it on your machine

Same authorize → execute → verify loop. No account. Connect Kit when you go live.

No signup required

npx -p @paybond/kit paybond dev loop --offline

Offline Kit loop: authorize spend → execute tool → verify evidence. No account.