Wallet skill runtime

Install wallet skills without giving AI your private key.

SkillWallet* lets users grant bounded permissions to wallet skills. AI can reason when enabled, but execution stays permissioned, delegated, and controlled by the user.

AI reasons. Backend executes. User controls permissions.

Explore Skills

No AI private key access

Bounded delegated permissions

Optional x402 + Venice AI reasoning

Runtime flow

How SkillWallet* works

01

Install a skill

Users select wallet skills from the catalog, such as DCA, cron-based execution, or inbound-event strategies.

02

Grant bounded permission

The user signs a constrained delegation. The backend can only operate inside the approved permission scope.

03

Runtime evaluates triggers

Skill Runtime checks schedules, onchain events, skill configuration, and optional data sources.

04

Backend executes approved actions

AI may return execute or skip when enabled, but it never signs. Execution is backend-built and permission-bounded.

Skill modules

Installable wallet skills

Skills are installed as permissioned modules. Each skill declares its trigger, execution scope, and whether AI reasoning is enabled.

AI-Powered DCA

cron
Trigger
custom cron
Data
optional x402
Reasoning
Venice AI enabled
Execution
delegated backend call
Permission
bounded spend + token scope

Custom Cron DCA

cron
Trigger
custom cron
Data
none required
Reasoning
disabled
Execution
delegated backend call
Permission
bounded spend + schedule scope

USDC Inbound DCA

event
Trigger
USDC inbound event
Data
optional runtime context
Reasoning
optional
Execution
delegated backend call
Permission
bounded token + receiver scope

Permission model

Permissioned execution, not autonomous wallet control.

The user grants bounded permissions. The backend can only execute approved actions inside that delegation scope. AI can suggest an execute or skip decision when a skill enables reasoning, but AI never signs transactions and never receives private keys.

What AI can do

  • Read skill context
  • Consume optional x402 data
  • Return execute / skip decision
  • Provide a reason

What AI cannot do

  • Access private keys
  • Sign transactions
  • Bypass delegation limits
  • Execute outside approved scope

System design

Runtime architecture

The runtime keeps reasoning, permission checks, execution building, and wallet signing clearly separated.

User + MetaMask
Frontend App
Skill Catalog
Installation / Delegation API
Database
Skill Runtime
Cron Runner / Event Handler
Optional x402 Service
Optional Venice AI reasoning
Execution Builder
Sponsor / Executor Context
1Shot Relayer
EVM Chain
Execution History

Start controlled

Start with one bounded wallet skill.

Explore Skills