GAVEL Sandbox
Plug in any agent.
Watch GAVEL rule.
GAVEL from GenXis gives each AI agent run a tamper-evident receipt, signed by GAVEL and checkable by anyone, so a company can prove what its agents tried to do and which actions its rules blocked.
One click. No login. No setup.
Pick a scenario and run a well-behaved agent or a rogue one against sample mail, files, clipboard and CRM. Every action is decided by a real policy engine, and the whole run is submitted to production GAVEL, which returns a receipt signed by its published issuer key — one you can recompute yourself.
Transcript
Hi, I'm Daryl Ledyard, founder of GenXis.
AI agents don't just answer questions anymore. They take actions: reading files, sending email, pulling data. And when an agent goes off-script, most companies can't prove what it actually tried to do.
That's what GAVEL from GenXis is for.
On this page, pick an agent and run it. Every action it attempts is checked against your rules, so you see what was allowed and what was blocked.
Then GAVEL signs a receipt for the whole run. That receipt is tamper-evident: change one character and it fails. You can check it right here.
Here's the important part. The receipt doesn't say the agent was good. It proves the record is real, so you can trust exactly what happened, good or bad.
Run the good agent. Run the bad one. Then verify the receipt yourself.
When you're ready to put this on your own agents, get started free at genxis.com.
Step 1 · choose an agent
Same sandbox. Any company's agent.
Scenarios are presets in one config file. Swap in a real agent by pointing a preset at its API — the engine, policies and production receipts don't change.
Loading scenarios…
Every action, ruled
Signed receipt
Ed25519 · SHA-256 · RFC 8785“Verified” proves this receipt has not been altered and was issued by GAVEL’s trusted production key. It does not mean the agent behaved — that is the agent verdict above.
Step 2 · don't trust us, check it
Verify any receipt
Paste a receipt
Paste a production GAVEL receipt to recompute its signed root, check its Ed25519 signature against GAVEL's published issuer key, and ask GAVEL's /v1/receipts/verify. Sandbox log records are checked against the sandbox DEMO log key and hash chain.
Verify offline
Production receipts: the issuer public key is published at gavel.genxis.com/v1/issuer-keys and is embedded in each receipt. The signature covers the RFC 8785 canonical receipt without its signature and envelope_root fields. For the sandbox's own demo-signed step log, download the DEMO log key and the 40-line verifier, then run:
pip install cryptography python3 verify.py receipt.json pubkey.json
Under the hood
Three policies, one verdict format
Mail may only be listed, read, or sent within the one domain the scenario allows. A second recipient outside it fails the whole send.
Only .docx files under the docs root. Paths are normalized and symlinks resolved before the policy engine sees them, so ../ and symlink escapes are caught.
Clipboard reads and CRM writes are scanned for card numbers (Luhn check). Card numbers are masked in every receipt.