Skip to content
AgentLayer Docs

Quick Start

Quick Start

Most local setup can still be delegated to an agent or installer, but three things should remain user-owned:

  • runtime secrets
  • wallet passwords
  • final approval for risky writes

Fastest install path

The easiest current setup is still the bundled installer:

Terminal window
npx @agentlayer.tech/wallet install --yes

That lays down the local runtime, Python backend, helper services, and host config scaffolding.

Solana-first setup

The default onboarding path is Solana.

You provide the local runtime secrets:

Terminal window
export AGENT_WALLET_BOOT_KEY='...'
export AGENT_WALLET_MASTER_KEY='...'
export AGENT_WALLET_APPROVAL_SECRET='...'

Then install or finalize the local runtime.

You do not need to bring your own Solana RPC just to get started. The default path already supports:

  • hosted shared Solana RPC through the provider gateway
  • Bags provider access
  • Jupiter Earn provider-gateway backed flows

Bring your own RPC only if you want more control, higher limits, or more predictable performance.

Bitcoin setup

Start the local Bitcoin runtime:

Terminal window
cd wdk-btc-wallet && sh run-local.sh

Then connect it to OpenClaw:

Terminal window
sh agent-wallet/scripts/setup_btc_wallet.sh

That flow creates or unlocks a local BTC wallet and binds it to the current host user.

EVM setup

Start or bootstrap the local EVM runtime:

Terminal window
sh agent-wallet/scripts/setup_evm_wallet.sh

That host-side setup can:

  • start wdk-evm-wallet
  • create or unlock the local EVM vault wallet
  • bind the wallet for the local user
  • wire OpenClaw to backend=wdk_evm_local

Safety model during setup

The operational split is still the same:

  • the user owns secrets, passwords, and approvals
  • the agent can automate installation, binding, and routine wallet operations through constrained tools