Live product demo
See what developers and owners actually do
Run a real sandbox clearance without creating an account. The developer side creates a ClearanceIntent; the owner side approves with a browser passkey biometric in the ZeroGrant Element; the result panel shows only the bounded output.
Real passkey clearance
A recruiter app asks a yes or no fit question. The owner reviews purpose and categories, then approves or declines. The app receives a bounded result, not the underlying file. Approve uses your browser passkey or biometric (Touch ID, Face ID, Windows Hello). Sandbox never charges. No sign-up required.
Demo idle. Start a sandbox clearance when ready.
1. Developer app
Server key onlyYour backend creates a ClearanceIntent with a secret API key. The browser never sees that key. It receives a one-time client_secret for the Element iframe.
- Scenario
- Hiring fit clearance
- Purpose
- sandbox_clearance
- Adapter
- sandbox_boolean
- Categories
- sandbox
- Question
- Is this candidate a fit for the listed role?
2. Data owner
Real ElementThe owner reviews recipient, purpose, and categories, then unlocks with a device passkey. Approval borrows authority for this request only.
Owner panel waits for an intent
Start the clearance on the left. The Element mounts here with the one-time client secret only.
3. Bounded result and lifecycle
After approval, the developer app receives a purpose-shaped JSON result and cryptographic proof reference. Raw source data is not returned. Decline ends the request with no result.
Event timeline
- Events appear as the clearance progresses.
Bounded result
Build this in your product
Get sandbox API keys, install the SDK, and run the same ClearanceIntent loop in your own app. Sandbox stays free and never charges Stripe.