←
Create Permission Token
1
Identity
2
Permissions
3
Forbidden
4
Binding
5
Review
Token Identity
Name your token, specify the agent, and choose a blockchain.
A human-readable name for this permission token
Auto-generated unique identifier. This binds the token to the agent.
Scope this token to a specific user. Leave empty for an agent-level token that applies to all users. Can be a Slack user ID, email, or any identifier your system uses.
đŸ”ĩ
Ethereum L2 - Base
Ethereum L2 (ERC-721)
âšĒ
Algorand
ASA
🔒 On-Chain Identity
By default, a pseudonymous identifier is used on-chain to protect your agent's real name. Only your organization can link it back to the real agent.
Use real agent name on-chain
If enabled, the actual agent ID will be publicly visible on the blockchain. Default: off (decoy identifier used).
On-chain identifier: al-â€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸâ€ĸ
Describe what your agent should do
Tell us in plain English what you want this agent to do, and we'll configure the permissions automatically. You can review and adjust before minting.
Try: "Read my email and calendar, search the web, but block all PII"
Forbidden Actions
Explicit deny rules that override all permissions. Even if a tool is allowed in Step 2, a forbidden rule here will block it. Use these for hard safety boundaries.
🧠 Describe what should be forbidden in plain English:
+ Add forbidden action
💡 Common patterns:
â€ĸ Block all shell access: forbid exec — "Shell commands not permitted"
â€ĸ Block external comms: forbid message — "No outbound messaging allowed"
â€ĸ Block file deletion: forbid exec with params rm — "File deletion prohibited"
â€ĸ Block sub-agents: forbid sessions_spawn — "Cannot create child agents"
Session Binding & Expiration
Control when and where this token is valid.
Session Binding
Lock this token to a specific agent session. When strict, the token only works within that exact session.
Strict Mode
Token only valid within this exact session (recommended)
Expiration
Set an automatic expiration date for this token.
Choose what happens when the token reaches its expiration date.
🔐 Permission Encryption
Encrypt permissions on-chain so they can't be read without the decryption key. Enterprise feature for sensitive/classified agent configurations.
Encrypt Permissions
AES-256-GCM encryption. Only your organization can decrypt and verify permissions.
What this means:
  • Permissions stored as encrypted ciphertext
  • On-chain: only a SHA-256 hash is visible
  • Runtime decrypts in memory during verification
  • Competitors and public cannot see agent capabilities
Review & Mint
Confirm your token configuration before minting to the blockchain.
Token Identity
—
—
Blockchain
—
On-Chain Identity
—
Permission Mode
—
Allowed Tools
—
Description
This description is stored with the token. Edit freely before minting.
Minting Token
Writing to blockchain, please wait...
1
Preparing Transaction
Validating permissions and creating wallet
2
Minting On-Chain
Submitting transaction to the blockchain
3
Confirming
Waiting for blockchain confirmation
4
Recording
Saving token to database and cache
🎉
Token Minted Successfully!
Your permission token is now live on-chain.
❌
Minting Failed