Permission is specific.
Allow a swap. Deny a transfer. Define the destinations your agent can use.
Intelligence needs boundaries.
VORN
Initializing agent· · ·
AGENT PERMISSION LAYERInteractive prototype / 001
Human intent. Defined limits.Explore the protocol ↓
01 Explicit permissions02 Bounded spending03 Visible decisions04 Instant revocation
01 / The principle
Autonomy.
Within limits.
An agent can make a request.
Your policy decides if it goes through.
INPUT
→Agent intent
Swap 25 USDC
POLICY CHECK
→[ VORN ]
Permission · Destination · Budget
DECISION
Allow or deny
Every result, with a reason.
Every amount counts.
Set limits per request, per day and per session. A denied request spends nothing.
Nothing in the dark.
Inspect every approval and denial. Change the rules or revoke the session at any time.
02 / Interactive playground
Put the rules
to the test.
Configure a policy. Send a request.
See the boundary in action.
SIMULATION
No wallet connection. No signatures. No real transactions or funds.
Ready to startVORN / LOCAL DEMO
V01
AGENT / VORN–01
Make a request.
Used in 24 hours0.00 USDC
Daily remaining500.00 USDC
Session expires inNot started
Session usage: 0.00 / 1,000.00 USDCReady when you are.
TRY A SCENARIO
[ ]
Awaiting a request
The boundaries are yours.
Start a session, then send your first request.
Decision log
0 requestsYour agent's decisions will appear here.
| Request / Time | Amount | Decision | Reason |
|---|
This simulation runs in your browser. Saved data stays on this device. Approvals are simulated and do not execute on a blockchain.
03 / Under the surface
Clear rules.
No mystery.
Each request is checked against the current session, permissions, destination and budget. If a check fails, the request is denied.
Try the policy engine ↗What can I do in the playground?+
Set allowed actions and destinations, define USDC budgets, and start a one-hour demo session. Send requests to see approvals, denials and the exact reason behind each result.
Does this control a real wallet?+
No. This is a local policy simulation. It never asks for a wallet connection, private key or signature. A production product would need verified transaction data and permissions enforced by the wallet or smart contracts.
How are spending limits calculated?+
Only approved requests count. Each amount is checked against the per-request limit, approved spending over the last 24 hours, and total session spending. Denied requests consume no budget.
Can I change a running policy?+
Yes. Save a new policy at any time. It applies to the next request without resetting usage or extending the session. Lowering a budget below existing usage blocks further spending.
What happens when I revoke access?+
The session immediately denies future requests. Its usage and decision log remain available. Start a new demo session to clear the history and begin again.
Where is the session stored?+
In this browser's local storage, when available. There is no shared server. Export the decision log as JSON to keep a record. Clearing browser data removes the saved session.
You define the boundary.
Let the agentdo the rest.↗