paybondpaybond
Sign in

Middleware trace

See what sandbox smoke returns — step by step.

Run paybond agent sandbox smoke after paybond login, then replay the JSON here or open the local paybond dev trace vertical timeline dashboard.

Policy before tools

A preset or policy file defines which operations are paid, capped, and evidence-backed before your agent runs.

Authorize then execute

Paybond approves spend against a sandbox intent, then your tool handler runs — denied calls never reach vendor APIs.

Evidence drives settlement

Tool results map into completion presets; sandbox simulates release so you see the full loop without production keys.

Sandbox smoke replay

Middleware trace from CLI JSON

This timeline replays the output of paybond agent sandbox smoke. Run the command locally, then open paybond dev trace for live runs.

Operation travel.book_hotel
npx -p @paybond/kit paybond agent sandbox smoke \
  --preset travel \
  --result-body '{"status":"completed","cost_cents":18700}' \
  --format json
ReadyPolicyStep 1 of 8

Policy loaded

preset · paybond.policy

The travel policy preset defines which tools are side-effecting, spend caps, and the completion preset used for evidence.

Smoke JSON slice

{
  "policy_file": "paybond.policy.yaml",
  "operation": "travel.book_hotel",
  "requested_spend_cents": 18700,
  "completion_preset": "cost_and_completion"
}

Want the full settlement lifecycle? Open the settlement walkthrough. For integration steps, see quickstart-agent.