CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-agent-wallet

Add budget limits, approval workflows, and a policy-gated wallet layer to your autonomous agents. Use when: Enforce daily and per-transaction spend limits on autonomous agents; Create a human-in-the-loop approval queue for high-value AI payments; Maintain an immutable audit log of every payment attempt and decision.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openclaw-agent-wallet/SKILL.md
SKILL.md
Quality
Evals
Security

Openclaw Agent Wallet

Free skill by Nex AI. This file is the public guide from Agensi. Scripts, extension source, and templates from the original package are not in this folder.

Control Agent Spending without Giving Up Keys

The OpenClaw Agent Wallet provides a robust policy and budgeting layer for autonomous agents. It solves the "blank check" problem by sitting between your agent's decision-making logic and your actual funds, ensuring no agent can accidentally or maliciously drain a wallet.

What it does

This skill implements a rigorous spend-gate. Instead of giving an agent direct access to private keys, it forces every transaction through a WalletPolicy engine. It supports hard caps (per transaction, per day, or lifetime), domain-based allow/deny lists, and a human-in-the-loop approval queue for high-value transfers.

  • Policy-Based Budgeting: Define strict financial guardrails in JSON.
  • Air-Gapped Signing: Communicates with an external signer service via WALLET_SIGNER_URL, keeping private keys entirely outside the agent's environment.
  • Human-in-the-Loop: Automatically queues transactions exceeding specific thresholds for manual CLI or webhook approval.
  • Immutable Audit Logs: Every success, failure, and manual intervention is recorded in an append-only JSON log for full accountability.

Why use this skill?

Prompting an AI to "be careful with money" is not a security strategy. This skill provides a technical enforcement layer that works regardless of the model's behavior. It is framework-agnostic, working seamlessly with OpenClaw or local Python-based agents, and focuses on the custody boundary—ensuring your credentials stay safe while your agent stays productive.

When to use

  • Enforce daily and per-transaction spend limits on autonomous agents
  • Create a human-in-the-loop approval queue for high-value AI payments
  • Maintain an immutable audit log of every payment attempt and decision
  • Decouple private key management from agent logic via secure signer URLs

Known limitations

  • Requires separate external signer service.
  • Local file-based logs/queues: not natively distributed.
  • No built-in currency conversion: assumes single-currency policy.

Example

Request

Setup a wallet policy for my agent with a $50 daily limit and require my approval for any transaction over $10.

Result

Wallet policy initialized:

  • Daily Cap: $50.00
  • Approval Threshold: >$10.00
  • Audit Log: active (vault/audit.jsonl)

The agent now routes all spend requests through the policy engine. Transactions >$10 will remain 'pending' until approved via the CLI.

Questions

How does the openclaw-agent-wallet prevent my AI agent from overspending?

This skill acts as a security middleware that prevents agents from draining funds by enforcing hard spending caps, domain restrictions, and human-approval workflows, ensuring you never hand over a 'blank check.'

Does this skill require me to share my private keys directly with the AI?

No, your private keys never touch the agent's environment; the skill uses an air-gapped signing process via a dedicated URL to ensure your credentials remain isolated and secure.

Which AI frameworks or agents are compatible with this wallet layer?

The skill is framework-agnostic and written in Python, making it compatible with the native OpenClaw framework as well as any custom local agent that can interface with JSON-based policy engines.

Can I require manual approval for high-value transactions only?

You can set auto-approval limits for small tasks while requiring manual CLI or webhook intervention for transactions that exceed a specific dollar amount or target unrecognized addresses.

What is required to get the wallet layer up and running?

Setup involves configuring your spend policies in a JSON file and defining your remote signer URL; the package includes the core policy engine, the audit logger, and integration templates.

Does the skill provide a record of all agent financial activity?

Yes, the skill maintains an immutable, append-only JSON audit log that records every attempted transaction, policy hit, and manual approval for full financial accountability.


Built by Nex AI. More skills, including the paid catalog: https://www.agensi.io/creators/ch1n4-g3nd4x

Repository

NexaiGuy/nex-ai-skills

Path

skills/openclaw-agent-wallet/SKILL.md

Last updated
First committed

Also appears in

NexaiGuy/nex-ai-skills
In sync

since Nov 6, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.