paybondpaybond
Sign in

Middleware trace

Visual trace for Paybond agent middleware — local dev dashboard, timeline UI, event model, CLI trace, and hosted replay.

Paybond middleware trace shows the tool boundary lifecycle — not model reasoning. Use it to see policy authorization, handler execution, evidence, and sandbox settlement in one vertical timeline.

Developer reference: /docs/kit/middleware-trace. Hosted developer replay: /demo/agent-trace. For the interactive proof aha (edit evidence → release vs refund), use the Kit Proof Lab.

Try it

Terminal 1:

Terminal
Terminal commandSwipe to inspect long lines
paybond dev loop --offline

Terminal 2 (same project directory):

Terminal
Terminal commandSwipe to inspect long lines
paybond dev trace

Open http://127.0.0.1:9477 — select a run from the sidebar or follow the trace_url printed by smoke/loop.

What you see

PhaseMeaning
ToolSide-effecting tool resolved (tool_selected)
AuthorizePaybond authorized, denied, or held the spend ceiling
EvidenceAuto-evidence submitted after a successful handler
ResultHandler timing, spend finalized, settlement status

Typical flow: tool call → Paybond authorized up to $200.00 (20,000 cents) → tool executed → evidence submitted with reported cost $187.00 (18,700 cents) → settlement released, capturing $187.00 and releasing the unused $13.00.

Surfaces

SurfaceWhen to use
paybond dev trace (:9477)Local iteration after smoke or loop
paybond agent run trace --run-id <id>Headless / CI after bind and execute
/demo/agent-traceShare a visual replay without running the local server
trace_sink / Gateway reporter on bindCustom telemetry or console agent-run timeline
Console intent dossierProduction operator audit (authenticated)

Events persist to .paybond/dev-trace.jsonl so smoke and trace can run in separate terminals. Multi-step runs also write .paybond/runs/<run_id>.trace.json.

Dev, sandbox, and production

Local dashboardTrace events
Default in production appOffOff — pass traceSink or Gateway reporter to opt in
Default after paybond dev loopOn (.paybond/dev-trace.jsonl)On via dev collector
Console operator viewN/AIntent dossier always; agent-run timeline when Gateway reporting is wired

Full matrix, CLI, and SDK production examples: /docs/kit/middleware-trace#production-examples.

Table-format smoke prints:

✓ Trace → http://127.0.0.1:9477/runs/<run-id>
✓ Replay → https://paybond.ai/demo/agent-trace?intent=<intent-id>

JSON smoke includes trace_url, agent_trace_url, and console_url when a intent id is present.