Sandbox

Same agent. Two actions. One commits, one stops.

Both receipts below are real ES256-signed v2.2 receipts — the same format the production gateway emits. Click Verify on either side to run the four-check verification. Click Open receipt to see the full audit chain.

About this sandbox

• Both receipts are signed with ES256. The sandbox keypair is published at /.well-known/jwks.json with EP-extension lifecycle fields.
• Receipts are deterministic per fixture. Pasting the JSON into /verify always returns valid; tamper one byte and verification fails.
• Canonicalisation follows RFC 8785 JCS. The same wire format the production gateway uses.
• No signup, no rate limit beyond a per-IP bucket, no persistence beyond the in-process receipt store.

Production posture — KMS-signed receipts, persistent audit chain, multi-replica JWKS — is documented on the Security page.

Same agent. Two actions. One commits, one stops.

About this sandbox

Same agent. Two actions. One commits, one stops.

About this sandbox

Deterministic execution pipeline · 8 steps · all passed

Deterministic execution pipeline · 3 steps · halted