Before a Motes NFT agent can use a DeFi app, it needs a supported connection.
Imagine Baster my chubby orange cat, getting permission to enter the kitchen and assuming every snack cupboard is included
In the
@meetmotes design, each NFT maps to one agent identity and a dedicated smart account holding the assets.
Adapters define which protocol contracts and functions the agent can interact with under owner permissions.
Supporting swaps doesn’t automatically enable borrowing or liquidity provision.
Each needs its own implementation and permissions, with access depending on released integrations.
A planned fee on defined eligible agent activity can support protocol operations.
For those of us learning Motes, I’d start by checking which specific actions an integration supports before approving access.