@agentlayer.tech/wallet 0.1.13 → 0.1.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -4,17 +4,25 @@
4
4
  These instructions apply to the entire `.openclaw/` tree.
5
5
 
6
6
  ## Purpose
7
- This tree contains local OpenClaw host-side workspace assets. In the current repo, its primary responsibility is the `agent-wallet` extension that bridges OpenClaw to the authoritative Python `agent-wallet` backend.
7
+ This tree contains local OpenClaw host-side workspace assets. In the current repo, its main responsibilities are:
8
+
9
+ - the `agent-wallet` extension that bridges OpenClaw to the authoritative Python `agent-wallet` backend
10
+ - the `pay-bridge` extension that bridges OpenClaw to the local `pay` CLI for paid API discovery and execution
8
11
 
9
12
  ## Current structure
10
13
  - `.openclaw/extensions/agent-wallet/index.ts` — TypeScript extension entrypoint registered by OpenClaw.
11
14
  - `.openclaw/extensions/agent-wallet/openclaw.plugin.json` — plugin manifest and config schema.
12
15
  - `.openclaw/extensions/agent-wallet/package.json` — extension package metadata.
13
16
  - `.openclaw/extensions/agent-wallet/skills/wallet-operator/SKILL.md` — user-facing operational wallet safety guidance.
17
+ - `.openclaw/extensions/pay-bridge/index.ts` — TypeScript entrypoint for the local `pay` CLI bridge.
18
+ - `.openclaw/extensions/pay-bridge/openclaw.plugin.json` — plugin manifest and config schema for pay tools.
19
+ - `.openclaw/extensions/pay-bridge/core.mjs` — local `pay` command execution and output shaping.
20
+ - `.openclaw/extensions/pay-bridge/skills/pay-operator/SKILL.md` — user-facing operational guidance for paid API usage.
14
21
 
15
22
  ## Design intent
16
23
  - Keep the TypeScript extension thin and host-oriented.
17
24
  - Let Python own wallet logic, policy, approvals, signing rules, and Solana implementation details.
25
+ - Let `pay` remain the source of truth for paid API wallet/account behavior.
18
26
  - Let the extension focus on:
19
27
  - resolving config
20
28
  - locating the Python package
@@ -27,6 +35,7 @@ This tree contains local OpenClaw host-side workspace assets. In the current rep
27
35
 
28
36
  ### Keep bridge logic thin
29
37
  - Do not duplicate business logic from Python unless OpenClaw requires it at registration time.
38
+ - Do not duplicate payment protocol logic from `pay`; prefer invoking the local CLI and shaping its output.
30
39
  - Do not reimplement approval validation, transaction policy, wallet derivation, or Solana-specific rules in TypeScript.
31
40
  - Prefer forwarding config into the CLI bridge and letting Python decide runtime behavior.
32
41
  - Treat this layer as a transport and schema bridge, not an execution authority.
@@ -2,6 +2,12 @@
2
2
 
3
3
  Workspace extension for the official OpenClaw agent.
4
4
 
5
+ External install path:
6
+
7
+ ```bash
8
+ openclaw plugins install clawhub:@agentlayertech/agent-wallet-plugin
9
+ ```
10
+
5
11
  This extension registers wallet tools through the official OpenClaw plugin API and forwards execution to the local Python `agent-wallet` backend.
6
12
 
7
13
  It is designed so the OpenClaw agent sees a small operational wallet surface instead of raw key management.
@@ -57,6 +63,20 @@ Recommended local installer entrypoint:
57
63
  sh ./setup.sh
58
64
  ```
59
65
 
66
+ For packaged installs, keep the runtime installer path:
67
+
68
+ ```bash
69
+ npx @agentlayer.tech/wallet install --yes
70
+ ```
71
+
72
+ The ClawHub plugin package only installs the native OpenClaw plugin. It expects the authoritative Python runtime to already exist, and by default it now looks for it at:
73
+
74
+ ```bash
75
+ ~/.openclaw/agent-wallet-runtime/current/agent-wallet
76
+ ```
77
+
78
+ If that runtime is not present, set `plugins.entries.agent-wallet.config.packageRoot` explicitly.
79
+
60
80
  That installs the Python backend, Node dependencies for the local BTC/EVM runtimes, and patches the OpenClaw plugin config. Wallet creation, unlock, and local service start stay as separate host-side steps.
61
81
 
62
82
  For self-hosted installs, prefer `SOLANA_RPC_URL` / `SOLANA_RPC_URLS` in local env and treat the plugin `rpcUrl` / `rpcUrls` fields as fallback only. If the local runtime exposes `ALCHEMY_API_KEY` or `HELIUS_API_KEY`, the wallet can derive the Solana RPC URL automatically for `mainnet` or `devnet`. Local env always takes precedence over `openclaw.json`.