One task. Two providers.
Shared authority.
An agent needs to refund a customer and close their case. See how each provider verifies exactly what Acme authorized—then try changing the request.
Customer charged after cancellation
Refund $40. Close the case.Order 123 · customer Avery
Acme support agent
Acts for Acme under an explicit delegation. Checks each provider's identity before sending customer data.
Ready to verify providersSeparate deployments verify the same authority, retain their own execution state, and sign their own evidence.
Start with the authorized task
Every run gets fresh grants and provider state. Each provider retains its own signing key and execution state across requests and restarts.
Try to break it
These controls alter a real signed request or a provider check across the separate services.
Evidence timeline
Authorization, provider verification and execution are recorded separately.
- Run a scenario to inspect the evidence.
What was authorized
Readable grants with their exact bindings and signed proofs.
No grants issued yet.
Provider execution receipts
No execution evidence yet.
How recognition works in this demo
Acme, the agent and both providers start with a provisioned authority key. The providers accept only Acme's named agent, principal and delegation. Provider identities bind their endpoint to a public key; a real service call challenges key possession. Issuance and enrollment are service-only capabilities. Each provider owns its durable consumption and execution state.
Run a scenario to inspect the public trust root.
Inspect cross-service calls and signed provider state
Run a scenario to inspect service evidence.
Demo boundaries. The authority, PaymentsCo and SupportCo are independently deployed Workers under one demo operator. Provider keys and consumption/effects are isolated in their own durable storage. Runs expire after ten minutes, grants after five minutes, and provider records are retained for one hour. Reset starts a new synthetic run; it does not erase an existing provider record. Trust is provisioned and all financial/customer data is synthetic. This proves separate-service verification, with no claim of independent-vendor adoption, live payments or public certification. The original refund demo remains available with its gateway-backed flows.