Usage Proof Ledger
Real session events the workbench emitted, plus a public receipt verifier. Bounded surface — no raw secrets, no admin keys, hash-prefix fields only. For an explanatory walkthrough of what proof exists and what it does not claim, see the Proof Center.
Public-beta proof bundles
Bounded scope, strict-public-beta redaction. Bytes are returned inline — no signed URL is exposed.
No proofs generated yet for this session. Generate a proof from a successful 200 + receipt event to bundle the session-owned audit slice for offline verification.
What this proof bundle proves
- The session-owned receipts and the audit-event slice that produced them.
- The Ed25519 signature over the bundle manifest.
- The sha256 of every bundled member.
What this proof bundle does not prove
- Public production billing — not launched.
- Customer revenue or signed pilot — not claimed.
- Enterprise GA — not claimed.
- Official SOC 2 / ISO 27001 / HIPAA / PCI / SAML / SCIM certifications — not claimed.
Connecting to live ledger…
Verify a receipt
Paste a receipt ID from the X-AgentTrust-Receipt-Id header on a successful 200. The widget fetches the public GET /v1/receipts/:id route and renders the bounded receipt body. To verify the Ed25519 signature offline, open /verify.
What this surface is
- Real session-scoped audit events. The four self-serve setup actions plus the per-request gateway pipeline events (identity, policy, payment, receipt) for calls correlated to your sandbox session via the gateway-injected session-id-hash.
- A bounded receipt verifier that reads from the public
/v1/receipts/:idroute — same source the landing proof center consumes. - A bridge from "I just made a sandbox call" to "here is the request, the receipt, and how to verify it" without leaving the workbench.
What this surface is not
- Not a real payment ledger. The sandbox proof header is a triple-gated demo path; no real settlement happens.
- Not a terminal-session ledger. Calls from
pnpm public-beta:tryuse a separate sandbox session with its own cookie jar; those events appear under their own session, not here. Use the browser-issued session for the in-console ledger. - Not an enterprise GA workspace. No paid plan launched, no signed customer pilot, no SOC 2 / ISO 27001 / HIPAA / PCI / SAML / SCIM official certification claimed.