Know the actor
An agent identity links a request to an owner and a scoped role. Identity is context, not a guarantee of trust.

Agents propose the action.
You define what happens next.
A permission layer for agent identity, spending policies and accountable decisions. Explore the flow before connecting a wallet.
Follow the permission path ↓Three parts of a permission system, designed to stay connected.
An agent identity links a request to an owner and a scoped role. Identity is context, not a guarantee of trust.
Express limits on amounts, recipients and sessions. Every proposed action can be evaluated against the same rules.
Connect the request to the policy and decision. A useful audit trail explains why an action was allowed or blocked.
Place policy evaluation between an agent’s intent and the execution boundary. Wallet access is available in the workspace; transaction writes remain gated until contracts are configured.
Open demo workspace ↗intent = agent.propose()
policy = owner.boundaries
decision = evaluate(intent, policy)
if decision.allowed:
// execution boundary
else:
// stop before signing
audit.record(intent, decision)Illustrative pseudocode · no execution here
Interactive, not transactional.The walkthrough and workspace use example identities, balances and decisions. They are not onchain activity.
Integration boundaries.Connecting a wallet does not deploy a policy or authorize agent spending. Contract writes remain gated.
Trust is earned.This preview makes no claim of a deployed, audited protocol or guaranteed protection of funds.