Why Functor
Functor enables a global registry of permissions onchain, accessible by any agent.
Traditional agentic wallets store permissions locally or in centralized servers.
Functor's Keystore infrastructure makes composable permissions accessible across any chain and any wallet, enabling:
| Agent-to-agent verification | Two AIs acting on the same wallet can verify each other's authority onchain. No platform in between. |
| Cross-app authorization | Any DEX, orderbook, or protocol can read whether an agent is authorized, without integrating with the specific wallet vendor. |
| A new class of agent services | Users hire AI agents through onchain employment contracts. Anyone can verify what an agent is allowed to do, and revoke is one transaction. |
What Functor solves
Permissions without a middleman
Authorization rules live onchain, not in a vendor's database. Any protocol can verify whether an agent is allowed to act, with no integration required.
Policy enforced before every transaction
Spend caps, contract allowlists, and expiry windows are validated at the execution layer, not in application code that can be bypassed.
Self-custodial by architecture
The user signs. The user revokes. Functor never holds keys. Grant or revoke in one transaction, with no support ticket and no counterparty risk.
Who it's for
App developers
Ship agentic features with a wallet your users actually control. Give an agent a scoped key, not full custody, and let the chain enforce the limit.
AI agent builders
Equip your agent with a wallet and a capped, revocable session. The agent operates within the bounds the user set, and those bounds are publicly verifiable.
Protocols and integrators
Read agent authority from the chain before executing. Know exactly what an agent is allowed to do without trusting the agent's own claims.